LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Wireless Stopped Working on Laptop - Fails to get IP address (http://www.linuxquestions.org/questions/slackware-14/wireless-stopped-working-on-laptop-fails-to-get-ip-address-892731/)

statguy 07-20-2011 08:52 AM

Wireless Stopped Working on Laptop - Fails to get IP address
 
Hello.

My wireless networking is broken on my ThinkPad T60. It has worked in the past, but no longer. My OS is Slack 12.2 and I'm using Wicd 1.5.6. Here is a description of the problem.

When I open the Wicd window, it displays the wireless networks it can see, as it always has. When I try to connect to a network, even one I have successfully connected to in the past, it sits for a long time trying to get an IP address and then fails to connect.

I could use some help debugging this. Here are the sanitized lines from wicd.log from the failed attempt, followed by my successful wired re-connection.

Code:

2011/07/20 09:24:47 :: Setting hidden essid****
2011/07/20 09:24:53 :: Connecting to wireless network ****
2011/07/20 09:24:53 :: Putting interface down
2011/07/20 09:24:53 :: Releasing DHCP leases...
2011/07/20 09:24:53 :: Setting false IP...
2011/07/20 09:24:53 :: Stopping wpa_supplicant and any DHCP clients
2011/07/20 09:24:53 :: Flushing the routing table...
2011/07/20 09:24:53 :: Putting interface up...
2011/07/20 09:24:53 :: Running DHCP
2011/07/20 09:25:53 :: Broadcasting DHCP_DISCOVER
2011/07/20 09:25:53 ::
2011/07/20 09:25:53 :: timed out waiting for a valid DHCP server response
2011/07/20 09:25:53 ::
2011/07/20 09:25:53 ::
2011/07/20 09:25:53 :: DHCP connection successful
2011/07/20 09:25:53 :: Connecting thread exiting.
2011/07/20 09:26:30 :: Putting interface down
2011/07/20 09:26:30 :: Releasing DHCP leases...
2011/07/20 09:26:30 :: Setting false IP...
2011/07/20 09:26:30 :: Stopping wpa_supplicant and any DHCP clients
2011/07/20 09:26:30 :: Flushing the routing table...
2011/07/20 09:26:30 :: Putting interface up...
2011/07/20 09:26:30 :: Running DHCP
2011/07/20 09:26:35 :: Broadcasting DHCP_DISCOVER
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: broadcastAddr option is missing in DHCP server response.
Assuming x.x.x.255
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: dhcpIPaddrLeaseTime=81411 in DHCP server response.
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: DHCP_OFFER received from  (x.x.x.9)
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: Broadcasting DHCP_REQUEST for x.x.x.202
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: DHCP_ACK received from  (x.x.x.9)
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: Broadcasting ARPOP_REQUEST for x.x.x.202
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: Broadcasting DHCP_DISCOVER
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: broadcastAddr option is missing in DHCP server response. Assuming x.x.x.255
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: dhcpIPaddrLeaseTime=81411 in DHCP server response.
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: DHCP_OFFER received from  (x.x.x.9)
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: Broadcasting DHCP_REQUEST for x.x.x.202
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: dhcpIPaddrLeaseTime=86400 in DHCP server response.
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: DHCP_ACK received from  (x.x.x.9)
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: Broadcasting ARPOP_REQUEST for x.x.x.202
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 ::
2011/07/20 09:26:35 :: DHCP connection successful
2011/07/20 09:26:35 :: Connecting thread exiting.

Also, iwconfig returns the following (ran while connected via wired connection).

Code:

# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0    IEEE 802.11abgn  ESSID:"SMH_Guest"
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated
          Tx-Power=23 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2352 B
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

irda0    no wireless extensions.

What other information do you need to help me find the problem?

Thanks for your help.

Robert.Thompson 07-20-2011 09:19 AM

I don't know if this will help but here is my output from my lenovo X61 Laptop:

Code:

root@lenovo:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0    IEEE 802.11abg  ESSID:"BELL074" 
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:1E:C7:80:7C:69 
          Bit Rate=54 Mb/s  Tx-Power=15 dBm 
          Retry  long limit:7  RTS thr:off  Fragment thr:off
          Encryption key: xxxxxxxxxxxxxx
          Power Management:off
          Link Quality=52/70  Signal level=-58 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:24  Missed beacon:0

root@lenovo:~#

I am using Wicd 1.7.0

I noticed, in your output, that you have no 'Access Point'.

Perhaps, the wifi card is turned off?

HTH,

statguy 07-20-2011 10:51 AM

I suspect that the access point would not get a value unless the wifi is connected. Since I can't connect, I cannot run iwconfig while connected to test this.

Although my T60 has a switch, it is ignored by the wireless driver. The fact that I can see wireless networks suggests that the card is on.

Robert.Thompson 07-20-2011 07:20 PM

What about uninstalling your existing Wicd and installing a new version?

Actually, now that the memory popped back into my brain, I once had the exact same problem as you describe:

Code:

When I open the Wicd window, it displays the wireless networks it can see, as it always has. When I try to connect to a network, even one I have successfully connected to in the past, it sits for a long time trying to get an IP address and then fails to connect.

I could use some help debugging this. Here are the sanitized lines from wicd.log from the failed attempt, followed by my successful wired re-connection.

My problem was that I had not set up the properties correctly. Either I was not using WEP or I had not entered the key correctly but the answer was to reset all the properties correctly. The symptom was exactly as you describe.

statguy 07-20-2011 07:37 PM

Quote:

Originally Posted by Robert.Thompson (Post 4420665)
What about uninstalling your existing Wicd and installing a new version?

Actually, now that the memory popped back into my brain, I once had the exact same problem as you describe:

Code:

When I open the Wicd window, it displays the wireless networks it can see, as it always has. When I try to connect to a network, even one I have successfully connected to in the past, it sits for a long time trying to get an IP address and then fails to connect.

I could use some help debugging this. Here are the sanitized lines from wicd.log from the failed attempt, followed by my successful wired re-connection.

My problem was that I had not set up the properties correctly. Either I was not using WEP or I had not entered the key correctly but the answer was to reset all the properties correctly. The symptom was exactly as you describe.

Well, I could try a new version, but I'd like to understand why it stopped working in the first place.

In the case of the network I attempted to connect to in my example, there is no key to enter. In terms of the network in my home, it used to work with the same settings that are there now.

statguy 07-26-2011 06:46 PM

Just a quick update. I did an upgrade to version 1.5.9 of wicd from the slack repository. I connected to my home network, got an IP address, but nothing would route. In the "External Programs" tab of the preferences box, I noticed that at some point in the past, I must have changed the DHCP client from Automatic to dhcpcd. When I changed this to Automatic, I successfully connected, and even posted this message wirelessly.

statguy 07-27-2011 09:34 AM

Quote:

Originally Posted by statguy (Post 4426096)
Just a quick update. I did an upgrade to version 1.5.9 of wicd from the slack repository. I connected to my home network, got an IP address, but nothing would route. In the "External Programs" tab of the preferences box, I noticed that at some point in the past, I must have changed the DHCP client from Automatic to dhcpcd. When I changed this to Automatic, I successfully connected, and even posted this message wirelessly.

I got excited too soon. After I was connected to my home network for a few minutes, my traffic again started having routing problems. When I'd connect to a website I had just previously connected to, it would take a long time to look up the address. Eventually, all traffic stopped and I could not even connect to my router. I don't think it's a router problem because I have several wired connections (and even reconnecting the laptop to the cat5 restored my connectivity) and my wife's laptop is wireless, all with no problems.

This morning, I again tried a wireless network in the office. It is open with no encryption. I could not get an IP address. Again, I have used this network in the past.

I will try booting the laptop in windows to see if it's a wireless card issue. Meanwhile, any other thoughts?

bonixavier 07-27-2011 11:44 AM

I'm interested in the solution to this problem because I get exactly the same problems when trying to connect to unauthenticated essids. WPA works fine and I haven't tested WEP. I'm running -current.

igadoter 07-29-2011 04:40 PM

Your device might be broken broken. For me it seems that USB wifi cards work well ca. 2 years. Try different adapter to be sure it is not a hardware fault.

zer0.0? 07-29-2011 05:26 PM

I've never used wicd... do you maybe want to try connecting from the command line? not sure if that will solve it but it cant hurt to try.

if your network doesn't need a password, then I just connect with:

$ iwconfig wlan0 essid foo
...foo in your case would be SMH_Guest it looks like, but any essid is viable, then

$dhcpcd wlan0

I'm just curious of what the output of this is. If this and wicd do not work, it very well may be a hardware malfunction

zer0.0? 07-29-2011 05:32 PM

oh, and bonixavier,

I actually have the opposite problem, I have difficulty connecting to essid's that require a key. how do you connect in this situation? I'm doing everything from the command line, what happens is I execute:

$ iwconfig wlan0 essid arbitrary_essid
$ iwconfig wlan0 key associated_key_to_arbitrary_essid
$ dhcpcd wlan0

and it seems to always fail. sort of frustrating when it connects to unauthorized networks just fine. any advice is much appreciated

statguy 07-29-2011 05:47 PM

Quote:

Originally Posted by zer0.0? (Post 4428885)
I've never used wicd... do you maybe want to try connecting from the command line? not sure if that will solve it but it cant hurt to try.

if your network doesn't need a password, then I just connect with:

$ iwconfig wlan0 essid foo
...foo in your case would be SMH_Guest it looks like, but any essid is viable, then

$dhcpcd wlan0

I'm just curious of what the output of this is. If this and wicd do not work, it very well may be a hardware malfunction

OK. Here are the results at home, which I can connect to, the connection degrades. Note that my home network uses WEP.

Code:

# iwconfig
lo        no wireless extensions.

irda0    no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0    IEEE 802.11abgn  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Tx-Power=23 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2352 B
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

# iwconfig wlan0 essid myessid key s:mykey
root@omega:~# iwconfig
lo        no wireless extensions.

irda0    no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0    IEEE 802.11abgn  ESSID:"myessid"
          Mode:Managed  Frequency:2.452 GHz  Access Point: 00:18:E7:D3:7C:67
          Bit Rate=1 Mb/s  Tx-Power=23 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2352 B
          Encryption key:5861-7269-614C-6569-6768-3731-37  Security mode:open
          Power Management:off
          Link Quality=84/100  Signal level:-41 dBm  Noise level=-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

# dhcpcd wlan0
Broadcasting DHCP_DISCOVER
dhcpIPaddrLeaseTime=86400 in DHCP server response.
dhcpT1value is missing in DHCP server response. Assuming 43200 sec
dhcpT2value is missing in DHCP server response. Assuming 75600 sec
DHCP_OFFER received from  (192.168.1.1)
Broadcasting DHCP_REQUEST for 192.168.1.194
dhcpIPaddrLeaseTime=86400 in DHCP server response.
dhcpT1value is missing in DHCP server response. Assuming 43200 sec
dhcpT2value is missing in DHCP server response. Assuming 75600 sec
DHCP_ACK received from  (192.168.1.1)
Broadcasting ARPOP_REQUEST for 192.168.1.194

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1a:6b:35:04:00
          inet addr:192.168.1.192  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21a:6bff:fe35:400/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:4589 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3413 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1661868 (1.5 MiB)  TX bytes:484537 (473.1 KiB)
          Memory:ee000000-ee020000

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:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1300 (1.2 KiB)  TX bytes:1300 (1.2 KiB)

wlan0    Link encap:Ethernet  HWaddr 00:19:7e:40:e8:7e
          inet addr:192.168.1.194  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::219:7eff:fe40:e87e/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:62 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8626 (8.4 KiB)  TX bytes:2700 (2.6 KiB)

wmaster0  Link encap:UNSPEC  HWaddr 00-19-7E-40-E8-7E-77-6C-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING 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)

