You are not logged in.

#1 2017-09-13 21:38:44

nchishol
Member
Registered: 2016-06-13
Posts: 6

Wireless network connectivity sporadically drops

I am experiencing sporadic loss of internet connectivity when using my campus wireless network. Contacting university tech support yielded little more than "we do not offer Linux support". Others running Windows in my office are not experiencing problems. I have configured the connection (using NetworkManager through GNOME settings) according to the instructions provided by the university. Quoting them,

  • Security Type : WPA2-Enterprise

  • Encryption Type : AES

  • EAP Method : TTLS

  • Phase 2 (Inner Method) : PAP

  • Root CA Certificate(s) : Install AddTrust External CA Root (this root certificate is pre-installed on most OSes so you likely will not have to install it manually)

  • Anonymous Identity (Outer Identity) : Blank

After my connectivity drops, I am unable to load any webpages until reconnecting by clicking on the network SSID in the Gnome network settings dialog (even if I wait for quite a while). Doing so gets the internet working again for some time (under a minute to over an hour) until it eventually drops again. (Typically, a "?" wifi symbol will appear in the GNOME tray after it drops.) Unfortunately, this is a very frustrating workaround.

Here is an excerpt from from journalctl -u NetworkManager, where my connection was fine for quite some time (about 45 min) before dropping.

*** REMOVED: see more detailed logs under "Update 1" ***

Other potentially relevant info:

% ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:21:cc:c8:42:81 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 8c:70:5a:ca:d6:0c brd ff:ff:ff:ff:ff:ff
    inet 158.130.163.52/22 brd 158.130.163.255 scope global dynamic wlp3s0
       valid_lft 1018sec preferred_lft 1018sec
    inet6 2607:f470:6:4003:6e7c:eb14:cd4d:e9c0/64 scope global noprefixroute dynamic 
       valid_lft 2591999sec preferred_lft 604799sec
    inet6 fe80::fc0:92ab:8c65:d80c/64 scope link 
       valid_lft forever preferred_lft forever
% ip route
default via 158.130.160.1 dev wlp3s0 proto static metric 600 
158.130.160.0/22 dev wlp3s0 proto kernel scope link src 158.130.163.52 metric 600 
% lspci -v
...
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
	Subsystem: Intel Corporation Centrino Advanced-N 6205 (802.11a/b/g/n)
	Flags: bus master, fast devsel, latency 0, IRQ 30
	Memory at f2400000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
...
% iwconfig
lo        no wireless extensions.

enp0s25   no wireless extensions.

wlp3s0    IEEE 802.11  ESSID:"AirPennNet"  
          Mode:Managed  Frequency:5.805 GHz  Access Point: 04:BD:88:5B:9D:30   
          Bit Rate=162 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=46/70  Signal level=-64 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:25   Missed beacon:0

Please let me know if any more logs/output would help.

So far, I have tried (from the ArchWiki) adding the file

/etc/dhclient.conf

containing

interface "wlp3s0" {
  send dhcp-client-identifier 8c:70:5a:ca:d6:0c;
}

but this did not fix the problem. Perhaps a kind someone could help better direct my troubleshooting.


Update 1:

Below is the dmesg output, as requested. I have trimmed it to several minutes before and after my internet connectivity dropped, which occurred, in this case, at about 15:50 (plus/minus a couple minutes).

% dmesg -wH
[Sep14 15:40] wlp3s0: disconnect from AP 04:bd:88:5b:9d:30 for new auth to 04:bd:88:5b:9d:20
[  +0.064662] wlp3s0: authenticate with 04:bd:88:5b:9d:20
[  +0.003736] wlp3s0: send auth to 04:bd:88:5b:9d:20 (try 1/3)
[  +0.001922] wlp3s0: authenticated
[  +0.005274] wlp3s0: associate with 04:bd:88:5b:9d:20 (try 1/3)
[  +0.003475] wlp3s0: RX AssocResp from 04:bd:88:5b:9d:20 (capab=0x431 status=0 aid=2)
[  +0.019647] wlp3s0: associated
[Sep14 15:45] wlp3s0: deauthenticated from 04:bd:88:5b:9d:20 (Reason: 3=DEAUTH_LEAVING)
[  +0.629980] wlp3s0: authenticate with 04:bd:88:5b:9d:30
[  +0.003980] wlp3s0: send auth to 04:bd:88:5b:9d:30 (try 1/3)
[  +0.002338] wlp3s0: authenticated
[  +0.004472] wlp3s0: associate with 04:bd:88:5b:9d:30 (try 1/3)
[  +0.000934] wlp3s0: RX AssocResp from 04:bd:88:5b:9d:30 (capab=0x11 status=0 aid=18)
[  +0.018969] wlp3s0: associated
[  +0.072237] wlp3s0: Limiting TX power to 36 (36 - 0) dBm as advertised by 04:bd:88:5b:9d:30
[Sep14 15:47] wlp3s0: disconnect from AP 04:bd:88:5b:9d:30 for new auth to 04:bd:88:5b:9d:20
[  +0.041994] wlp3s0: authenticate with 04:bd:88:5b:9d:20
[  +0.003443] wlp3s0: send auth to 04:bd:88:5b:9d:20 (try 1/3)
[  +0.002821] wlp3s0: authenticated
[  +0.004599] wlp3s0: associate with 04:bd:88:5b:9d:20 (try 1/3)
[  +0.002532] wlp3s0: RX AssocResp from 04:bd:88:5b:9d:20 (capab=0x431 status=0 aid=2)
[  +0.019350] wlp3s0: associated
[ +26.786196] wlp3s0: deauthenticated from 04:bd:88:5b:9d:20 (Reason: 3=DEAUTH_LEAVING)
[  +0.551041] wlp3s0: authenticate with 04:bd:88:5b:9d:30
[  +0.002877] wlp3s0: send auth to 04:bd:88:5b:9d:30 (try 1/3)
[  +0.036565] wlp3s0: authenticated
[  +0.000974] wlp3s0: associate with 04:bd:88:5b:9d:30 (try 1/3)
[  +0.000983] wlp3s0: RX AssocResp from 04:bd:88:5b:9d:30 (capab=0x11 status=0 aid=21)
[  +0.019248] wlp3s0: associated
[  +0.077326] wlp3s0: Limiting TX power to 36 (36 - 0) dBm as advertised by 04:bd:88:5b:9d:30
[Sep14 15:48] wlp3s0: disconnect from AP 04:bd:88:5b:9d:30 for new auth to 04:bd:88:5b:9d:20
[  +0.049490] wlp3s0: authenticate with 04:bd:88:5b:9d:20
[  +0.002736] wlp3s0: send auth to 04:bd:88:5b:9d:20 (try 1/3)
[  +0.001921] wlp3s0: authenticated
[  +0.019807] wlp3s0: associate with 04:bd:88:5b:9d:20 (try 1/3)
[  +0.006804] wlp3s0: RX AssocResp from 04:bd:88:5b:9d:20 (capab=0x431 status=0 aid=2)
[  +0.020319] wlp3s0: associated
[Sep14 15:52] wlp3s0: disconnect from AP 04:bd:88:5b:9d:20 for new auth to 04:bd:88:5b:9d:30
[  +0.046362] wlp3s0: authenticate with 04:bd:88:5b:9d:30
[  +0.002753] wlp3s0: send auth to 04:bd:88:5b:9d:30 (try 1/3)
[  +0.021155] wlp3s0: authenticated
[  +0.000221] wlp3s0: associate with 04:bd:88:5b:9d:30 (try 1/3)
[  +0.001135] wlp3s0: RX AssocResp from 04:bd:88:5b:9d:30 (capab=0x11 status=0 aid=54)
[  +0.019173] wlp3s0: associated
[  +0.078608] wlp3s0: Limiting TX power to 36 (36 - 0) dBm as advertised by 04:bd:88:5b:9d:30

