Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Promiscuous\s+and\s+Multicast\s+semantics\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Promiscuous\s+and\s+Multicast\s+semantics\s*$/: 8 ]

Total 8 documents matching your query.

1. Promiscuous and Multicast semantics (score: 1): Author: xxxxxx>; Date: Sat, 08 Sep 2001 15:14:06 +1000; G'day all, I am working on adding multicast / promiscuous mode support to the CDCEther driver (USB Communication Device Class, Ethernet control model - and don't blame me for the name...) The questio; /archives/netdev/2001-09/msg00040.html (8,375 bytes)
2. Re: Promiscuous and Multicast semantics (score: 1): Author: xxxxxxx; Date: Sat, 8 Sep 2001 11:32:01 -0400 (EDT); ... Correct. Every change to the Rx filter is communicated by a call to net_device.set_multicast_list(dev) [[ This name is slightly misleading: at one point this call had three parameters, including; /archives/netdev/2001-09/msg00042.html (11,244 bytes)
3. Re: Promiscuous and Multicast semantics (score: 1): Author: xxxxxx>; Date: Sun, 09 Sep 2001 19:51:54 +1000; Is this a "necessary", in that if that call is made, something has definately changed? OK, that did help, although having your explaination to read with the code certainly made it a lot easier. Thank; /archives/netdev/2001-09/msg00044.html (9,650 bytes)
4. Re: Promiscuous and Multicast semantics (score: 1): Author: xxxxxxxxxxxxxx>; Date: Sun, 9 Sep 2001 10:15:22 -0400 (EDT); No, there are cases where set_multicast_list() is called without a change in the Rx filter. It's usually called three times when the interface is started, when you would expect that just once would d; /archives/netdev/2001-09/msg00047.html (12,467 bytes)
5. Promiscuous and Multicast semantics (score: 1): Author: Brad Hards <bhards@xxxxxxxxxxxxxx>; Date: Sat, 08 Sep 2001 15:14:06 +1000; G'day all, I am working on adding multicast / promiscuous mode support to the CDCEther driver (USB Communication Device Class, Ethernet control model - and don't blame me for the name...) The questio; /archives/netdev/2001-09/msg00177.html (8,375 bytes)
6. Re: Promiscuous and Multicast semantics (score: 1): Author: Donald Becker <becker@xxxxxxxxx>; Date: Sat, 8 Sep 2001 11:32:01 -0400 (EDT); ... Correct. Every change to the Rx filter is communicated by a call to net_device.set_multicast_list(dev) [[ This name is slightly misleading: at one point this call had three parameters, including; /archives/netdev/2001-09/msg00179.html (11,284 bytes)
7. Re: Promiscuous and Multicast semantics (score: 1): Author: Brad Hards <bhards@xxxxxxxxxxxxxx>; Date: Sun, 09 Sep 2001 19:51:54 +1000; Is this a "necessary", in that if that call is made, something has definately changed? OK, that did help, although having your explaination to read with the code certainly made it a lot easier. Thank; /archives/netdev/2001-09/msg00181.html (9,698 bytes)
8. Re: Promiscuous and Multicast semantics (score: 1): Author: Donald Becker <becker@xxxxxxxxx>; Date: Sun, 9 Sep 2001 10:15:22 -0400 (EDT); No, there are cases where set_multicast_list() is called without a change in the Rx filter. It's usually called three times when the interface is started, when you would expect that just once would d; /archives/netdev/2001-09/msg00184.html (12,522 bytes)

Current List: 1 - 8
Page: [1]