On 08/02/2015 12:33 AM, auxsvr wrote:
What does /var/log/NetworkManager indicate about the connection attempts? Quite often here on 13.2 and on earlier versions before that, wpa_supplicant corrupts its memory and the only way to connect to certain WPA networks is by killing it, and Networkmanager or systemd automatically restart it and the connection proceeds as expected. Perhaps this is the same issue?
Most of it might as well be Greek to me. I had 'info' level debug enabled in the log file. The 'warn' level indications were: 2015-07-27T07:50:05.969002-05:00 alchemy NetworkManager[699]: <warn> failed to allocate link cache: (-10) Operation not supported ... 2015-07-27T07:50:06.046501-05:00 alchemy NetworkManager[699]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... 2015-07-27T07:50:06.047024-05:00 alchemy NetworkManager[699]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... ... 2015-07-27T07:50:06.072060-05:00 alchemy NetworkManager[699]: <warn> Trying to remove a non-existant call id. ... 2015-07-27T08:18:19.619986-05:00 alchemy NetworkManager[699]: <warn> Connection disconnected (reason -3) ... 2015-07-27T08:18:20.446230-05:00 alchemy NetworkManager[699]: <warn> Connection disconnected (reason -3) <repeated multiple times> I then have a break in the log from 7/27 to 8/1 when I returned from vacation for the time NetworkManager was killed to allow the connection to work. The connection was with a generic AP: Cell 03 - Address: 10:5F:06:C0:A6:28 Channel:11 Frequency:2.462 GHz (Channel 11) Quality=43/70 Signal level=-67 dBm Encryption key:on ESSID:"togetheragain" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=8002aaf88adbd086 Extra: Last beacon: 39ms ago IE: Unknown: 000D746F676574686572616761696E IE: Unknown: 010482848B96 IE: Unknown: 03010B IE: Unknown: 0706555320010B1E IE: Unknown: 200100 IE: Unknown: 2A0100 IE: Unknown: 2D1A2C001EFFFF0000000000000000000000000000A8000000000000 IE: Unknown: 32080C1218243048606C IE: Unknown: 3D160B000500000000000000000000000000000000000000 IE: Unknown: 480100 IE: Unknown: 7F0100 IE: Unknown: DD1E00904C332C001EFFFF0000000000000000000000000000A8000000000000 IE: Unknown: DD1A00904C340B000400000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: WPA Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: DD180050F2020101020003A4000027A4000042435E0062322F00 IE: Unknown: DD750050F204104A0001101044000102103B000103104700102444C9854279476A83A59E23B44F9D7F10210009416374696F6E74656310230007504B353030314110240003312E3010420005444D4136361054000800060050F2040001101100012010080002210C103C0001011049000600372A000120 IE: Unknown: DD050009860100 Nothing looked particularly odd about what the AP reported. After killing NetworkManager and issuing the commands: # wpa_supplicant -dddt -iwlp23s0 -c/etc/wpa_supplicant/wpa_supplicant.conf -Dwext -f /var/log/wpa_supplicant.log # iwconfig wlp23s0 essid "togetheragain" instantly the connection was made. Then following up with: # /sbin/dhcpcd -D -N -t 999999 -h alchemy -c /etc/sysconfig/network/scripts/dhcpcd-hook wlp23s0 & the dhcp address was acquired and resolve.conf modified to include both LAN and WAN Gateway IP, all was fine. The problem at home was due to the fact that resolv.conf was not updated on return and still contained the network LAN/WAN gateway addresses. Let me know if there is any other specific information I can provide that might be relevant to this issue. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org