No output means no mention of tlp in the system logfile. I will do some searching to see if there is a tlp logfileFelony wrote:Forgive my ignorance, but what am I looking for when I use:
dmesg | grep -i tlp
All I get is a return to a prompt. I see no output.
Mint 17 wifi issues vs 16
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Re: Re: Mint 17 wifi issues vs 16
Re: Re: Mint 17 wifi issues vs 16
Sound good. TLP is supposed to be a good program for laptops and it would be great to use it. I do have a couple of other brainstorming ideas that may or may not apply.JeremyB wrote:No output means no mention of tlp in the system logfile. I will do some searching to see if there is a tlp logfileFelony wrote:Forgive my ignorance, but what am I looking for when I use:
dmesg | grep -i tlp
All I get is a return to a prompt. I see no output.
A lot of disconnects happen when downloading big files, like @ 9-36gb files, especially torrents
The frequency of the disconnects has gotten less frequent with the things we are doing, which is a big improvement.
Here are two things that may or may not be relevant:
1. Could Verizon FIOS be doing anything to cut off the downloads?
2. Could Transmission settings or the program itself have anything to do with it?
The disconnects while browsing have gotten better, but not fixed and trying one thing at a time we are doing is better than doing tons of things at once, not knowing what the issue actually is, especially since it seems to be affecting others rather than just me.
Thanks again for your hard work!
Re: Re: Re: Mint 17 wifi issues vs 16
Not sure about Verizon FIOS, I don't have access to the fancy stuff but I use a US Cellular mobile hotspot. Is there a router log of any kind to compare to dmesg. Most of the info I find on deauthenticated by local choice- reason 3 is older, prior to LM 17/Ubuntu 14.04 some problems were solved by stopping wpa-supplicant and one was fixed by using manual wifi settings instead of DHCPFelony wrote:Sound good. TLP is supposed to be a good program for laptops and it would be great to use it. I do have a couple of other brainstorming ideas that may or may not apply.JeremyB wrote:No output means no mention of tlp in the system logfile. I will do some searching to see if there is a tlp logfileFelony wrote:Forgive my ignorance, but what am I looking for when I use:
dmesg | grep -i tlp
All I get is a return to a prompt. I see no output.
A lot of disconnects happen when downloading big files, like @ 9-36gb files, especially torrents
The frequency of the disconnects has gotten less frequent with the things we are doing, which is a big improvement.
Here are two things that may or may not be relevant:
1. Could Verizon FIOS be doing anything to cut off the downloads?
2. Could Transmission settings or the program itself have anything to do with it?
The disconnects while browsing have gotten better, but not fixed and trying one thing at a time we are doing is better than doing tons of things at once, not knowing what the issue actually is, especially since it seems to be affecting others rather than just me.
Thanks again for your hard work!
Re: Mint 17 wifi issues vs 16
I will look at the router and see if I can find anything while you are looking at the dmesg.Not sure about Verizon FIOS, I don't have access to the fancy stuff but I use a US Cellular mobile hotspot. Is there a router log of any kind to compare to dmesg. Most of the info I find on deauthenticated by local choice- reason 3 is older, prior to LM 17/Ubuntu 14.04 some problems were solved by stopping wpa-supplicant and one was fixed by using manual wifi settings instead of DHCP
I'm positive that Verizon won't give me a static IP(s), so unless you mean something like trying to establish a static IP(s) from behind my router's NAT routing for devices in my household, I'd have to figure out how to do that.
Re: Re: Mint 17 wifi issues vs 16
You might be able to do it at the pc without changing router settings, I had to do some weird things to get wireless going when I was using Hughes satellite internetFelony wrote:I will look at the router and see if I can find anything while you are looking at the dmesg.Not sure about Verizon FIOS, I don't have access to the fancy stuff but I use a US Cellular mobile hotspot. Is there a router log of any kind to compare to dmesg. Most of the info I find on deauthenticated by local choice- reason 3 is older, prior to LM 17/Ubuntu 14.04 some problems were solved by stopping wpa-supplicant and one was fixed by using manual wifi settings instead of DHCP
I'm positive that Verizon won't give me a static IP(s), so unless you mean something like trying to establish a static IP(s) from behind my router's NAT routing for devices in my household, I'd have to figure out how to do that.
Re: Mint 17 wifi issues vs 16
The good news is, is that the laptop has been running since 1pm with no disconnects!
Now I'm about to stress test it and let's see what happens.
Did you find anything in the dmesg?
Now I'm about to stress test it and let's see what happens.
Did you find anything in the dmesg?
Re: Mint 17 wifi issues vs 16
Very interesting. As soon as I started the stress testing via torrents, no more than 5mins I was disconnected.Felony wrote:The good news is, is that the laptop has been running since 1pm with no disconnects!
Now I'm about to stress test it and let's see what happens.
Did you find anything in the dmesg?
Re: Mint 17 wifi issues vs 16
Should search syslog for info.Felony wrote:Very interesting. As soon as I started the stress testing via torrents, no more than 5mins I was disconnected.Felony wrote:The good news is, is that the laptop has been running since 1pm with no disconnects!
Now I'm about to stress test it and let's see what happens.
Did you find anything in the dmesg?
Code: Select all
cat /var/log/syslog | grep wlan0
I did a google search for verizon fios disconnect- this might be a two headed monster
Re: Mint 17 wifi issues vs 16
*Whew*
Here is the out output:
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): deactivating device (reason 'none') [0]
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): taking down device.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Interface wlan0.IPv6 no longer relevant for mDNS.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::4eeb:42ff:fe29:bdfa.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Withdrawing address record for fe80::4eeb:42ff:fe29:bdfa on wlan0.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): bringing up device.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): bringing up device.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.051875] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0) supports 5 scan SSIDs
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: starting -> ready
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: ready -> disconnected
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0) supports 5 scan SSIDs
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Reject scan trigger since one is already pending
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) starting connection 'Manchester'
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: disconnected -> inactive
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0/wireless): access point 'Manchester' has security, but secrets are required.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0/wireless): connection 'Manchester' has security, and secrets exist. No new secrets needed.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: SME: Trying to authenticate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.522609] wlan0: authenticate with f8:e4:fb:84:34:35
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.532790] wlan0: send auth to f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: inactive -> authenticating
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Trying to associate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.637206] wlan0: send auth to f8:e4:fb:84:34:35 (try 2/3)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.638959] wlan0: authenticated
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.641211] wlan0: associate with f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.644461] wlan0: RX AssocResp from f8:e4:fb:84:34:35 (capab=0x431 status=0 aid=5)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Associated with f8:e4:fb:84:34:35
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.650135] wlan0: associated
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.650165] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associating -> associated
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: WPA: Key negotiation completed with f8:e4:fb:84:34:35 [PTK=CCMP GTK=CCMP]
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:e4:fb:84:34:35 completed [id=0 id_str=]
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associated -> completed
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Manchester'.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Beginning IP6 addrconf.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC dhclient: Listening on LPF/wlan0/4c:eb:42:29:bd:fa
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC dhclient: Sending on LPF/wlan0/4c:eb:42:29:bd:fa
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC dhclient: DHCPREQUEST of 192.168.1.3 on wlan0 to 255.255.255.255 port 67 (xid=0x5880bd54)
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.3.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: New relevant interface wlan0.IPv4 for mDNS.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Registering new address record for 192.168.1.3 on wlan0.IPv4.
Jul 3 10:28:26 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Jul 3 10:28:26 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Jul 3 10:28:26 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Jul 3 10:28:26 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Policy set 'Manchester' (wlan0) as default for IPv4 routing and DNS.
Jul 3 10:28:27 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) successful, device activated.
Jul 3 10:28:27 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::4eeb:42ff:fe29:bdfa.
Jul 3 10:28:27 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: New relevant interface wlan0.IPv6 for mDNS.
Jul 3 10:28:27 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Registering new address record for fe80::4eeb:42ff:fe29:bdfa on wlan0.*.
Jul 3 10:28:44 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): IP6 addrconf timed out or failed.
Jul 3 10:28:44 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jul 3 10:28:44 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jul 3 10:28:44 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 3 10:28:45 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:29:28 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.675068] wlan0: deauthenticated from f8:e4:fb:84:34:35 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Jul 3 10:30:31 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:e4:fb:84:34:35 reason=6
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: SME: Trying to authenticate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.708513] wlan0: authenticate with f8:e4:fb:84:34:35
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: completed -> authenticating
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.731300] wlan0: send auth to f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Trying to associate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.735163] wlan0: authenticated
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.736121] wlan0: associate with f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jul 3 10:30:49 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.752522] wlan0: RX AssocResp from f8:e4:fb:84:34:35 (capab=0x431 status=0 aid=5)
Jul 3 10:30:49 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Associated with f8:e4:fb:84:34:35
Jul 3 10:30:49 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.758356] wlan0: associated
Jul 3 10:30:49 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associating -> associated
Jul 3 10:30:50 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: WPA: Key negotiation completed with f8:e4:fb:84:34:35 [PTK=CCMP GTK=CCMP]
Jul 3 10:30:50 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:e4:fb:84:34:35 completed [id=0 id_str=]
Jul 3 10:30:50 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associated -> completed
Jul 3 10:31:54 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.859561] wlan0: deauthenticated from f8:e4:fb:84:34:35 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:e4:fb:84:34:35 reason=6
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: SME: Trying to authenticate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.882481] wlan0: authenticate with f8:e4:fb:84:34:35
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: completed -> authenticating
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.895461] wlan0: send auth to f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Trying to associate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.909928] wlan0: authenticated
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.913998] wlan0: associate with f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.917490] wlan0: RX AssocResp from f8:e4:fb:84:34:35 (capab=0x431 status=0 aid=5)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Associated with f8:e4:fb:84:34:35
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.924535] wlan0: associated
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: WPA: Key negotiation completed with f8:e4:fb:84:34:35 [PTK=CCMP GTK=CCMP]
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:e4:fb:84:34:35 completed [id=0 id_str=]
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Jul 3 10:33:37 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:43:37 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: message repeated 5 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Jul 3 10:45:37 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Here is the out output:
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): deactivating device (reason 'none') [0]
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): taking down device.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Interface wlan0.IPv6 no longer relevant for mDNS.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::4eeb:42ff:fe29:bdfa.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Withdrawing address record for fe80::4eeb:42ff:fe29:bdfa on wlan0.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): bringing up device.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): bringing up device.
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.051875] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0) supports 5 scan SSIDs
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: starting -> ready
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: ready -> disconnected
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0) supports 5 scan SSIDs
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Reject scan trigger since one is already pending
Jul 3 10:28:23 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) starting connection 'Manchester'
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: disconnected -> inactive
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0/wireless): access point 'Manchester' has security, but secrets are required.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0/wireless): connection 'Manchester' has security, and secrets exist. No new secrets needed.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: SME: Trying to authenticate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.522609] wlan0: authenticate with f8:e4:fb:84:34:35
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.532790] wlan0: send auth to f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: inactive -> authenticating
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Trying to associate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.637206] wlan0: send auth to f8:e4:fb:84:34:35 (try 2/3)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.638959] wlan0: authenticated
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.641211] wlan0: associate with f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.644461] wlan0: RX AssocResp from f8:e4:fb:84:34:35 (capab=0x431 status=0 aid=5)
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Associated with f8:e4:fb:84:34:35
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.650135] wlan0: associated
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142227.650165] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 3 10:28:24 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associating -> associated
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: WPA: Key negotiation completed with f8:e4:fb:84:34:35 [PTK=CCMP GTK=CCMP]
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:e4:fb:84:34:35 completed [id=0 id_str=]
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associated -> completed
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Manchester'.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Beginning IP6 addrconf.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC dhclient: Listening on LPF/wlan0/4c:eb:42:29:bd:fa
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC dhclient: Sending on LPF/wlan0/4c:eb:42:29:bd:fa
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC dhclient: DHCPREQUEST of 192.168.1.3 on wlan0 to 255.255.255.255 port 67 (xid=0x5880bd54)
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.3.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: New relevant interface wlan0.IPv4 for mDNS.
Jul 3 10:28:25 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Registering new address record for 192.168.1.3 on wlan0.IPv4.
Jul 3 10:28:26 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Jul 3 10:28:26 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Jul 3 10:28:26 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Jul 3 10:28:26 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Policy set 'Manchester' (wlan0) as default for IPv4 routing and DNS.
Jul 3 10:28:27 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) successful, device activated.
Jul 3 10:28:27 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::4eeb:42ff:fe29:bdfa.
Jul 3 10:28:27 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: New relevant interface wlan0.IPv6 for mDNS.
Jul 3 10:28:27 dustin-HP-Pavilion-dv6-Notebook-PC avahi-daemon[973]: Registering new address record for fe80::4eeb:42ff:fe29:bdfa on wlan0.*.
Jul 3 10:28:44 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): IP6 addrconf timed out or failed.
Jul 3 10:28:44 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jul 3 10:28:44 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jul 3 10:28:44 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 3 10:28:45 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:29:28 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.675068] wlan0: deauthenticated from f8:e4:fb:84:34:35 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Jul 3 10:30:31 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:e4:fb:84:34:35 reason=6
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: SME: Trying to authenticate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.708513] wlan0: authenticate with f8:e4:fb:84:34:35
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: completed -> authenticating
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.731300] wlan0: send auth to f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Trying to associate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.735163] wlan0: authenticated
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.736121] wlan0: associate with f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:30:48 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jul 3 10:30:49 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.752522] wlan0: RX AssocResp from f8:e4:fb:84:34:35 (capab=0x431 status=0 aid=5)
Jul 3 10:30:49 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Associated with f8:e4:fb:84:34:35
Jul 3 10:30:49 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142373.758356] wlan0: associated
Jul 3 10:30:49 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associating -> associated
Jul 3 10:30:50 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: WPA: Key negotiation completed with f8:e4:fb:84:34:35 [PTK=CCMP GTK=CCMP]
Jul 3 10:30:50 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:e4:fb:84:34:35 completed [id=0 id_str=]
Jul 3 10:30:50 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associated -> completed
Jul 3 10:31:54 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.859561] wlan0: deauthenticated from f8:e4:fb:84:34:35 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:e4:fb:84:34:35 reason=6
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: SME: Trying to authenticate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.882481] wlan0: authenticate with f8:e4:fb:84:34:35
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: completed -> authenticating
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.895461] wlan0: send auth to f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Trying to associate with f8:e4:fb:84:34:35 (SSID='Manchester' freq=2457 MHz)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.909928] wlan0: authenticated
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.913998] wlan0: associate with f8:e4:fb:84:34:35 (try 1/3)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.917490] wlan0: RX AssocResp from f8:e4:fb:84:34:35 (capab=0x431 status=0 aid=5)
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: Associated with f8:e4:fb:84:34:35
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC kernel: [142469.924535] wlan0: associated
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: WPA: Key negotiation completed with f8:e4:fb:84:34:35 [PTK=CCMP GTK=CCMP]
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:e4:fb:84:34:35 completed [id=0 id_str=]
Jul 3 10:32:25 dustin-HP-Pavilion-dv6-Notebook-PC NetworkManager[984]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Jul 3 10:33:37 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Jul 3 10:43:37 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: message repeated 5 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Jul 3 10:45:37 dustin-HP-Pavilion-dv6-Notebook-PC wpa_supplicant[1049]: wlan0: CTRL-EVENT-SCAN-STARTED
Re: Mint 17 wifi issues vs 16
The weird thing is that, again, it just started when Mint 17 was installed. Like you said, it may be a combo of things:
1. Mint 17 changed some interaction with the way it handles the wireless conversation with my router that it doesn't like, even though fresh and multiple kernels were tried.
2. The router coincidentally broke when I upgraded.
3. Some Transmission setting is causing MOST of the issues
4. Verizon doesn't like me using the max bandwidth I pay for and is either now changing its policy (unannounced) and Mint 17 has nothing to do with it
All of that just still doesn't explain other people's problems, however.
1. Mint 17 changed some interaction with the way it handles the wireless conversation with my router that it doesn't like, even though fresh and multiple kernels were tried.
2. The router coincidentally broke when I upgraded.
3. Some Transmission setting is causing MOST of the issues
4. Verizon doesn't like me using the max bandwidth I pay for and is either now changing its policy (unannounced) and Mint 17 has nothing to do with it
All of that just still doesn't explain other people's problems, however.
Re: Mint 17 wifi issues vs 16
I found this
http://askubuntu.com/questions/465848/f ... untu-14-04
But I think we already set the country codes or at least one of the settings were correct. It appears that most of the messages in syslog are from IPv6
http://askubuntu.com/questions/465848/f ... untu-14-04
But I think we already set the country codes or at least one of the settings were correct. It appears that most of the messages in syslog are from IPv6
Re: Mint 17 wifi issues vs 16
WOW!JeremyB wrote:I found this
http://askubuntu.com/questions/465848/f ... untu-14-04
But I think we already set the country codes or at least one of the settings were correct. It appears that most of the messages in syslog are from IPv6
Some of that stuff is strikingly familiar to what we have been doing.
Which ones haven't we tried?
Remember, all of the tweaks we have done so far have remained as we tried them, except the IPv6. That one really made no difference.
What remains is the consistency when not downloading big files is pretty much gone. In fact, I don't think I have had any disconnections while doing Internet light activities in the last day or two. It is simply the bandwidth maxing big files that are the issue (as of now).
The thing that sounds familiar is the having to toggle the wireless to get it to come back on. We had to to correct the tweak that, when disconnected, tried to reconnect on its own. That just led to finding the network, attempting to connect, then failing repeatedly.
I don't remember setting the country code. Do you think that will do anything? If so, how do we go about it?
Any ideas?
Re: Mint 17 wifi issues vs 16
I just tested again, by direct downloading about 7 Mint .iso simultaneously. It can't be Transmission or torrents only.
Re: Mint 17 wifi issues vs 16
To check the country code that is set and there is a third one I never hear anyone talking about is
Code: Select all
iw reg get
Code: Select all
cat /etc/default/crda | grep -i regdomain
Code: Select all
cat /sys/module/cfg80211/parameters/ieee80211_regdom
Re: Mint 17 wifi issues vs 16
First:JeremyB wrote:To check the country code that is setCode: Select all
iw reg get
and there is a third one I never hear anyone talking about isCode: Select all
cat /etc/default/crda | grep -i regdomain
Code: Select all
cat /sys/module/cfg80211/parameters/ieee80211_regdom
country US:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 20), DFS
(5490 - 5600 @ 40), (3, 20), DFS
(5650 - 5710 @ 40), (3, 20), DFS
(5735 - 5835 @ 40), (3, 30)
(57240 - 63720 @ 2160), (N/A, 40)
Second:
# Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set
REGDOMAIN=
Third:
00
Is that all correct?
Re: Mint 17 wifi issues vs 16
Not really all correctFelony wrote:First:JeremyB wrote:To check the country code that is setCode: Select all
iw reg get
and there is a third one I never hear anyone talking about isCode: Select all
cat /etc/default/crda | grep -i regdomain
Code: Select all
cat /sys/module/cfg80211/parameters/ieee80211_regdom
country US:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 20), DFS
(5490 - 5600 @ 40), (3, 20), DFS
(5650 - 5710 @ 40), (3, 20), DFS
(5735 - 5835 @ 40), (3, 30)
(57240 - 63720 @ 2160), (N/A, 40)
Second:
# Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set
REGDOMAIN=
Third:
00
Is that all correct?
Code: Select all
sudo gedit /etc/default/crda
The third part might not matter at all but let's see is the crda change does anything. What model is your FIOS?
Re: Mint 17 wifi issues vs 16
I made the change and will test again.
What do you mean by, "What model is my FIOS?" Do you mean the brand/model of the router?
If so, it is an Actiontec, model: MI424WR-GEN3, Firmware: 40.21.10.3 (current-up to date)
BTW, there are a TON of settings on the router and I happened to notice that IPv6 was already disabled on it, if that matters.
What do you mean by, "What model is my FIOS?" Do you mean the brand/model of the router?
If so, it is an Actiontec, model: MI424WR-GEN3, Firmware: 40.21.10.3 (current-up to date)
BTW, there are a TON of settings on the router and I happened to notice that IPv6 was already disabled on it, if that matters.
Re: Mint 17 wifi issues vs 16
Should disable IPv6 in Network Manager also, or ignore is the correct term.Felony wrote:I made the change and will test again.
What do you mean by, "What model is my FIOS?" Do you mean the brand/model of the router?
If so, it is an Actiontec, model: MI424WR-GEN3, Firmware: 40.21.10.3 (current-up to date)
BTW, there are a TON of settings on the router and I happened to notice that IPv6 was already disabled on it, if that matters.
Can you switch the router do different network modes- 11b, 11g, 11n, and combinations of those? It might be worth trying
Code: Select all
cat /var/log/syslog | grep -i tlp
Re: Mint 17 wifi issues vs 16
I must need more sleep, that isn't Ipv6 addresses, they are MAC addresses. Are there any kernel updates listed in mint update, update manager/view/linux kernelsJeremyB wrote:I found this
http://askubuntu.com/questions/465848/f ... untu-14-04
But I think we already set the country codes or at least one of the settings were correct. It appears that most of the messages in syslog are from IPv6
I wonder if 3.13.0-29 might work as it was released by Ubuntu and it may fix things that are not fixed in upstream kernel releases yet. When rebooting you will likely have to choose "previous linux mint versions" in grub and select the 3.13.0-29 one
Re: Mint 17 wifi issues vs 16
That TLP command did nothing. It just put me back to a prompt.
I found the following in my router that had a drop down box to only choose one of the options:
Compatibility Mode: 802.11b/g/n
Legacy Mode: 802.11b/g
Performance Mode: 802.11n
It was set on Compatibility Mode, so I'm switching to Legacy Mode and testing again. I hope I don't lose performance with "n"
Update: I did the changes in the router and it still disconnected during downloads.
I'm going to install the 3.13.0-29 and see what happens. I just need to find where to download it! LOL!
I found the following in my router that had a drop down box to only choose one of the options:
Compatibility Mode: 802.11b/g/n
Legacy Mode: 802.11b/g
Performance Mode: 802.11n
It was set on Compatibility Mode, so I'm switching to Legacy Mode and testing again. I hope I don't lose performance with "n"
Update: I did the changes in the router and it still disconnected during downloads.
I'm going to install the 3.13.0-29 and see what happens. I just need to find where to download it! LOL!