Re: Re: Kernel 2.6 and Linksys WUSB11 2.8 error...

Hi,

On Thu, 8 Jan 2004, Robert Burns wrote:

> Well, I guess the driver is working now (???). wlan0 is now being
> registered correctly. I still can't ping my router. Here's what I did:
>
> iwconfig wlan0 essid myid channel 8
> ifconfig 192.168.0.5 [that address isn't being used on my network]

the default mode of the driver is ad-hoc, try
	 iwconfig wlan0 mode managed essid myid
(channel is irrelevant for managed mode) to connect to an AP.

> I then tried pinging my router (192.168.0.1), but I got a host could not
> be reached message. Same thing for apple.com and other addresses. I
> tried this:
>
> iwconfig wlan0
>
> All of the settings are correct for my router/AP. However, signal
> strength was 120 or so, and link quality was 0. Also, the Cell number
> did not correspond to my AP's MAC ID.
>
> dmesg looks fine. I'm sort of a n00bie at networking, so can someone
> tell me what I need to do in order to be able to ping my router? If I

assuming that you see the MAC address of your USB adapter in the syslog
(i.e. the driver started correctly) and the "config descr too short" error
disappeared and the above didn't help, try this:

- read http://at76c503a.berlios.de/support.html#trouble :-)
- set module param debug=0x180003 for at76c503
- reset your essid with iwconfig, reopen the netdev wlan0 if necessary
- look into the syslog (with kern.debug included!) for the result of
  the scan ("wlan0 BSS table"). Does it contain your AP?
  If not, enlarge the channel scan times (or check if SSID hiding is on in
  the AP - switch it off). If yes, the syslog should tell you, why it
  wasn't choosen with the above debug setting.
- post your syslog.

/Jörg