Here is a slightly more detailed log using journalctl -f. I have trimmed out some extraneous gnome-related warnings.

% journalctl -f
Sep 14 15:40:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: SME: Trying to authenticate with 04:bd:88:5b:9d:20 (SSID='AirPennNet' freq=2462 MHz)
Sep 14 15:40:55 CHE12-003 kernel: wlp3s0: disconnect from AP 04:bd:88:5b:9d:30 for new auth to 04:bd:88:5b:9d:20
Sep 14 15:40:55 CHE12-003 kernel: wlp3s0: authenticate with 04:bd:88:5b:9d:20
Sep 14 15:40:55 CHE12-003 kernel: wlp3s0: send auth to 04:bd:88:5b:9d:20 (try 1/3)
Sep 14 15:40:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: Trying to associate with 04:bd:88:5b:9d:20 (SSID='AirPennNet' freq=2462 MHz)
Sep 14 15:40:55 CHE12-003 kernel: wlp3s0: authenticated
Sep 14 15:40:55 CHE12-003 kernel: wlp3s0: associate with 04:bd:88:5b:9d:20 (try 1/3)
Sep 14 15:40:55 CHE12-003 kernel: wlp3s0: RX AssocResp from 04:bd:88:5b:9d:20 (capab=0x431 status=0 aid=2)
Sep 14 15:40:55 CHE12-003 NetworkManager[3067]: <info>  [1505418055.6794] device (wlp3s0): supplicant interface state: completed -> associating
Sep 14 15:40:55 CHE12-003 kernel: wlp3s0: associated
Sep 14 15:40:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: Associated with 04:bd:88:5b:9d:20
Sep 14 15:40:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 14 15:40:55 CHE12-003 NetworkManager[3067]: <info>  [1505418055.7389] device (wlp3s0): supplicant interface state: associating -> associated
Sep 14 15:40:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 14 15:40:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Sep 14 15:40:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: WPA: Key negotiation completed with 04:bd:88:5b:9d:20 [PTK=CCMP GTK=CCMP]
Sep 14 15:40:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 04:bd:88:5b:9d:20 completed [id=0 id_str=]
Sep 14 15:40:56 CHE12-003 NetworkManager[3067]: <info>  [1505418056.6633] device (wlp3s0): supplicant interface state: associated -> completed
Sep 14 15:40:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise=9999 txrate=5500
Sep 14 15:43:09 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 15:43:09 CHE12-003 dhclient[3101]: DHCPACK from 128.91.2.136
Sep 14 15:43:09 CHE12-003 NetworkManager[3067]: <info>  [1505418189.4356] dhcp4 (wlp3s0):   address 158.130.164.33
Sep 14 15:43:09 CHE12-003 dbus[613]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Sep 14 15:43:09 CHE12-003 NetworkManager[3067]: <info>  [1505418189.4356] dhcp4 (wlp3s0):   plen 22 (255.255.252.0)
Sep 14 15:43:09 CHE12-003 dbus[613]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 14 15:43:09 CHE12-003 NetworkManager[3067]: <info>  [1505418189.4356] dhcp4 (wlp3s0):   gateway 158.130.164.1
Sep 14 15:43:09 CHE12-003 nm-dispatcher[5664]: req:1 'dhcp4-change' [wlp3s0]: new request (0 scripts)
Sep 14 15:43:09 CHE12-003 NetworkManager[3067]: <info>  [1505418189.4356] dhcp4 (wlp3s0):   lease time 1200
Sep 14 15:43:09 CHE12-003 nm-dispatcher[5664]: req:1 'dhcp4-change' [wlp3s0]: completed: no scripts
Sep 14 15:43:09 CHE12-003 NetworkManager[3067]: <info>  [1505418189.4356] dhcp4 (wlp3s0):   nameserver '128.91.18.2'
Sep 14 15:43:09 CHE12-003 dhclient[3101]: bound to 158.130.164.33 -- renewal in 570 seconds.
Sep 14 15:43:09 CHE12-003 NetworkManager[3067]: <info>  [1505418189.4356] dhcp4 (wlp3s0):   nameserver '128.91.49.2'
Sep 14 15:43:09 CHE12-003 NetworkManager[3067]: <info>  [1505418189.4356] dhcp4 (wlp3s0): state changed bound -> bound
Sep 14 15:43:09 CHE12-003 systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 14 15:43:09 CHE12-003 systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 14 15:45:19 CHE12-003 kernel: wlp3s0: deauthenticated from 04:bd:88:5b:9d:20 (Reason: 3=DEAUTH_LEAVING)
Sep 14 15:45:19 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=04:bd:88:5b:9d:20 reason=3
Sep 14 15:45:19 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 14 15:45:19 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Sep 14 15:45:19 CHE12-003 NetworkManager[3067]: <warn>  [1505418319.4728] sup-iface[0x560b95dd9000,wlp3s0]: connection disconnected (reason 3)
Sep 14 15:45:19 CHE12-003 NetworkManager[3067]: <info>  [1505418319.4944] device (wlp3s0): supplicant interface state: completed -> disconnected
Sep 14 15:45:19 CHE12-003 NetworkManager[3067]: <info>  [1505418319.5775] device (wlp3s0): supplicant interface state: disconnected -> scanning
Sep 14 15:45:19 CHE12-003 wpa_supplicant[1253]: wlp3s0: SME: Trying to authenticate with 04:bd:88:5b:9d:30 (SSID='AirPennNet' freq=5805 MHz)
Sep 14 15:45:19 CHE12-003 kernel: wlp3s0: authenticate with 04:bd:88:5b:9d:30
Sep 14 15:45:19 CHE12-003 kernel: wlp3s0: send auth to 04:bd:88:5b:9d:30 (try 1/3)
Sep 14 15:45:19 CHE12-003 kernel: wlp3s0: authenticated
Sep 14 15:45:19 CHE12-003 wpa_supplicant[1253]: wlp3s0: Trying to associate with 04:bd:88:5b:9d:30 (SSID='AirPennNet' freq=5805 MHz)
Sep 14 15:45:20 CHE12-003 kernel: wlp3s0: associate with 04:bd:88:5b:9d:30 (try 1/3)
Sep 14 15:45:20 CHE12-003 kernel: wlp3s0: RX AssocResp from 04:bd:88:5b:9d:30 (capab=0x11 status=0 aid=18)
Sep 14 15:45:20 CHE12-003 NetworkManager[3067]: <info>  [1505418320.0204] device (wlp3s0): supplicant interface state: scanning -> authenticating
Sep 14 15:45:20 CHE12-003 wpa_supplicant[1253]: wlp3s0: Associated with 04:bd:88:5b:9d:30
Sep 14 15:45:20 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 14 15:45:20 CHE12-003 NetworkManager[3067]: <info>  [1505418320.0226] device (wlp3s0): supplicant interface state: authenticating -> associating
Sep 14 15:45:20 CHE12-003 kernel: wlp3s0: associated
Sep 14 15:45:20 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Sep 14 15:45:20 CHE12-003 NetworkManager[3067]: <info>  [1505418320.0283] device (wlp3s0): supplicant interface state: associating -> associated
Sep 14 15:45:20 CHE12-003 kernel: wlp3s0: Limiting TX power to 36 (36 - 0) dBm as advertised by 04:bd:88:5b:9d:30
Sep 14 15:45:20 CHE12-003 wpa_supplicant[1253]: wlp3s0: WPA: Key negotiation completed with 04:bd:88:5b:9d:30 [PTK=CCMP GTK=CCMP]
Sep 14 15:45:20 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 04:bd:88:5b:9d:30 completed [id=0 id_str=]
Sep 14 15:45:20 CHE12-003 NetworkManager[3067]: <info>  [1505418320.9289] device (wlp3s0): supplicant interface state: associated -> completed
Sep 14 15:45:21 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-66 noise=9999 txrate=6000
Sep 14 15:45:23 CHE12-003 avahi-daemon[612]: Registering new address record for 2607:f470:6:4007:e0b:1335:58f3:f3eb on wlp3s0.*.
Sep 14 15:47:31 CHE12-003 wpa_supplicant[1253]: wlp3s0: SME: Trying to authenticate with 04:bd:88:5b:9d:20 (SSID='AirPennNet' freq=2462 MHz)
Sep 14 15:47:31 CHE12-003 kernel: wlp3s0: disconnect from AP 04:bd:88:5b:9d:30 for new auth to 04:bd:88:5b:9d:20
Sep 14 15:47:31 CHE12-003 kernel: wlp3s0: authenticate with 04:bd:88:5b:9d:20
Sep 14 15:47:31 CHE12-003 kernel: wlp3s0: send auth to 04:bd:88:5b:9d:20 (try 1/3)
Sep 14 15:47:31 CHE12-003 kernel: wlp3s0: authenticated
Sep 14 15:47:31 CHE12-003 kernel: wlp3s0: associate with 04:bd:88:5b:9d:20 (try 1/3)
Sep 14 15:47:31 CHE12-003 kernel: wlp3s0: RX AssocResp from 04:bd:88:5b:9d:20 (capab=0x431 status=0 aid=2)
Sep 14 15:47:31 CHE12-003 wpa_supplicant[1253]: wlp3s0: Trying to associate with 04:bd:88:5b:9d:20 (SSID='AirPennNet' freq=2462 MHz)
Sep 14 15:47:31 CHE12-003 NetworkManager[3067]: <info>  [1505418451.3101] device (wlp3s0): supplicant interface state: completed -> authenticating
Sep 14 15:47:31 CHE12-003 wpa_supplicant[1253]: wlp3s0: Associated with 04:bd:88:5b:9d:20
Sep 14 15:47:31 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 14 15:47:31 CHE12-003 kernel: wlp3s0: associated
Sep 14 15:47:31 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 14 15:47:31 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Sep 14 15:47:31 CHE12-003 NetworkManager[3067]: <info>  [1505418451.4057] device (wlp3s0): supplicant interface state: authenticating -> associating
Sep 14 15:47:31 CHE12-003 NetworkManager[3067]: <info>  [1505418451.4428] device (wlp3s0): supplicant interface state: associating -> associated
Sep 14 15:47:32 CHE12-003 NetworkManager[3067]: <info>  [1505418452.2866] device (wlp3s0): supplicant interface state: associated -> 4-way handshake
Sep 14 15:47:32 CHE12-003 NetworkManager[3067]: <info>  [1505418452.2957] device (wlp3s0): supplicant interface state: 4-way handshake -> completed
Sep 14 15:47:32 CHE12-003 wpa_supplicant[1253]: wlp3s0: WPA: Key negotiation completed with 04:bd:88:5b:9d:20 [PTK=CCMP GTK=CCMP]
Sep 14 15:47:32 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 04:bd:88:5b:9d:20 completed [id=0 id_str=]
Sep 14 15:47:32 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=5500
Sep 14 15:47:34 CHE12-003 avahi-daemon[612]: Registering new address record for 2607:f470:6:4001:4c9b:697b:f397:47ff on wlp3s0.*.
Sep 14 15:47:58 CHE12-003 kernel: wlp3s0: deauthenticated from 04:bd:88:5b:9d:20 (Reason: 3=DEAUTH_LEAVING)
Sep 14 15:47:58 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=04:bd:88:5b:9d:20 reason=3
Sep 14 15:47:58 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 14 15:47:58 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Sep 14 15:47:58 CHE12-003 NetworkManager[3067]: <warn>  [1505418478.2251] sup-iface[0x560b95dd9000,wlp3s0]: connection disconnected (reason 3)
Sep 14 15:47:58 CHE12-003 NetworkManager[3067]: <info>  [1505418478.2532] device (wlp3s0): supplicant interface state: completed -> disconnected
Sep 14 15:47:58 CHE12-003 NetworkManager[3067]: <info>  [1505418478.3304] device (wlp3s0): supplicant interface state: disconnected -> scanning
Sep 14 15:47:58 CHE12-003 kernel: wlp3s0: authenticate with 04:bd:88:5b:9d:30
Sep 14 15:47:58 CHE12-003 wpa_supplicant[1253]: wlp3s0: SME: Trying to authenticate with 04:bd:88:5b:9d:30 (SSID='AirPennNet' freq=5805 MHz)
Sep 14 15:47:58 CHE12-003 kernel: wlp3s0: send auth to 04:bd:88:5b:9d:30 (try 1/3)
Sep 14 15:47:58 CHE12-003 wpa_supplicant[1253]: wlp3s0: Trying to associate with 04:bd:88:5b:9d:30 (SSID='AirPennNet' freq=5805 MHz)
Sep 14 15:47:58 CHE12-003 kernel: wlp3s0: authenticated
Sep 14 15:47:58 CHE12-003 kernel: wlp3s0: associate with 04:bd:88:5b:9d:30 (try 1/3)
Sep 14 15:47:58 CHE12-003 kernel: wlp3s0: RX AssocResp from 04:bd:88:5b:9d:30 (capab=0x11 status=0 aid=21)
Sep 14 15:47:58 CHE12-003 NetworkManager[3067]: <info>  [1505418478.7234] device (wlp3s0): supplicant interface state: scanning -> authenticating
Sep 14 15:47:58 CHE12-003 kernel: wlp3s0: associated
Sep 14 15:47:58 CHE12-003 wpa_supplicant[1253]: wlp3s0: Associated with 04:bd:88:5b:9d:30
Sep 14 15:47:58 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 14 15:47:58 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Sep 14 15:47:58 CHE12-003 NetworkManager[3067]: <info>  [1505418478.7456] device (wlp3s0): supplicant interface state: authenticating -> associating
Sep 14 15:47:58 CHE12-003 NetworkManager[3067]: <info>  [1505418478.7610] device (wlp3s0): supplicant interface state: associating -> associated
Sep 14 15:47:58 CHE12-003 kernel: wlp3s0: Limiting TX power to 36 (36 - 0) dBm as advertised by 04:bd:88:5b:9d:30
Sep 14 15:47:59 CHE12-003 wpa_supplicant[1253]: wlp3s0: WPA: Key negotiation completed with 04:bd:88:5b:9d:30 [PTK=CCMP GTK=CCMP]
Sep 14 15:47:59 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 04:bd:88:5b:9d:30 completed [id=0 id_str=]
Sep 14 15:47:59 CHE12-003 NetworkManager[3067]: <info>  [1505418479.7039] device (wlp3s0): supplicant interface state: associated -> completed
Sep 14 15:48:00 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise=9999 txrate=40500
Sep 14 15:48:01 CHE12-003 avahi-daemon[612]: Registering new address record for 2607:f470:6:4002:bdb0:e69:2309:f148 on wlp3s0.*.
Sep 14 15:48:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: SME: Trying to authenticate with 04:bd:88:5b:9d:20 (SSID='AirPennNet' freq=2462 MHz)
Sep 14 15:48:55 CHE12-003 kernel: wlp3s0: disconnect from AP 04:bd:88:5b:9d:30 for new auth to 04:bd:88:5b:9d:20
Sep 14 15:48:55 CHE12-003 kernel: wlp3s0: authenticate with 04:bd:88:5b:9d:20
Sep 14 15:48:55 CHE12-003 kernel: wlp3s0: send auth to 04:bd:88:5b:9d:20 (try 1/3)
Sep 14 15:48:55 CHE12-003 kernel: wlp3s0: authenticated
Sep 14 15:48:55 CHE12-003 NetworkManager[3067]: <info>  [1505418535.8033] device (wlp3s0): supplicant interface state: completed -> authenticating
Sep 14 15:48:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: Trying to associate with 04:bd:88:5b:9d:20 (SSID='AirPennNet' freq=2462 MHz)
Sep 14 15:48:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 14 15:48:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Sep 14 15:48:55 CHE12-003 kernel: wlp3s0: associate with 04:bd:88:5b:9d:20 (try 1/3)
Sep 14 15:48:55 CHE12-003 kernel: wlp3s0: RX AssocResp from 04:bd:88:5b:9d:20 (capab=0x431 status=0 aid=2)
Sep 14 15:48:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: Associated with 04:bd:88:5b:9d:20
Sep 14 15:48:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 14 15:48:55 CHE12-003 kernel: wlp3s0: associated
Sep 14 15:48:55 CHE12-003 NetworkManager[3067]: <info>  [1505418535.8722] device (wlp3s0): supplicant interface state: authenticating -> associating
Sep 14 15:48:55 CHE12-003 NetworkManager[3067]: <info>  [1505418535.9096] device (wlp3s0): supplicant interface state: associating -> associated
Sep 14 15:48:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: WPA: Key negotiation completed with 04:bd:88:5b:9d:20 [PTK=CCMP GTK=CCMP]
Sep 14 15:48:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 04:bd:88:5b:9d:20 completed [id=0 id_str=]
Sep 14 15:48:56 CHE12-003 NetworkManager[3067]: <info>  [1505418536.7727] device (wlp3s0): supplicant interface state: associated -> completed
Sep 14 15:48:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=5500
Sep 14 15:51:47 CHE12-003 dbus[613]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Sep 14 15:51:47 CHE12-003 systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 14 15:51:47 CHE12-003 dbus[613]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 14 15:51:47 CHE12-003 systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 14 15:51:47 CHE12-003 nm-dispatcher[5947]: req:1 'connectivity-change': new request (0 scripts)
Sep 14 15:51:47 CHE12-003 nm-dispatcher[5947]: req:1 'connectivity-change': completed: no scripts
Sep 14 15:52:39 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 15:52:45 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 15:52:51 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 15:52:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: SME: Trying to authenticate with 04:bd:88:5b:9d:30 (SSID='AirPennNet' freq=5805 MHz)
Sep 14 15:52:55 CHE12-003 kernel: wlp3s0: disconnect from AP 04:bd:88:5b:9d:20 for new auth to 04:bd:88:5b:9d:30
Sep 14 15:52:55 CHE12-003 kernel: wlp3s0: authenticate with 04:bd:88:5b:9d:30
Sep 14 15:52:55 CHE12-003 kernel: wlp3s0: send auth to 04:bd:88:5b:9d:30 (try 1/3)
Sep 14 15:52:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 14 15:52:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Sep 14 15:52:55 CHE12-003 NetworkManager[3067]: <info>  [1505418775.7680] device (wlp3s0): supplicant interface state: completed -> authenticating
Sep 14 15:52:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: Trying to associate with 04:bd:88:5b:9d:30 (SSID='AirPennNet' freq=5805 MHz)
Sep 14 15:52:55 CHE12-003 kernel: wlp3s0: authenticated
Sep 14 15:52:55 CHE12-003 kernel: wlp3s0: associate with 04:bd:88:5b:9d:30 (try 1/3)
Sep 14 15:52:55 CHE12-003 kernel: wlp3s0: RX AssocResp from 04:bd:88:5b:9d:30 (capab=0x11 status=0 aid=54)
Sep 14 15:52:55 CHE12-003 NetworkManager[3067]: <info>  [1505418775.7845] device (wlp3s0): supplicant interface state: authenticating -> associating
Sep 14 15:52:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: Associated with 04:bd:88:5b:9d:30
Sep 14 15:52:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 14 15:52:55 CHE12-003 kernel: wlp3s0: associated
Sep 14 15:52:55 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Sep 14 15:52:55 CHE12-003 NetworkManager[3067]: <info>  [1505418775.8392] device (wlp3s0): supplicant interface state: associating -> associated
Sep 14 15:52:55 CHE12-003 kernel: wlp3s0: Limiting TX power to 36 (36 - 0) dBm as advertised by 04:bd:88:5b:9d:30
Sep 14 15:52:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: WPA: Key negotiation completed with 04:bd:88:5b:9d:30 [PTK=CCMP GTK=CCMP]
Sep 14 15:52:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 04:bd:88:5b:9d:30 completed [id=0 id_str=]
Sep 14 15:52:56 CHE12-003 NetworkManager[3067]: <info>  [1505418776.7781] device (wlp3s0): supplicant interface state: associated -> completed
Sep 14 15:52:56 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-68 noise=9999 txrate=6000
Sep 14 15:53:01 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 15:53:01 CHE12-003 dhclient[3101]: DHCPACK from 128.91.2.136
Sep 14 15:53:01 CHE12-003 NetworkManager[3067]: <info>  [1505418781.8901] dhcp4 (wlp3s0):   address 158.130.164.33
Sep 14 15:53:01 CHE12-003 NetworkManager[3067]: <info>  [1505418781.8901] dhcp4 (wlp3s0):   plen 22 (255.255.252.0)
Sep 14 15:53:01 CHE12-003 NetworkManager[3067]: <info>  [1505418781.8901] dhcp4 (wlp3s0):   gateway 158.130.164.1
Sep 14 15:53:01 CHE12-003 NetworkManager[3067]: <info>  [1505418781.8902] dhcp4 (wlp3s0):   lease time 1200
Sep 14 15:53:01 CHE12-003 NetworkManager[3067]: <info>  [1505418781.8902] dhcp4 (wlp3s0):   nameserver '128.91.18.2'
Sep 14 15:53:01 CHE12-003 NetworkManager[3067]: <info>  [1505418781.8902] dhcp4 (wlp3s0):   nameserver '128.91.49.2'
Sep 14 15:53:01 CHE12-003 NetworkManager[3067]: <info>  [1505418781.8902] dhcp4 (wlp3s0): state changed bound -> bound
Sep 14 15:53:01 CHE12-003 dbus[613]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Sep 14 15:53:01 CHE12-003 systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 14 15:53:01 CHE12-003 dbus[613]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 14 15:53:01 CHE12-003 systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 14 15:53:01 CHE12-003 nm-dispatcher[5993]: req:1 'dhcp4-change' [wlp3s0]: new request (0 scripts)
Sep 14 15:53:01 CHE12-003 nm-dispatcher[5993]: req:1 'dhcp4-change' [wlp3s0]: completed: no scripts
Sep 14 15:53:01 CHE12-003 dhclient[3101]: bound to 158.130.164.33 -- renewal in 550 seconds.
Sep 14 15:57:06 CHE12-003 firefox.desktop[2350]: 1505419026841        Sync.ErrorHandler        ERROR        Sync encountered an error: [Exception... "NS_ERROR_UNKNOWN_HOST"  nsresult: "0x804b001e (NS_ERROR_UNKNOWN_HOST)"  location: "JS frame :: resource://services-sync/resource.js :: Channel_onStopRequest :: line 422"  data: no] Stack trace: Channel_onStopRequest()@resource://services-sync/resource.js:422 < waitForSyncCallback()@resource://services-common/async.js:98 < makeSpinningCallback/callback.wait()@resource://services-common/async.js:168 < promiseSpinningly()@resource://services-common/async.js:234 < _fetchInfo()@resource://services-sync/service.js:470 < sync()@resource://services-sync/stages/enginesync.js:79 < onNotify()@resource://services-sync/service.js:1081 < WrappedNotify()@resource://services-sync/util.js:160 < WrappedLock()@resource://services-sync/util.js:116 < _lockedSync()@resource://services-sync/service.js:1071 < sync/<()@resource://services-sync/service.js:1063 < WrappedCatch()@resource://services-sync/util.js:91 < sync()@resource://services-sync/service.js:1052
Sep 14 15:57:53 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-61 noise=9999 txrate=120000
Sep 14 15:58:25 CHE12-003 dbus[613]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Sep 14 15:58:25 CHE12-003 systemd[1]: Starting Hostname Service...
Sep 14 15:58:25 CHE12-003 dbus[613]: [system] Successfully activated service 'org.freedesktop.hostname1'
Sep 14 15:58:25 CHE12-003 systemd[1]: Started Hostname Service.
Sep 14 15:58:25 CHE12-003 gsd-power[1778]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
Sep 14 15:59:21 CHE12-003 wpa_supplicant[1253]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-68 noise=9999 txrate=162000
Sep 14 16:02:11 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:02:16 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:02:28 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:02:38 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:02:53 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:03:01 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:03:09 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:03:26 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:03:34 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:03:49 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:04:01 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:04:19 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:04:30 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:04:37 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:04:47 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:05:04 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:05:22 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:05:31 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:05:50 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:06:04 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:06:19 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:06:40 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:06:47 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:06:55 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:07:03 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:07:14 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:07:31 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:07:42 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:08:01 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:08:11 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:08:21 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:08:26 CHE12-003 firefox.desktop[2350]: 1505419706957        Sync.ErrorHandler        ERROR        Sync encountered an error: [Exception... "NS_ERROR_UNKNOWN_HOST"  nsresult: "0x804b001e (NS_ERROR_UNKNOWN_HOST)"  location: "JS frame :: resource://services-sync/resource.js :: Channel_onStopRequest :: line 422"  data: no] Stack trace: Channel_onStopRequest()@resource://services-sync/resource.js:422 < waitForSyncCallback()@resource://services-common/async.js:98 < makeSpinningCallback/callback.wait()@resource://services-common/async.js:168 < promiseSpinningly()@resource://services-common/async.js:234 < _fetchInfo()@resource://services-sync/service.js:470 < sync()@resource://services-sync/stages/enginesync.js:79 < onNotify()@resource://services-sync/service.js:1081 < WrappedNotify()@resource://services-sync/util.js:160 < WrappedLock()@resource://services-sync/util.js:116 < _lockedSync()@resource://services-sync/service.js:1071 < sync/<()@resource://services-sync/service.js:1063 < WrappedCatch()@resource://services-sync/util.js:91 < sync()@resource://services-sync/service.js:1052
Sep 14 16:08:35 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:08:56 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:09:13 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:09:18 CHE12-003 systemd-timesyncd[605]: Timed out waiting for reply from 208.75.88.4:123 (2.arch.pool.ntp.org).
Sep 14 16:09:26 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:09:29 CHE12-003 systemd-timesyncd[605]: Timed out waiting for reply from 108.61.73.243:123 (2.arch.pool.ntp.org).
Sep 14 16:09:39 CHE12-003 systemd-timesyncd[605]: Timed out waiting for reply from 204.17.205.24:123 (2.arch.pool.ntp.org).
Sep 14 16:09:41 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:09:49 CHE12-003 systemd-timesyncd[605]: Timed out waiting for reply from 216.93.242.12:123 (2.arch.pool.ntp.org).
Sep 14 16:09:59 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:10:11 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:10:25 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 128.91.2.136 port 67
Sep 14 16:10:36 CHE12-003 dhclient[3101]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67
Sep 14 16:10:36 CHE12-003 dhclient[3101]: DHCPNAK from 128.91.164.1
Sep 14 16:10:36 CHE12-003 NetworkManager[3067]: <info>  [1505419836.8855] dhcp4 (wlp3s0): state changed bound -> expire
Sep 14 16:10:36 CHE12-003 NetworkManager[3067]: <info>  [1505419836.9544] dhcp4 (wlp3s0): canceled DHCP transaction, DHCP client pid 3101
Sep 14 16:10:36 CHE12-003 NetworkManager[3067]: <info>  [1505419836.9544] dhcp4 (wlp3s0): state changed expire -> done
Sep 14 16:10:36 CHE12-003 NetworkManager[3067]: <info>  [1505419836.9546] device (wlp3s0): scheduling DHCPv4 restart in 120 seconds, 3 tries left (reason: lease expired)
Sep 14 16:12:37 CHE12-003 NetworkManager[3067]: <info>  [1505419957.2162] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
Sep 14 16:12:37 CHE12-003 NetworkManager[3067]: <info>  [1505419957.2600] dhcp4 (wlp3s0): dhclient started with pid 6237
Sep 14 16:12:37 CHE12-003 dhclient[6237]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67
Sep 14 16:12:37 CHE12-003 dhclient[6237]: DHCPNAK from 128.91.164.1
Sep 14 16:12:37 CHE12-003 NetworkManager[3067]: <info>  [1505419957.3742] dhcp4 (wlp3s0): state changed unknown -> expire
Sep 14 16:12:37 CHE12-003 NetworkManager[3067]: <info>  [1505419957.4064] dhcp4 (wlp3s0): canceled DHCP transaction, DHCP client pid 6237
Sep 14 16:12:37 CHE12-003 NetworkManager[3067]: <info>  [1505419957.4064] dhcp4 (wlp3s0): state changed expire -> done
Sep 14 16:12:37 CHE12-003 NetworkManager[3067]: <info>  [1505419957.4068] device (wlp3s0): scheduling DHCPv4 restart in 120 seconds, 2 tries left (reason: lease expired)
Sep 14 16:13:02 CHE12-003 avahi-daemon[612]: Withdrawing address record for 158.130.164.33 on wlp3s0.
Sep 14 16:13:02 CHE12-003 avahi-daemon[612]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 158.130.164.33.
Sep 14 16:13:02 CHE12-003 avahi-daemon[612]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.1931] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.1985] dhcp4 (wlp3s0): dhclient started with pid 6306
Sep 14 16:14:37 CHE12-003 dhclient[6306]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 4
Sep 14 16:14:37 CHE12-003 dhclient[6306]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67
Sep 14 16:14:37 CHE12-003 dhclient[6306]: DHCPOFFER from 128.91.164.1
Sep 14 16:14:37 CHE12-003 dhclient[6306]: DHCPACK from 128.91.164.1
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.2945] dhcp4 (wlp3s0):   address 128.91.166.99
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.2946] dhcp4 (wlp3s0):   plen 22 (255.255.252.0)
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.2946] dhcp4 (wlp3s0):   gateway 128.91.164.1
Sep 14 16:14:37 CHE12-003 avahi-daemon[612]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 128.91.166.99.
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.2947] dhcp4 (wlp3s0):   lease time 1200
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.2947] dhcp4 (wlp3s0):   nameserver '128.91.18.2'
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.2947] dhcp4 (wlp3s0):   nameserver '128.91.49.2'
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.2948] dhcp4 (wlp3s0): state changed unknown -> bound
Sep 14 16:14:37 CHE12-003 avahi-daemon[612]: New relevant interface wlp3s0.IPv4 for mDNS.
Sep 14 16:14:37 CHE12-003 avahi-daemon[612]: Registering new address record for 128.91.166.99 on wlp3s0.IPv4.
Sep 14 16:14:37 CHE12-003 NetworkManager[3067]: <info>  [1505420077.2996] policy: set 'AirPennNet' (wlp3s0) as default for IPv4 routing and DNS
Sep 14 16:14:37 CHE12-003 dbus[613]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Sep 14 16:14:37 CHE12-003 systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 14 16:14:37 CHE12-003 dbus[613]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 14 16:14:37 CHE12-003 systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 14 16:14:37 CHE12-003 nm-dispatcher[6316]: req:1 'dhcp4-change' [wlp3s0]: new request (0 scripts)
Sep 14 16:14:37 CHE12-003 nm-dispatcher[6316]: req:1 'dhcp4-change' [wlp3s0]: completed: no scripts
Sep 14 16:14:37 CHE12-003 dhclient[6306]: bound to 128.91.166.99 -- renewal in 515 seconds.
Sep 14 16:16:21 CHE12-003 dbus[613]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Sep 14 16:16:21 CHE12-003 systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 14 16:16:21 CHE12-003 dbus[613]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 14 16:16:21 CHE12-003 systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 14 16:16:21 CHE12-003 nm-dispatcher[6355]: req:1 'connectivity-change': new request (0 scripts)
Sep 14 16:16:21 CHE12-003 nm-dispatcher[6355]: req:1 'connectivity-change': completed: no scripts

