You are not logged in.
Okay, so as you might have noticed with my previous topic on this infernal wlan card it's causing trouble again.
This time however I cannot even begin to fathom the issue.
the actual issue is coming up but first some notes on my usage scenario
[root@zero-dev /]# uptime
04:40:01 up 31 days, 11:49, 4 users, load average: 1.22, 0.96, 0.84
This happened about 12 hours ago so let's assume it happened at 30 days uptime, during this time there has not been any hardware or software changes as I've not needed to perform any.
The WLAN has been working for the most part (with at most a few minutes of downtime every now and then) during this time as well, but when it finally broke down and refused to connect (in wicd I get "connection failed: unable to obtain ip address")
as the wicd line isn't all that useful let's check the log (truncated down to the relevant section):
2014/10/15 01:03:57 :: No wired connection present, attempting to autoconnect to wireless network
2014/10/15 01:03:58 :: trying to automatically connect to...MOTOROLA-80623
2014/10/15 01:03:58 :: Connecting to wireless network MOTOROLA-80623
2014/10/15 01:03:58 :: Putting interface down
2014/10/15 01:03:58 :: Releasing DHCP leases...
2014/10/15 01:03:58 :: Setting false IP...
2014/10/15 01:03:59 :: Stopping wpa_supplicant
2014/10/15 01:03:59 :: Flushing the routing table...
2014/10/15 01:03:59 :: Putting interface up...
2014/10/15 01:04:01 :: Generating psk...
2014/10/15 01:04:01 :: Attempting to authenticate...
2014/10/15 01:04:03 :: Running DHCP with hostname zero-dev
2014/10/15 01:04:03 :: dhcpcd[939]: version 6.4.7 starting
2014/10/15 01:04:03 ::
2014/10/15 01:04:03 :: dhcpcd[939]: DUID 00:01:00:01:1b:35:7b:d5:1c:65:9d:8a:dc:22
2014/10/15 01:04:03 ::
2014/10/15 01:04:03 :: dhcpcd[939]: wlp6s0: IAID 9d:8a:dc:22
2014/10/15 01:04:03 ::
2014/10/15 01:04:03 :: dhcpcd[939]: wlp6s0: soliciting an IPv6 router
2014/10/15 01:04:03 ::
2014/10/15 01:04:04 :: dhcpcd[939]: wlp6s0: soliciting a DHCP lease
2014/10/15 01:04:04 ::
2014/10/15 01:04:15 :: dhcpcd[939]: wlp6s0: no IPv6 Routers available
2014/10/15 01:04:15 ::
2014/10/15 01:04:33 :: dhcpcd[939]: timed out
2014/10/15 01:04:33 ::
2014/10/15 01:04:33 :: DHCP connection failed
2014/10/15 01:04:33 :: exiting connection thread
2014/10/15 01:04:33 :: Sending connection attempt result dhcp_failed
2014/10/15 01:10:12 :: rfkill: blocking wifi
2014/10/15 01:10:12 :: rfkill: blocking wlan
2014/10/15 01:10:12 :: rfkill: blocking wimax
2014/10/15 01:10:12 :: rfkill: blocking wwan
2014/10/15 01:10:13 :: rfkill: unblocking wifi
2014/10/15 01:10:13 :: rfkill: unblocking wlan
2014/10/15 01:10:13 :: rfkill: unblocking wimax
2014/10/15 01:10:13 :: rfkill: unblocking wwanwell that's rather useless, what about dmesg?
[2718042.329049] IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
[2718043.588218] r8169 0000:01:00.0 enp1s0: link up
[2718043.588232] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
[2718044.507777] wlp6s0: authenticate with cc:7d:37:82:b3:43
[2718044.517994] wlp6s0: send auth to cc:7d:37:82:b3:43 (try 1/3)
[2718044.519699] wlp6s0: authenticated
[2718044.519740] rtl8192ce 0000:06:00.0 wlp6s0: disabling HT/VHT due to WEP/TKIP use
[2718044.520852] wlp6s0: associate with cc:7d:37:82:b3:43 (try 1/3)
[2718044.523245] wlp6s0: RX AssocResp from cc:7d:37:82:b3:43 (capab=0x411 status=0 aid=3)
[2718044.523402] wlp6s0: associated
[2718044.523448] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready
[2718076.083839] wlp6s0: deauthenticating from cc:7d:37:82:b3:43 by local choice (Reason: 3=DEAUTH_LEAVING)
[2718076.116101] cfg80211: Calling CRDA to update world regulatory domainagain a rather useless block of information.
Well now, let's connect manually then, I configured wpa_supplicant according to the wiki and this is my current output:
[root@zero-dev wicd]# dhcpcd wlp6s0
dhcpcd[9493]: version 6.4.7 starting
dhcpcd[9493]: wlp6s0: adding address fe80::611d:a17e:7a1d:c20e
dhcpcd[9493]: if_addaddress6: Permission denied
dhcpcd[9493]: DUID 00:01:00:01:1b:35:7b:d5:1c:65:9d:8a:dc:22
dhcpcd[9493]: wlp6s0: IAID 9d:8a:dc:22
dhcpcd[9493]: wlp6s0: soliciting a DHCP lease
dhcpcd[9493]: wlp6s0: soliciting an IPv6 router
dhcpcd[9493]: timed out
dhcpcd[9493]: exitedaha! so it's attempting to utilize ipv6 for some arcane reason, even though it's used ipv4 fine up until now and even though my router does not support it.
very well, let's disable it.
sysctl -w net.ipv6.conf.all.disable_ipv6=1
sysctl -w net.ipv6.conf.default.disable_ipv6=1Okay, trying again!
well now, nothing changed.
let's restart wicd and see what happens
[2722515.928912] wicd[9318]: segfault at 0 ip 00007f70152a5055 sp 00007f700e020bb8 error 6 in libc-2.20.so[7f701520f000+199000]well now, that's one of many similar lines, all being wicd segfaulting.
apparently it doesn't like ipv6 being disabled, very well I'll enable it again.
sysctl -w net.ipv6.conf.all.disable_ipv6=0
sysctl -w net.ipv6.conf.default.disable_ipv6=0Aaand nothing happened.
At least the wired connection I plugged (after I realized I wouldn't be able to get the wireless running easily) and enabled through wicd didn't die with wicd.
In short: the wlan is broken, it died spontaneously and I don't know what to do, before you suggest "reboot" I'm quite against that, I don't treat symptoms I try to treat problems, rebooting fixes the symptom but whatever cased the error in the first place is still present and thus I cannot really use such a "solution".
I've read through the entire output of dmesg and cannot find any hint as to what caused the wlan to die, wicd.log has nothing relevant either
faillog only contains a long sequence of "^@^@^@^@^@^@^@^@" repeated over and over, same for lastlog
Any further assistance in diagnosing this problem would be greatly appreciated.
Offline
UPDATE:
I can connect using a static setup
i.e sudo dhcpcd -S ip_address=192.168.0.15/24 -S routers=192.168.0.1 -S domain_name_servers=8.8.8.8 wlp6s0
This is however not optimal nor remotely desireable, as per last post logs are still completely void of relevant data (and wicd is still dead).
Offline
UPDATE 2: I was forced to reboot because of stupidity, I don't know why or how but I had the idea that I could soft reset my system by doing a systemctl restart * while in the directory with all services... yeah, that didn't work out very well (it had the same outcome as kill 1 in the sense that the system entered runlevel 6 and shut down causing a reboot, the opposite of what I wanted)
The problem remains unsolved, my DHCP is still borked.
note to self: 5 am system administration is something I need to stop.
Last edited by CubeGod (2014-10-18 03:24:03)
Offline