From: Michael Tokarev <mjt@tls.msk.ru>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: linux-only "freshness" auth problem??
Date: Sat, 22 Aug 2015 11:39:10 +0300 [thread overview]
Message-ID: <55D8352E.9040702@msgid.tls.msk.ru> (raw)
In-Reply-To: <1440152186.2107.14.camel@sipsolutions.net>
21.08.2015 13:16, Johannes Berg wrote:
> On Fri, 2015-08-21 at 12:35 +0300, Michael Tokarev wrote:
>>
>> Aug 21 11:31:49 x200la kernel: wlan0: authenticated
>> Aug 21 11:31:49 x200la kernel: wlan0: waiting for beacon from c0:4a:00:49:1b:f2
>
> Do you see any *kernel* messages after this? I'm half expecting to see
> that the beacon never arrives, or something like that?
The kernel log is repeated. The next log line is again scanning start,
since NetworkManager (or wpa_supplicant, I'm not familiar with the machinery
involved) request scan again.
> Are the hotels running similar equipment perhaps? If rebooting the AP
> helps then perhaps the APs aren't actually beaconing quite properly -
> maybe you could put the card into sniffer mode (monitor mode) and
> capture what's going on over the air for a bit after this happened?
Can you give some more specific comments please? We just rebooted the
AP the next time, it all started working again, and I need to install
all the necessary tools while it is working ;) Since I'm not familiar
with wifi machinery, maybe you can give me specific command lines to
run? :)
Thank you!
/mjt
next prev parent reply other threads:[~2015-08-22 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 9:35 linux-only "freshness" auth problem?? Michael Tokarev
2015-08-21 9:53 ` Rafał Miłecki
2015-08-22 8:51 ` Michael Tokarev
[not found] ` <55D83809.7040305@tls.msk.ru>
2015-08-22 8:52 ` Michael Tokarev
2015-08-21 10:16 ` Johannes Berg
2015-08-22 8:39 ` Michael Tokarev [this message]
2015-08-24 12:37 ` Johannes Berg
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=55D8352E.9040702@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).