From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Aleksandar Milivojevic <alex@milivojevic.org>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Wolfgang Kufner <wolfgang.kufner@gmail.com>,
Luis Correia <buga@loide.net>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>
Subject: Re: [rt2x00-users] Linksys WUSB600N v1 disconnecting from AP
Date: Sat, 8 Jan 2011 10:47:18 +0100 [thread overview]
Message-ID: <201101081047.18475.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <AANLkTintU_vSt5eWoma4_d9tNCxPpOfpGZMq7XXppjpP@mail.gmail.com>
Am Samstag, 8. Januar 2011 schrieb Aleksandar Milivojevic:
> Running 'iw event -t' shows a lot of disassociation due to inactivity.
> This happens even if there is regular flow of traffic (for example, I
> start ping to my AP and leave it running, or I leave Pandora streaming
> music in the browser).
>
> Below is example of output of 'iw event -t' (these lines repeat in the
> output at irregularl intervals):
>
> 1294464037.037450: wlan0 (phy #0): deauth 00:1c:10:ea:2a:cb ->
> 00:1e:52:79:e9:ff reason 4: Disassociated due to inactivity
> 1294464037.037538: wlan0 (phy #0): disconnected (local request)
Aha, so it's not the AP disassociating you but it's your client disconnecting
on its own. Mind to provide the wpa_supplicant log for the same situation when
run with "-ddt"?
Helmut
next prev parent reply other threads:[~2011-01-08 9:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim0AM3=T=TMu79ZQi79+CKANamBcz620n2xm8bW@mail.gmail.com>
2011-01-04 18:46 ` [rt2x00-users] Linksys WUSB600N v1 disconnecting from AP Helmut Schaa
2011-01-04 19:01 ` Luis Correia
[not found] ` <AANLkTi=KFG-7GPw2=6VTZqEceEcJM6OdWoTQaN_83NqP@mail.gmail.com>
[not found] ` <AANLkTikREOFV+WGWgo9yh9bTrz346kF0muKE8gs5N+km@mail.gmail.com>
2011-01-04 21:53 ` Aleksandar Milivojevic
2011-01-04 22:31 ` Wolfgang Kufner
2011-01-05 6:57 ` Aleksandar Milivojevic
2011-01-05 10:32 ` Wolfgang Kufner
2011-01-06 4:11 ` Aleksandar Milivojevic
2011-01-06 7:09 ` Aleksandar Milivojevic
2011-01-06 16:31 ` Aleksandar Milivojevic
2011-01-07 2:44 ` Luis R. Rodriguez
2011-01-07 10:11 ` Helmut Schaa
2011-01-07 19:46 ` Aleksandar Milivojevic
2011-01-07 20:22 ` Luis R. Rodriguez
2011-01-07 22:13 ` Peter Stuge
2011-01-07 22:18 ` Luis R. Rodriguez
2011-01-07 23:00 ` Peter Stuge
2011-01-07 23:26 ` Jouni Malinen
2011-01-07 22:54 ` Aleksandar Milivojevic
2011-01-08 6:14 ` Aleksandar Milivojevic
2011-01-08 9:47 ` Helmut Schaa [this message]
2011-01-10 7:12 ` Aleksandar Milivojevic
2011-01-10 7:30 ` Gertjan van Wingerde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201101081047.18475.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=alex@milivojevic.org \
--cc=buga@loide.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=users@rt2x00.serialmonkey.com \
--cc=wolfgang.kufner@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.