[linux-dvb] problems with dvbnet interfaces in promiscous mode

Sebastian Heidl s.heidl at teles.de
Thu Feb 2 11:10:01 CET 2006


Does anyone care to comment on this one ? I'm not willing to believe we
are the only ones experiencing this problem. Or maybe this is a FAQ ?
Then please point me to the right document.

regards.
_sh_

On Wed, 2006-02-01 at 10:04 +0100, Sebastian Heidl wrote:
> we're trying to establish monitoring for a data application over
> satellite. As several transponders have to be monitored we are using
> several adapters in one machine. The recognition of the adapters and the
> creation of the network interfaces is without problems.
> 
> >>>>>>>>>> dmesg output (MAC adresses hidden) >>>>>>>>>>
> b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
> flexcop-pci: will use the HW PID filter.
> flexcop-pci: card revision 2
> PCI: Found IRQ 12 for device 0000:00:0a.0
> PCI: Setting latency timer of device 0000:00:0a.0 to 64
> DVB: registering new adapter (FlexCop Digital TV device).
> b2c2-flexcop: MAC address = 00:d0:d7:0e:34:3f
> b2c2-flexcop: found the stv0299 at i2c address: 0x68
> DVB: registering frontend 0 (ST STV0299 DVB-S)...
> b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S' at the 'PCI' bus controlled by a 'FlexCopIIb' complete
> flexcop-pci: will use the HW PID filter.
> flexcop-pci: card revision 1
> PCI: Found IRQ 10 for device 0000:00:0b.0
> PCI: Setting latency timer of device 0000:00:0b.0 to 64
> DVB: registering new adapter (FlexCop Digital TV device).
> b2c2-flexcop: MAC address = 00:d0:d7:02:0f:9d
> b2c2-flexcop: found the stv0299 at i2c address: 0x68
> DVB: registering frontend 1 (ST STV0299 DVB-S)...
> b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S' at the 'PCI' bus controlled by a 'FlexCopII' complete
> 
> 
> Only when the interfaces are put into promiscous mode, which is a must
> for the monitoring application, the traffic of _all_ adaptors is sent to
> the interfaces. That way it's not possible to differentiate the
> transponders any more.
> 
> So is there a way to separate the traffic of the transponders ? Maybe
> some module parameters we missed ?
> 
> We used the v4l-dvb-20060115.tar.gz snapshot compiled against the latest
> RHEL4 kernel in our tests.




More information about the linux-dvb mailing list