> Speaking of which, I'd really like to see bridge support getting added to
> all new NIC drivers from now on. However, the current bridge interface
> leaves something to be desired...
hopefully things will improve if someone finds the time to
extend ether_input() as suggested by archie Cobbs an
Robert Watson writes:
> > You should go promiscuous to multicast. If the card doesn't support
> > that, you should go fully promiscuous and drop unicasts that aren't
> > to you. (Make sure you don't block packets that bpf is going to
> > want to see).
>
> Also, if you want bridging support, you
On Fri, 21 Apr 2000, Bill Fenner wrote:
> >What should I do when I see ALLMULTI?
>
> You should go promiscuous to multicast. If the card doesn't support
> that, you should go fully promiscuous and drop unicasts that aren't
> to you. (Make sure you don't block packets that bpf is going to
> wan
>What should I do when I see ALLMULTI?
You should go promiscuous to multicast. If the card doesn't support
that, you should go fully promiscuous and drop unicasts that aren't
to you. (Make sure you don't block packets that bpf is going to
want to see).
Bill
To Unsubscribe: send mail to [E
Hi
In my seemingly never ending quest to get a correctly functioning
driver for the WebGear wireless LAN cards I need some advice on how to
DTRT with multi-casts.
The WebGear cards can be programmed with 16 multicast addresses, from
these the NIC itself generates hashes.
So what should I do whe
5 matches
Mail list logo