My 3 problems

Cotobear · 11-20-2007, 03:38 AM

I think I may have found the problem. Now that WPA_supplicant is running, it seems to be timing out before it connects to the network. Specifically, wpa_cli is listing:
Authentication with 00:0d:88:98:20:36 timed out.

Further, the wireless is flashing for a few seconds, then stops for a second, than flashes again for a few seconds, which seems to be saying that it's trying to connect at least.

Running wpa_gui shows the status as going from associated to"group_handshake" before disconnecting itself.

It also seems like the first time it tries to connect, whatever the timeout is set to be is a little higher than on the subsequent retries.

I read the wpa_supplicant troubleshooting area that you wrote and it suggested to put WLAN_WPAWAIT[0]=30. I tried this, but it seems to not have worked in that the timeouts are still occuring... and nevermind... heheh, managed to get it working on a restart.

However it still failed to connect the first time and connected on the retry (perhaps by luck that time?) Or does the WLAN_WPAWAIT affect the retry time?

As for,
ifconfig -a
iwconfig
lspci -v | egrep "(Wireless|Net)".

I'm not sure you still require these? However just in case:

lspci -v | egrep "(Wireless|Net)"
-- yields nothing, however I'm using a USB key, could this be the reason?

lsusb yields the device as:
Bus 1 Device 2: ID 07d1:3a08 D-Link System

ndiswrapper -l lists the device as present

ifconfig -a:

Code:

eth0      Link encap:Ethernet  HWaddr 00:0B:DB:9D:04:53  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:1B:11:1E:BE:AF  
          inet addr:192.168.0.108  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:11ff:fe1e:beaf/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:400 errors:0 dropped:0 overruns:0 frame:0
          TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:128532 (125.5 KiB)  TX bytes:5069 (4.9 KiB)

iwconfig (truncated to relevant part):

Code:

wlan0     IEEE 802.11g  ESSID:"HomeM"  Nickname:"slackware"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:0D:88:98:20:36   
          Bit Rate=108 Mb/s   
          Encryption key:1306-E650-49A3-E28A-7A95-861C-C2C5-39D0-2532-CA3B-E72D-FCF0-4737-5ABC-227F-3F0A   Security mode:restricted
          Power Management:off
          Link Quality:59/100  Signal level:-58 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Again, thank you for the help,
Coto

Cotobear · 11-20-2007, 03:48 AM

Quote:

Originally Posted by BCarey

You don't want to keep commenting and uncommenting this line. wpa_supplicant can also handle unprotected (and WEP) networks. That's why you have multiple network sections in your wpa_supplicant.conf.

Brian

Sorry BCarey, I didn't realize that what you were saying is that wpa_supplicant would load automatically upon booting up the system. My confusion was with the fact that I failed to boot up the system after uncommenting this line, and that's what I was getting the errors.

My bad.

Alien Bob · 11-20-2007, 03:50 AM

Good! Looks all OK to me now.

Eric

Cotobear · 11-20-2007, 03:59 AM

Just a follow up on that WPA_WPAWAIT question. What does it affect exactly?

Thanks in advance,
Cotobear

Alien Bob · 11-20-2007, 04:19 AM

Quote:

Originally Posted by Cotobear

Just a follow up on that WPA_WPAWAIT question. What does it affect exactly?

Thanks in advance,
Cotobear

It extends the time the rc.wireless script waits to give the wpa_supplicant daemon a chance to associate. The default wait time is 10 seconds which can be too short for certain card / Access Point combinations.

Eric