Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] Re: dvb and dvb0_0 network device
Hi, Johannes Stezenbach
I have nothing when i do : ---> dvbsnoop -n 1 -crc 101
But i 've seen in the feature list of dvbsnoop on the website :
http://dvbsnoop.sourceforge.net/features.html
that for the option -crc and -nocrc :
CRC check | if supported by hardware, firmware or driver (demux level)
I have a PCI nexus-s from technotrend
Do you think that the option -crc could be used in my case.
If it's right I've got a problem with my crc32 function ....
Do you know where i can found a dvbsnoop ouput with a full mpe packet and an
IP datagramm inside. (and a good CRC32)
**************************
THANKS Johannes
**************************
----------------------------------------------------------
-----------------------------------------------------------
Quoting Johannes Stezenbach <js@convergence.de>:
> On Thu, Jun 10, 2004 at 09:30:36AM +0200, dvb@cristalys.com wrote:
> >
> > # dvbsnoop -n 1 101
> >
> > ----------------------------------------------------------
> > SECT-Packet: 00000001 PID: 101 (0x0065), Length: 80 (0x0050)
> > Time received: Thu 2004-06-10 09:02:20.367
> > ----------------------------------------------------------
> > 0000: 3e b0 4d 7b f1 c1 00 00 20 5c d0 00 45 00 00 40 >.M{....
> \..E..@
> > 0010: 1d 54 00 00 ff 01 89 68 0a 01 00 fe 0a 01 00 01
> .T.....h........
> > 0020: 08 00 38 8c 03 d5 00 00 00 07 e5 59 00 00 70 fe
> ..8........Y..p.
> > 0030: ab cd ab cd ab cd ab cd ab cd ab cd ab cd ab cd
> ................
> > 0040: ab cd ab cd ab cd ab cd ab cd ab cd 7d 24 f5 0a
> ............}$..
>
>
> Looks good to me. If you still get the same output with
> # dvbsnoop -n 1 -crc 101
> then the CRC is correct, otherwise you have found your problem.
>
>
> > and the ifconfig gave me:
> >
> > ----------------------------------------------------------------
> > dvb0_0 Lien encap:Ethernet HWaddr 00:D0:5C:20:F1:7B
> > inet adr:10.1.0.1 Bcast:10.255.255.255 Masque:255.0.0.0
> > UP BROADCAST RUNNING NOARP MULTICAST MTU:4096 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 lg file transmission:1000
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> Either there was no traffic, or the CRC was wrong. (You should run
> tcpdump after configuring the interface to set it into promiscous mode,
> otherwise a wrong MAC address could also be the reason for not seeeing
> any traffic).
>
> Johannes
>
>
>
Home |
Main Index |
Thread Index