On Fri, 30 Jul 2004 22:27:43 +0200 Xavier Van Laethem <xavier@xxxxxxxxxxxx> wrote: > > >From FAQ > ------------------------------------------------------ > It doesn't work with my Wireless card! > > This is a known problem, and it is not caused by the bridge code. Many > wireless cards don't allow spoofing of the source address. It is a firmware > restriction with some chipsets. You might find some information in the bridge > mailing list archives to help. > ------------------------------------------------------ > > Trying with hostap driver for wifi card. It work when wifi card is in master > mode but it is no more working with wifi card in managed or ad-hoc mode. > So y try changing hardfware (ethernet) address of the wireless card (using the > one of bridge interface) with "ip link set wlan0 address..." and it seems to > work well... (it should also work with "ifconfig..." but y an using the one > comming from busybox and it doesn't allow to change hw address) > y dont find any such solution in the mailing list.... It seems that hostap doesn't provide the same interface as normal ethernet card. One problem is that it doesn't forward packets between nodes connected to the same access point. These are hostap problems, and should be fixed there, the bridge code shouldn't need to have special code for the hostap devices. > By the way, why is the hardware address of the bridge chanching at each > interface added to the bridge? Solution would be simpler if the bridge keep > hardware addres of the first interface added, and by adding wireless > interface first, no? Probably just a stupid day one coding bug.. The problem is what if the first interface goes away? > Xavier Van Laethem
