Description of problem: I am running F8 on a Thinkpad T60 with iwl3945. When using a wireless network (either WEP or WPA), I will sometimes, seemingly randomly, lose my network connection. Then, NetworkManager will try to re-connect, fail, and prompt me for the WEP/WPA key that it already should have, since it was previously logged in. When I enter the WEP/WPA key, it fails to re-connect to the network and keeps prompting me for the key repeatedly. This error happens at random, and my computer can go for hours before I see this happen. If I reboot, I can re-connect to the network fine again. I also don't experience this error with RHEL 5. Version-Release number of selected component (if applicable): NetworkManager-0.7.0-0.6.7.svn3235.fc8 iwl3945-firmware-2.14.1.5-2 kernel-2.6.24.4-64.fc8 How reproducible: Not that easy to reproduce Steps to Reproduce: 1. Connect to a WEP/WPA protected wireless network 2. Use the network/system and wait several hours (can be many hours) 3. Actual results: System looses network connection and can't reconnect Expected results: System doesn't lose connection and can reconnect if it does lose the connection Additional info:
You should provide more info like /var/log/messages and /var/log/wpa_supplicant from when such disconnections happen.
I use an Intel ABG 3945 Wireless Card which uses the iwl3945 driver and for me it works perfectly.The following are the versions i use NetworkManager-0.7.0-0.6.7.svn3370.fc8 iwl3945-firmware-2.14.1.5-2 kernel-2.6.24.5-85.fc8 However i guess you could do this try disabling ipv6 in firefox if you are not able to view the webpages alone and try using peer-dns in the resolv.conf and have you enabled the eth0 and wlan0 at startup itself if yes you could try disabling the device during start up and see. However you could give us more info on the bug which would enable us to isolate the problem.
This bug needs more info and hence changing the status to NeedInfo. Cheers Balaji
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.