Some relevant bits:
Sep 11 16:49:38 Arbeits-PC NetworkManager[1104]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Sep 11 16:49:44 Arbeits-PC kernel: [ 1749.454788] wlan0: Connection to AP a0:f3:c1:05:80:ec lost
Sep 11 16:49:45 Arbeits-PC wpa_supplicant[1205]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:05:80:ec reason=4
Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0): supplicant interface state: completed -> disconnected
Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Sep 11 16:49:45 Arbeits-PC wpa_supplicant[1205]: wlan0: SME: Trying to authenticate with a0:f3:c1:05:80:ec (SSID='WG-WLAN' freq=2427 MHz)
Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.282343] wlan0: authenticate with a0:f3:c1:05:80:ec
Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.306287] wlan0: send auth to a0:f3:c1:05:80:ec (try 1/3)
Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.410098] wlan0: send auth to a0:f3:c1:05:80:ec (try 2/3)
Sep 11 16:49:46 Arbeits-PC kernel: [ 1750.514232] wlan0: send auth to a0:f3:c1:05:80:ec (try 3/3)
Sep 11 16:49:46 Arbeits-PC kernel: [ 1750.618374] wlan0: authentication with a0:f3:c1:05:80:ec timed out
So the AP is disconnecting the device a couple seconds with reason 4,
which is "Disassociated due to inactivity". My thought is that this
points to a driver bug (Larry?).
Dan
So what should i do?
2013/9/11 Larry Finger <[email protected]>:
> On 09/11/2013 11:14 AM, Dan Williams wrote:
>>
>> Some relevant bits:
>>
>> Sep 11 16:49:38 Arbeits-PC NetworkManager[1104]: <info> (wlan0):
>> supplicant interface state: 4-way handshake -> completed
>> Sep 11 16:49:44 Arbeits-PC kernel: [ 1749.454788] wlan0: Connection to AP
>> a0:f3:c1:05:80:ec lost
>> Sep 11 16:49:45 Arbeits-PC wpa_supplicant[1205]: wlan0:
>> CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:05:80:ec reason=4
>> Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0):
>> supplicant interface state: completed -> disconnected
>> Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0):
>> supplicant interface state: disconnected -> scanning
>> Sep 11 16:49:45 Arbeits-PC wpa_supplicant[1205]: wlan0: SME: Trying to
>> authenticate with a0:f3:c1:05:80:ec (SSID='WG-WLAN' freq=2427 MHz)
>> Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.282343] wlan0: authenticate with
>> a0:f3:c1:05:80:ec
>> Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0):
>> supplicant interface state: scanning -> authenticating
>> Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.306287] wlan0: send auth to
>> a0:f3:c1:05:80:ec (try 1/3)
>> Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.410098] wlan0: send auth to
>> a0:f3:c1:05:80:ec (try 2/3)
>> Sep 11 16:49:46 Arbeits-PC kernel: [ 1750.514232] wlan0: send auth to
>> a0:f3:c1:05:80:ec (try 3/3)
>> Sep 11 16:49:46 Arbeits-PC kernel: [ 1750.618374] wlan0: authentication
>> with a0:f3:c1:05:80:ec timed out
>>
>> So the AP is disconnecting the device a couple seconds with reason 4,
>> which is "Disassociated due to inactivity". My thought is that this
>> points to a driver bug (Larry?).
>
>
> Possibly, but for reference, my Edimax EW-7811Un has been running for 37
> hours. During that time, I have had no deauthentications and only 2
> instances of the "AP lost" reconnections. The latter is what I am currently
> trying to fix, but at that error rate, it is difficult. I am running the
> latest 3.11 kernel from wireless testing.
>
> The only thing I am doing that is unusual is that I am pinging my router at
> a 5 second interval using the command
>
> ping -i5 192.168.1.1
>
> It is possible that I am preventing a power save operation, which is making
> a difference.
>
> Larry
>
On 09/11/2013 11:14 AM, Dan Williams wrote:
> Some relevant bits:
>
> Sep 11 16:49:38 Arbeits-PC NetworkManager[1104]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
> Sep 11 16:49:44 Arbeits-PC kernel: [ 1749.454788] wlan0: Connection to AP a0:f3:c1:05:80:ec lost
> Sep 11 16:49:45 Arbeits-PC wpa_supplicant[1205]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a0:f3:c1:05:80:ec reason=4
> Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0): supplicant interface state: completed -> disconnected
> Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0): supplicant interface state: disconnected -> scanning
> Sep 11 16:49:45 Arbeits-PC wpa_supplicant[1205]: wlan0: SME: Trying to authenticate with a0:f3:c1:05:80:ec (SSID='WG-WLAN' freq=2427 MHz)
> Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.282343] wlan0: authenticate with a0:f3:c1:05:80:ec
> Sep 11 16:49:45 Arbeits-PC NetworkManager[1104]: <info> (wlan0): supplicant interface state: scanning -> authenticating
> Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.306287] wlan0: send auth to a0:f3:c1:05:80:ec (try 1/3)
> Sep 11 16:49:45 Arbeits-PC kernel: [ 1750.410098] wlan0: send auth to a0:f3:c1:05:80:ec (try 2/3)
> Sep 11 16:49:46 Arbeits-PC kernel: [ 1750.514232] wlan0: send auth to a0:f3:c1:05:80:ec (try 3/3)
> Sep 11 16:49:46 Arbeits-PC kernel: [ 1750.618374] wlan0: authentication with a0:f3:c1:05:80:ec timed out
>
> So the AP is disconnecting the device a couple seconds with reason 4,
> which is "Disassociated due to inactivity". My thought is that this
> points to a driver bug (Larry?).
Possibly, but for reference, my Edimax EW-7811Un has been running for 37 hours.
During that time, I have had no deauthentications and only 2 instances of the
"AP lost" reconnections. The latter is what I am currently trying to fix, but at
that error rate, it is difficult. I am running the latest 3.11 kernel from
wireless testing.
The only thing I am doing that is unusual is that I am pinging my router at a 5
second interval using the command
ping -i5 192.168.1.1
It is possible that I am preventing a power save operation, which is making a
difference.
Larry
On 11/09/13 17:33, Larry Finger wrote:
>> So the AP is disconnecting the device a couple seconds with reason 4,
>> which is "Disassociated due to inactivity". My thought is that this
>> points to a driver bug (Larry?).
>
> Possibly, but for reference, my Edimax EW-7811Un has been running for 37
> hours. During that time, I have had no deauthentications and only 2
> instances of the "AP lost" reconnections. The latter is what I am
> currently trying to fix, but at that error rate, it is difficult. I am
> running the latest 3.11 kernel from wireless testing.
>
> The only thing I am doing that is unusual is that I am pinging my router
> at a 5 second interval using the command
>
> ping -i5 192.168.1.1
>
> It is possible that I am preventing a power save operation, which is
> making a difference.
Hi Larry,
For comparison, what does your device report when plugged in? My device
reports this:
Sep 10 00:28:41 kentang kernel: [90532.399226] usb 4-1.2: new high-speed
USB device number 26 using ehci-pci
Sep 10 00:28:41 kentang kernel: [90532.492624] usb 4-1.2: New USB device
found, idVendor=0bda, idProduct=8176
Sep 10 00:28:41 kentang kernel: [90532.492627] usb 4-1.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Sep 10 00:28:41 kentang kernel: [90532.492629] usb 4-1.2: Manufacturer:
Realtek
Sep 10 00:28:41 kentang kernel: [90532.492630] usb 4-1.2: SerialNumber:
00e04c000001
Sep 10 00:28:41 kentang kernel: [90532.502454] rtl8192cu: Chip version 0x10
Sep 10 00:28:42 kentang kernel: [90532.581772] rtl8192cu: MAC address:
00:0b:81:89:81:b8
Sep 10 00:28:42 kentang kernel: [90532.581776] rtl8192cu: Board Type 0
Also what type of USB port are you using? I'm plugged direct (no hub)
into a ehci-pci port on a laptop if that makes a difference to power?
ATB,
Mark.
On 09/11/2013 12:11 PM, Mark Cave-Ayland wrote:
> On 11/09/13 17:33, Larry Finger wrote:
>
>>> So the AP is disconnecting the device a couple seconds with reason 4,
>>> which is "Disassociated due to inactivity". My thought is that this
>>> points to a driver bug (Larry?).
>>
>> Possibly, but for reference, my Edimax EW-7811Un has been running for 37
>> hours. During that time, I have had no deauthentications and only 2
>> instances of the "AP lost" reconnections. The latter is what I am
>> currently trying to fix, but at that error rate, it is difficult. I am
>> running the latest 3.11 kernel from wireless testing.
>>
>> The only thing I am doing that is unusual is that I am pinging my router
>> at a 5 second interval using the command
>>
>> ping -i5 192.168.1.1
>>
>> It is possible that I am preventing a power save operation, which is
>> making a difference.
>
> Hi Larry,
>
> For comparison, what does your device report when plugged in? My device reports
> this:
>
> Sep 10 00:28:41 kentang kernel: [90532.399226] usb 4-1.2: new high-speed USB
> device number 26 using ehci-pci
> Sep 10 00:28:41 kentang kernel: [90532.492624] usb 4-1.2: New USB device found,
> idVendor=0bda, idProduct=8176
> Sep 10 00:28:41 kentang kernel: [90532.492627] usb 4-1.2: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
> Sep 10 00:28:41 kentang kernel: [90532.492629] usb 4-1.2: Manufacturer: Realtek
> Sep 10 00:28:41 kentang kernel: [90532.492630] usb 4-1.2: SerialNumber:
> 00e04c000001
> Sep 10 00:28:41 kentang kernel: [90532.502454] rtl8192cu: Chip version 0x10
> Sep 10 00:28:42 kentang kernel: [90532.581772] rtl8192cu: MAC address:
> 00:0b:81:89:81:b8
> Sep 10 00:28:42 kentang kernel: [90532.581776] rtl8192cu: Board Type 0
>
> Also what type of USB port are you using? I'm plugged direct (no hub) into a
> ehci-pci port on a laptop if that makes a difference to power?
My device has USB ID of 7392:7811. The logged data are as follows:
[ 2.844078] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 3.120082] usb 1-4: new high-speed USB device number 3 using ehci-pci
[ 22.448552] rtl8192cu: Chip version 0x10
[ 22.649915] rtl8192cu: MAC address: 00:1f:1f:c8:8e:cb
[ 22.649926] rtl8192cu: Board Type 0
I am plugged into an ehci port on my laptop; however, the power-saving feature I
discussed refers to the ability of wireless devices to shut down their power
during a period when no packets are expected. The station (STA) informs the
access point (AP) that it is going into that mode, and the AP will not send any
data until the STA is once again ready. Many drivers have the ability to disable
this feature on module loading, but not rtl8192cu (yet). I am looking into
adding this code.
Larry
On 09/11/2013 11:53 AM, Vincent Thiele wrote:
> So what should i do?
Open a command-line window and enter the command
ping x.y.z.w
where the IP address of your router replaces the x, y, z, and w.
Larry