I have gone through https://wiki.archlinux.org/index.php/Wi … onnections, and I do not see an obvious match with my particular issue. I will try disabling PCI Express power management in the BIOS of my Thinkpad T420 tomorrow to see if that helps. From the output of iwconfig though, it appears that power management on my wireless card is off. I am not sure if there is an incompatibility with the way the university has their wireless routers set up, in which case I'd have little power to make changes.

Last edited by nchishol (2017-09-14 22:43:16)

Offline

#2 2017-09-13 21:48:01

adesh
Member
Registered: 2016-10-05
Posts: 167

Re: Wireless network connectivity sporadically drops

Please check your dmesg output, or post here for someone to analyze.
Wiki also has troubleshooting steps for random wireless disconnections; try them if not already done.

Offline

#3 2017-09-14 22:45:58

nchishol
Member
Registered: 2016-06-13
Posts: 6

Re: Wireless network connectivity sporadically drops

Thanks for pointing me to that wiki page, adesh. I have provided the output you requested in an update to my original post. Unfortunately, the problem still has not become apparent to me.

Offline

#4 2017-09-15 07:19:56

seth
Member
Registered: 2012-09-03
Posts: 49,601

Re: Wireless network connectivity sporadically drops

Output of

systemctl list-units | grep -iE '(net|wicd|dhcp|conn)'