I will need to wait until Tuesday to try the WLAN without a key.

rc nai 07-30-2011 12:44 AM

By any chance did you edit the rc.inet1.conf file in /etc.rc.d/? If so, you might want to read this:
http://slackware.osuosl.org/slackwar...ADME.SLACKWARE

Here's an alternative for you to try if wicd doesn't work. Take your time and read, you'll learn a lot :)
http://alien.slackbook.org/dokuwiki/...e:network#wicd

statguy 07-30-2011 07:07 PM

This gets more and more puzzling. Last night (July 29) I started wireless at home manually. It stayed connected all evening (several hours) with no issue. Today (July 30) I connected using wicd. It has remained stable all afternoon.

I guess this rules out hardware? I will still try connecting to the open network manually next week and report back.

statguy 08-02-2011 07:22 AM

Quote:

Originally Posted by zer0.0? (Post 4428889)
oh, and bonixavier,

I actually have the opposite problem, I have difficulty connecting to essid's that require a key. how do you connect in this situation? I'm doing everything from the command line, what happens is I execute:

$ iwconfig wlan0 essid arbitrary_essid
$ iwconfig wlan0 key associated_key_to_arbitrary_essid
$ dhcpcd wlan0

and it seems to always fail. sort of frustrating when it connects to unauthorized networks just fine. any advice is much appreciated

OK. I've tried this on the open network at my office with decidedly different results.

Code:

# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0    IEEE 802.11abgn  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Tx-Power=23 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2352 B
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

irda0    no wireless extensions.

# iwconfig wlan0 essid testessid
# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0    IEEE 802.11abgn  ESSID:"testessid"
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated
          Bit Rate:5.5 Mb/s  Tx-Power=23 dBm
          Retry min limit:7  RTS thr:off  Fragment thr=2352 B
          Encryption key:off
          Power Management:off
          Link Quality=68/100  Signal level:-51 dBm  Noise level=-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

irda0    no wireless extensions.

# dhcpcd wlan0
Broadcasting DHCP_REQUEST for 192.168.1.194
timed out waiting for DHCP_ACK response
Broadcasting DHCP_DISCOVER
timed out waiting for a valid DHCP server response

So, I notice a couple of things. When I attempt to connect, no access point is acquired. Is this because there are multiple access points reachable and I need to specify a specific one to connect to? I'm sure there is no key to access this WLAN because my Blackberry connects with no issue.

Obviously, the dhcpcd displays failure to contact a server and obtain an address.


All times are GMT -5. The time now is 12:56 AM.