pcap_to_ts
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pcap_to_ts [2016/12/14 21:47] – walkeradmin | pcap_to_ts [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PCAP to TS ====== | ====== PCAP to TS ====== | ||
+ | <color orange> | ||
---- | ---- | ||
- | \\ | ||
- | \\ | ||
- | <color red>This page is incomplete</ | ||
- | \\ | ||
\\ | \\ | ||
Sometimes it is useful to capture the video streams we are generating (or someone else is generating) that are present on the network. Using a Dektec is useful here, however we don't always have the opportunity to use an analyser. | Sometimes it is useful to capture the video streams we are generating (or someone else is generating) that are present on the network. Using a Dektec is useful here, however we don't always have the opportunity to use an analyser. | ||
Line 32: | Line 28: | ||
The format for tcpdump is - tcpdump -i < | The format for tcpdump is - tcpdump -i < | ||
tcpdump -i eth2 -B 64000 dst host 239.0.12.1 and port 1234 and multicast -w / | tcpdump -i eth2 -B 64000 dst host 239.0.12.1 and port 1234 and multicast -w / | ||
+ | |||
| | ||
+ | Example: | ||
+ | tcpdump -i eth2 -B 64000 dst host 239.0.100.1 and port 1234 and multicast -w / | ||
+ | |||
+ | |||
if the syntax is correct, the tcpdump will start: | if the syntax is correct, the tcpdump will start: | ||
tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size 65535 bytes | tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size 65535 bytes | ||
Line 54: | Line 55: | ||
---- | ---- | ||
==== Convert .pcap to .ts ==== | ==== Convert .pcap to .ts ==== | ||
+ | <color red>This is done on your computer, not on the MFEL</ | ||
\\ | \\ | ||
\\ | \\ | ||
Line 59: | Line 61: | ||
\\ | \\ | ||
\\ | \\ | ||
+ | There is a tool available called <color red> | ||
+ | \\ | ||
+ | \\ | ||
+ | Download the extractor file here {{ : | ||
+ | \\ | ||
+ | \\ | ||
+ | Before we extract the TS data, we need to know what the <color red> | ||
+ | \\ | ||
+ | \\ | ||
+ | To use the extractor, use the following syntax: | ||
+ | \\ | ||
+ | extractor source_file.pcap output.ts multicast port | ||
+ | \\ | ||
+ | If I have a source file called <color red> | ||
+ | \\ | ||
+ | \\ | ||
+ | extractor mfel.pcap mfel.ts 239.0.12.1 1234 | ||
+ | | ||
+ | If successful then you will see an output | ||
- | + | SkyStream Networks sniffer-to-MPEG Extractor Utility | |
- | + | Built May 5 2005 11:29:37 | |
- | + | ||
- | + | File had 119658 packets, 119658 extracted | |
- | + | \\ | |
- | + | The number of packets will change of course, but you should now have an extracted TS file. | |
- | Finally, see the FFMPEG section where you can convert .ts files to .mpg files (great for converting captures for replay on TVs via USB). | + | \\ |
+ | \\ | ||
+ | <color red> When using tcpdump, after capture you will get a packet count, when using extractor the packet count should be around the same, if not then the extract did not do the entire file.</ | ||
+ | \\ | ||
+ | ---- | ||
+ | ==== And Finally... ==== | ||
+ | See the FFMPEG section where you can convert .ts files to .mpg files (great for converting captures for replay on TVs via USB).[[ffmpeg|FFMPEG]] | ||
pcap_to_ts.1481752046.txt.gz · Last modified: 2023/03/09 22:35 (external edit)