?

Offline

#5 2017-09-15 07:57:36

adesh
Member
Registered: 2016-10-05
Posts: 167

Re: Wireless network connectivity sporadically drops

@OP: Did you try the solutions provided in the wiki? I think your problem is listed in Cause #1.
Your dmesg says:

[ +26.786196] wlp3s0: deauthenticated from 04:bd:88:5b:9d:20 (Reason: 3=DEAUTH_LEAVING)

and

[  +0.077326] wlp3s0: Limiting TX power to 36 (36 - 0) dBm as advertised by 04:bd:88:5b:9d:30
[Sep14 15:48] wlp3s0: disconnect from AP 04:bd:88:5b:9d:30 for new auth to 04:bd:88:5b:9d:20

That simply means that when kernel tries to reduce wireless adapter power, disconnection happens.

Try disabling power saving features of your wireless card, as per solution in the wiki.

Offline

#6 2017-09-15 17:29:26

nchishol
Member
Registered: 2016-06-13
Posts: 6

Re: Wireless network connectivity sporadically drops

@seth

% systemctl list-units | grep -iE '(net|wicd|dhcp|conn)'
sys-devices-pci0000:00-0000:00:19.0-net-enp0s25.device               loaded active plugged   82579LM Gigabit Network Connection (Lewisville) (ThinkPad T520)                  
sys-devices-pci0000:00-0000:00:1c.1-0000:03:00.0-net-wlp3s0.device   loaded active plugged   Centrino Advanced-N 6205 [Taylor Peak] (Centrino Advanced-N 6205 (802.11a/b/g/n))
sys-subsystem-net-devices-enp0s25.device                             loaded active plugged   82579LM Gigabit Network Connection (Lewisville) (ThinkPad T520)                  
sys-subsystem-net-devices-wlp3s0.device                              loaded active plugged   Centrino Advanced-N 6205 [Taylor Peak] (Centrino Advanced-N 6205 (802.11a/b/g/n))
sys-fs-fuse-connections.mount                                        loaded active mounted   FUSE Control File System                                                         
NetworkManager.service                                               loaded active running   Network Manager                                                                  
systemd-timesyncd.service                                            loaded active running   Network Time Synchronization                                                     
network.target                                                       loaded active active    Network                                                                          

