Re: probs with a Linksys WUSB11 ver2.8 in Mandrake...
Joerg Albert <[email protected]>
| Newsgroups | gmane.linux.drivers.at76c503a.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Ryan, On Mon, 2 Feb 2004, Ryan Mueller wrote: > > All signal quality and data transmission values are 0, as it's not > > connected. Might I need to specify the DHCP server? Windows lists it > > as the same address as the gateway IP. I don't know what the access > > point address is supposed to be. From what I saw in the iwconfig man > > it should determine it automatically. I tried running "iwconfig wlan0 > > ap any" which would force it to set determination to auto, but it said > > command not supported. The only thing that comes up in windows > > resembling an address is "Physical Address" under Network Connection > > Details. Listed as 00-0C-41-56-67-89. Do I need to specify that? > > Thanks for the help, you can use iwconfig wlan0 essid any to connect to any accesspoint around (unless it has SSID broadcasting disabled). "iwconfig wlan0 ap ..." isn't implemented in the driver (yet) - I'm still waiting for a good argument why it is useful. Access points are usually identified by their SSID, you specified "linksys" in your config file. > Slight addendum......the 00-0C-41-56-67-89 is the address for my access > point, and it shows it in the dmesg output when it loads the drivers and > recognizes the device. Could you please post the line where the MAC address of your AP is mentioned in the syslog (should contain more info)? Unless iwconfig wlan0 does not display your access point's MAC address (under "Cell:", AFAIR) your client is not connected. In this case, please switch on debugging in the driver by: iwpriv wlan0 set_debug 0x180003 iwconfig wlan0 essid linksys ifconfig wlan0 up and look into the syslog again. It should contains add. debug msg now. Post them. /Jörg P.S. Please avoid full quotes of previous postings, edit them. Otherwise it's difficult to find the new text.