On Tuesday 21 February 2006 17:00, you wrote: > > You need to patch dscape. Read the HOWTO: > > http://bu3sch.de/git?p=wireless-2.6.git;a=blob;h=6d5384008f944bb9a7ec1650426c6fcfb3e9f6ef;hb=dscape;f=Documentation/networking/bcm43xx-d80211-HOWTO.txt > > You can optionally try with -Dwext. That _should_ be supported, too, > > without patching. But I did not try this, yet. > > > > Thx for the hint, I have patched wpasupplicant. > The script seems to execute fine, there is a FIXME message but thats > all. > > The association is not working! > > I have several interface: (lo, eth0), eth1, wlan0, wlan0ap, wlan0.11, > sta0 > > Which one should I try associate? > iwconfig wlan0 essid mol > Result: nothing, no error message, nothing in the dmesg > > iwconfig sta0 essid mol > Result: nothing, but in the dmesg there is shown this: > sta0: Initial auth_alg=0 > sta0: authenticate with AP 00:11:d8:30:bf:0a > sta0: RX authentication from 00:11:d8:30:bf:0a (alg=0 transaction=2 > status=0) > sta0: authenticated > sta0: associate with AP 00:11:d8:30:bf:0a > sta0: RX ReassocResp from 00:11:d8:30:bf:0a (capab=0x401 status=0 aid=1) > sta0: associated
You are properly associated and the wireless network is up and running. > But iwconfig show ESSID:off/any. > Ping is not working (ping 192.168.1.1, my ap address) Probably a routing issue. I don't think this is related to the driver, as you successfully associated. That means sending and receiving properly works. The problem is in an upper layer. > Other ideas? Why is so many interfaces? Consider it a design-bug. :) > And which one should I use? sta0 is your wireless station. -- Greetings Michael.
pgpfhL872JR1o.pgp
Description: PGP signature