@adesh

I can confirm that power management is off.

% iwconfig wlp3s0
wlp3s0    IEEE 802.11  ESSID:"AirPennNet"  
          Mode:Managed  Frequency:5.805 GHz  Access Point: 04:BD:88:5B:9D:30   
          Bit Rate=81 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=39/70  Signal level=-71 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:54   Missed beacon:0

Could my problems be due to a bad signal level? I remember reading somewhere that less than -70dBm is not good, but I can't remember where.

Note that my regdomain was set to 00 (world). I changed it to US, and the disconnections seem to have become less frequent.

% iw reg get
global
country US: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
	(57240 - 63720 @ 2160), (N/A, 40), (N/A)

I am the only one working in my office today, and I have not had any disconnects so far. I am now wondering if it is possible that other nearby laptops could be causing interference and more frequent disconnects for me (our three desks are clustered closely together). If I can prove signal strength is indeed the culprit, I may be able to get IT to fix it. Secondly, I have noticed that iwconfig lists the Tx-power as 15 dBm, with the max allowed being 23–30 dBm depending on the frequency, if I am correctly interpreting the regdomain info. I am not sure if it is possible or useful to bump up the Tx-power.

Last edited by nchishol (2017-09-15 17:39:24)

Offline

#7 2017-09-15 20:35:11

seth
Member
Registered: 2012-09-03
Posts: 49,601

Re: Wireless network connectivity sporadically drops

Your network jumps between two accespoints. I first thought this was triggered by concurrent services, but it seems to be a networkmanager feature. It can probably be disabled an might be configured to be "smarter" (bigger overlap on failing and raising signal strength)

Offline

Board footer

Powered by FluxBB