|
Bugzilla – Full Text Bug Listing |
| Summary: | KNetworkManager fails to connect to unencrypted network for several times | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Grzegorz Kossakowski <registration> |
| Component: | Network | Assignee: | Jiri Benc <jbenc> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P3 - Medium | CC: | casualprogrammer, jrobiso2, lavrinenko_alex |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
NetworkManager log
dmesg output dmesg output after trying to connect using iw* commands NetworkManager log showing that problems with wifi are still there iw/if* commands failed, specifically dhcpd failed |
||
Seems like a driver issue to me. Could you please attach the output of dmesg after a failed connection attempt? I experience the same - this seems to be iwl3945 driver issue. 'iwlist wlan0 scan' takes long each time and frequently does not show my AP that is 2 meters away. I also have bunch of messages: ... wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6) ... in dmesg. Grzegorz, could you please provide the info requested in comment #1? Created attachment 218824 [details]
dmesg output
Helmut, sorry for delay.
I attached output of dmesg returned just after (first) attempt to connect using saved connection fails.
If you need more details don't hesitate to ask, I'll be responding more promptly now.
Really strange, dmesg shows some succeeded association attempts but NM seems to time out while waiting for an IP. Are you sure your AP is unencrypted? Could you please try if you can setup the connection without NM as root with a freshly booted system? - rcnetwork stop - ifconfig wlan0 up - iwconfig wlan0 essid <youressid> - wait a few seconds - dhcpcd wlan0 If dhcpcd returns you should have got an IP. Please verify this using ifconfig wlan0. (In reply to comment #2 from Alexander Lavirnenko) > I experience the same - this seems to be iwl3945 driver issue. 'iwlist wlan0 > scan' takes long each time and frequently does not show my AP that is 2 meters > away. I also have bunch of messages: Alexander, is your AP unencrypted too? Mine has no encryption, just MAC-based access control. ESSID is not hidden. Please see my earlier bug https://bugzilla.novell.com/show_bug.cgi?id=377560 that is very similar to this one. Thanks Alexander. Having the demsg-output reveals that the issue you've reported in bug 377560 is most likely the same. *** Bug 377560 has been marked as a duplicate of this bug. *** Mine AP is uncrypted too. I've followed instructions from comment #5 and my connection works just fine. See: linux:~ # ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr 00:1B:77:89:7B:30 inet addr:192.168.0.118 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21b:77ff:fe89:7b30/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:780 (780.0 b) TX bytes:6227 (6.0 Kb) However, this does not imply that this method of connecting is reliable. My previous delay in response was caused mainly by the fact that about ten attempts (each separated by reboot of a machine) to connect resulted in success so I couldn't provide any logs for analyse. This means, that there are random problems with connecting so we can be never sure if second method turned to be successful only because of coincidence... I have some others tasks now, I'll do some more extensive testing at the late evening. Created attachment 218974 [details]
dmesg output after trying to connect using iw* commands
I managed to make cmd line method fail. I attach new output of dmesg.
Not sure whether this is the proper Bug to add to, correct me if I'm wrong. While travelling I tried to connect to an unencrypted network with NetworkManager without success, then connection was made using ifup. After a while of operation connection was terminated and could not be restored for the rest of the day ( > 8h ) neither with NetworkManager nor with ifup. After letting the issue rest overnight, on booting this morning NetworkManager now connects to the AP. Not sure what kind of information to provide for further examination. This is a Siemens Fujitsu Amilo Si1520 with Intel ipw3945 running RC1 / GNOME Please update from factory to kernel-default-2.6.26-2/NetworkManager-0.7.0.r3783-5/NetworkManager-kde-0.7r826733-10 and re-check. Things seem to work for me after tonight's update. Question: Was this a fresh install, or an upgrade? If it was an upgrade, try replacing the /etc/sysconfig/network/config and ./dhcp files with the ones from /var/adm/fillup-templates. I recently found that the iwl driver is MUCH more sensitive to changes in timings, hold times, "drop connections if . . ", .etc stuff than the ipw driver ever was. Once I replaced my configs with the new ones (which really just reset all the values to default and added some nice commentary) most of my troubles with wireless went away. That was upgrade. Everything with wi-fi now works as expected, without files' tossing. Anything new from the bug reporters after the latest round of updates? After 2 months maybe its time to move this to NORESPONSE. If there is anybody still seeing this problem, could you please try to disable hw scanning: rmmod iwl3945 modprobe iwl3945 disable_hw_scan=1 (you may need to restart both NetworkManager and knetworkmanager afterwards) and report whether it changes anything? Created attachment 244715 [details]
NetworkManager log showing that problems with wifi are still there
At the moment I don't have access to unencrypted network but I use encrypted one instead. I decided to attach NetworkManager log because it contains information about exactly the same issues I had with unencrypted networks so I guess the reason is the same.
Issues are:
a) connection can "die" from time to time and then there is no way you can reconnect
b) sometimes wifi does not detect network at all
c) most of the time I had to try many times (including rebooting machine and deleting saved connection) before it connects successfully.
All this is happening at random times. Sometimes I can work with wifi for the whole day without a problem but often it dies after an hour or two.
I'll have an access to my unecpryted network over the weekend so I can provide more details if you need.
I have fresh kernel and NetworkManager packages from update repository for 11.0 version.
Thanks, that helped eliminating one possible cause. Ad comment #11: analyzing the log more carefully, it seems NetworkManager is still getting in your way. Disabling it by rcnetwork stop before trying the manual connection would most likely lead to a success. You don't need to try that, as I'm quite sure about it. Of course, if you prove me wrong, it will be interesting :-) I have a question about the initial description: how do you connect to the saved network? When you click on the knetworkmanager icon, do you see the network directly in the menu, or do you select the network in "Connect to other network" submenu? Jiri, Actually, I cannot reproduce this problem for last two days but this does not imply anything, IMHO. Once I hit this problem again I'll try to make sure that NetworkManager is not running. I tried all possible methods: auto connect (in case that knetworkmanager detects network at all), connecting using main menu and enforcing connection using "Connect to other network". In the order I have given. Of course, I didn't see any difference between this methods. If one failed, then any other would fail as well. Hello, Yesterday I managed to reproduce my problem both with knetworkmanager and iw*/if* commands. The problem was that my network was not discovered even if others were. After disabling NM, I tried iwconfig wlan0 scan but it didn't return my network as well. Actually, I have no more details to report because I didn't know what kind of information I should collect. This is issue is extremely annoying because it's hard to reproduce (sometimes everything works for 20-30 reboots) but usually it hits me when I urgently need my wifi working... Guys, Is there any chance to get this fixed before 11.1 release? If you are busy maybe you could point me to upstream driver maintainers so I could work with them directly? I believe that my wifi card is quite popular one and having driver working properly is a must. It's quite possible we have a problem in both knetworkmanager and the driver. Upstream bugzilla for the driver is at http://www.intellinuxwireless.org/bugzilla/ - but you should reproduce the problem on the latest vanilla kernel first. Grzegorz, please double check and be 100% sure that you have NetworkManager stopped ("rcnetwork stop" as root) before trying to connect via command line. This is extremely important.
We may see two different issues together here. Are you sure the problem shows up when using iw* commands and NetworkManager is stopped?
Jiri, I'm almost sure that NetworkManager was not running when I observed problems with detecting networks. I have additional question: it's rather common that after suspending my laptop and recovering it from that state I experience various problems with reconnecting to to the network I was connected previously. Since for me it's easier to reproduce my problems using suspending thus I would prefer this route. Is it fine with you? BTW. My gut feeling is that we observe different bugs because symptoms I see are really diverse. Just a quick note: I'm using my laptop a lot these days so it's a perfect chance for me to check if this problem is still present with 11.1 final. I must admit that it was only once that I had a small problem with connecting to network during one week of connecting to different networks. Give me one more week, if there are no more problems then I think we will have to close this report. Really helpful comment (#27), is this an issue or a non-issue ? Created attachment 266663 [details]
iw/if* commands failed, specifically dhcpd failed
Casual J. Programmer: I just wanted to let all interested know that I didn't forget about this bug report. It takes me a lot to respond to inquiries because of two reasons:
1. It was really hard to reproduce this bug on will (more details below)
2. I'm traveling a lot these days so it's not that everyday I can try new suggestions with reliable and trusted wifi networks.
Anyway, I think I've found something interesting. The wifi does not work for me only if power adapter is unplagged. I've tried ten reboots with power plugged-in and ten without. The results are:
1. unplugged: 1 successful connect, 9 unsuccessful
2. plugged-in: 9 successful connects, 1 unsuccessful
After finding that, testing any suggestions will be much, much easier. I wonder how I missed this correlation earlier.
I attach a log for if/iw* commands try when power was unplagged. I forgot to save dmesg output, however. Do you need it?
Forgot to remove NEEDINFO. Ok. Seems that nobody cares about this report. I'll create a new report with more detailed info of the issue as this report contains too much of confusing information. I suggest to close this one. Just to follow suggestion from #31 closing. |
Created attachment 217985 [details] NetworkManager log Hello, I noticed quite annoying problem with wireless networking. It appears that KNetworkManager has some troubles with connecting to previously saved network. Usually, I had to made about 2-3 attempts in order to connect to saved network. Sometimes it gets so stuck that the only way to connect is to remove saved connection and add it again. I attach NetworkManager log; here is information about my wireless card: linux:~ # hwinfo --wlan 07: PCI 200.0: 0282 WLAN controller [Created at pci.310] UDI: /org/freedesktop/Hal/devices/pci_8086_4222 Unique ID: y9sn.trkNZjh+GB2 Parent ID: z8Q3.yjCEx5JbDxB SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Model: "Hewlett-Packard Company Compaq 6710b" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x4222 "PRO/Wireless 3945ABG Network Connection" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x135c "Compaq 6710b" Revision: 0x02 Driver: "iwl3945" Driver Modules: "iwl3945" Device File: wlan0 Features: WLAN Memory Range: 0xf4000000-0xf4000fff (rw,non-prefetchable) IRQ: 217 (no events) HW Address: 00:1b:77:89:7b:30 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 34 36 38 40 42 44 46 48 52 56 60 64 100 104 108 112 116 120 124 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.17 5.18 5.19 5.2 5.21 5.22 5.23 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d00004222sv0000103Csd0000135Cbc02sc80i00" Driver Info #0: Driver Status: iwl3945 is active Driver Activation Cmd: "modprobe iwl3945" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #20 (PCI bridge)