From: Stephens, A. <all...@wi...> - 2006-07-26 19:20:03
|
Hi there: =20 I've been running UML using Linux 2.6.17 (guest) and 2.6.12 (host) and configured a guest with a pair of Ethernet multicast interfaces as shown below. (Note that I didn't configure any IP addresses, as I'm not trying to use them to carry IP traffic.) =20 uml_mconsole <session> config eth1=3Dmcast,00:00:00:00:01:01 uml_mconsole <session> config eth2=3Dmcast,00:00:00:00:02:02 =20 When a second guest transmitted traffic using a destination address of 00:00:00:00:01:01, the message showed up on both interfaces (as expected). However, the kernel protocol handled incoming messages did not recognize and discard the unwanted copy that showed up at "eth2" because the associated "struct net_device" object did not have the "promiscuity" field set to indicate that the interface might receive traffic other than its own. =20 It seems to me that any UML interface configured to use multicast should cause the promiscuity field of the associated net_device to be set -- but maybe I'm missing something here. Is the scenario I encountered really a bug? If so, is it a bug with UML or some other part of the Linux kernel? =20 Regards, Al Stephens Wind River =20 |