Red Hat Bugzilla – Bug 1011138
ipw2200 fails to complete DHCP after associating to RSN network
Last modified: 2014-04-22 16:28:23 EDT
Description of problem:
I have wireless set up to start automatically, or in networkmanager parlance, it is managed. It was working fine (came up connected at login) until the last kde-redhat update to 4.11.1 about 10 days ago.
I should add that this doesn't appear to be limited to secured connections. I haven't experimented long enough with unsecured, but I noticed the drops there, too.
Version-Release number of selected component (if applicable):
Boot computer, program tries endlessly to start network, finally fails and displays a red icon.
Steps to Reproduce:
I have noticed that when open the network configuration dialogue and change the wpa2 password and change it on the router, I can establish a connection, but it is dropped after about 5-10 minutes and cannot be reestablished. Reboot doesn't reestablish the configured behaviour of connecting at login, either. I have to continually change the router password and reboot the computer. I cannot get a connection, if I just change the password and click connect. A reboot is required, and it only connects for a few minutes before dropping again, ad infinitum.
With unsecured connections, I can establish a connection by clicking the icon, but it is dropped and I need to reboot to reconnect. Login/out doesn't work.
I have yum erased kde-plasma-networkmanagement after learning of (by conincidence) and installing kde-plasma-nm and the wireless problem persists, as noted above.
I no longer think this is a kde-plasma network problem. The problem is also in gnome.
I have, thus, changed the component to NetworkManager. I hope this is correct.
NetworkManager-0.9.8.2-8.git20130709.fc19.[x86_64/i686] - mainly i686, since I don't have wireless on the desktop computer, only on the laptop
The message that appears on the screen after login is:
Wireless Interface (wlp2s4) - Failed to activate
IP configuration was unavailable
nm-tool shows that the network is active, etc., but no IP address is ever established and then wireless becomes unusable.
Can you attach the output of 'journalctl -b -u NetworkManager' ?
Created attachment 803614 [details]
requsted output of journalctl -b -u NetworkManager with only wireless connected
I noticed numerous killswitch lines. I want to assure you that the network enable button on the laptop is switched ON.
It looks like things are working OK when connecting to the access point, but like you say, no IP address is ever obtained via DHCP. Check your firewall rules to make sure they aren't disallowing DHCP.
But, I also notice you're using an 'ipw2200' (or 2915) device. That device hasn't seen much love upstream in the kernel in quite some time, so it's also possible that the ipw2200 driver might be broken too. That's actually the most likely possibility, so I'm moving it to the kernel component so they can debug the issue there.
For the kernel team: looks like association works correctly, as the supplicant does get connected. But data frames do not appear to work, since DHCP does not get a response.
Sep 26 15:44:16 lap NetworkManager: <info> (wlp2s4): supplicant interface state: scanning -> associating
Sep 26 15:44:16 lap NetworkManager: <info> (wlp2s4): supplicant interface state: associating -> associated
Sep 26 15:44:16 lap NetworkManager: <info> (wlp2s4): supplicant interface state: associated -> 4-way handshake
Sep 26 15:44:17 lap NetworkManager: <info> (wlp2s4): supplicant interface state: 4-way handshake -> completed
Sep 26 15:44:17 lap NetworkManager: <info> Activation (wlp2s4/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'dutycalls'.
Sep 26 15:44:40 lap dhclient: DHCPDISCOVER on wlp2s4 to 255.255.255.255 port 67 interval 13 (xid=0x4af1233e)
Sep 26 15:44:53 lap dhclient: DHCPDISCOVER on wlp2s4 to 255.255.255.255 port 67 interval 14 (xid=0x4af1233e)
Sep 26 15:45:02 lap NetworkManager: <warn> (wlp2s4): DHCPv4 request timed out.
I don't know how to check the firewall rules. I never changed a thing, so it should be just the way it comes 'out of the box'. I don't think that's it, but tell me how to check it.
Yes, I am using ipw2200. I never selected it, the installer or whatever selected it automatically. Everything was working just great until about 10-12 days ago, then, suddenly no more wireless. Either a kernel update or a ipw2200-firmware update or a NetworkManager update messed up.
If you want me to use a different device driver, just tell me how to get my built-in laptop wireless working with the new driver.
It's still not working :-(
I have reinstalled my system and am now using Fedora 20ß.
There has been no change in this issue! It has metastasized to infect the new release :-(
Update: still doesn't work.
This serious issue is confirmed on a gateway AMD laptop with realtek RTL8192SE RevP wifi card also.
It stopped working after a kernel update in the fall on F19.
Still persistent in F20...
*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.
Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you experience different issues, please open a new bug report for those.
I updated the laptop to kernel-3.13.4-200.fc20 and I am still unable to get a wireless network connection.
I have since updated to kernel-3.13.5-200.fc20, but I didn't go through another shutdown and power up cycle to test it yet, but I don't feel optimistic. I will give it a try in a couple of days (I use the laptop daily in good weather, when I will be on the road a lot more).
I booted the laptop with the wired internet with the latest kernel-3.13.5-200.fc20 and then I disconnected the wire and...
...my wpa2-protected wireless WORKS!
This is the first time I have had a connection in 5 months and I am almost afraid to reboot the computer for fear of having it no longer work when the computer powers back up.
Okay, I rebooted the computer and I actually do have wireless upon login. The problem FINALLY appears to be successfully solved, thank God!
I noticed a small change:
Formerly, I used to log in and wireless was just there automatically, likely because it is set to connect automatically and it is managed by Network Manager.
Now, I log in and a password window opens up, asking for my password. Upon entry, the wireless network connects instantly.
I am not sure why the change. Either, it is a new protocol in Fedora 20 (remember that the last time this worked, we were still on Fedora 19), or else it could be the change from knetworkmanager to kde-plasma-nm. I don't mind having to open kwallet or pam or seahorse or whatever it is to get a connection, so long as IT WORKS.
Great job! Keep it up.
I do believe this fixed. It has been working for over a month, over numerous kernel updates.
Thanks for getting it solved.