From: Dan Williams <dcbw@redhat.com>
To: Detlev Casanova <detlev.casanova@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
laurent.pinchart@ideasonboard.com
Subject: Re: NetworkManager not listing access points
Date: Mon, 23 Sep 2013 11:13:49 -0500 [thread overview]
Message-ID: <1379952829.2475.16.camel@dcbw.foobar.com> (raw)
In-Reply-To: <3006906.Q9n0kfrGGo@naboo>
On Sun, 2013-09-22 at 16:20 +0200, Detlev Casanova wrote:
> Le samedi 21 septembre 2013 22:51:59 Johannes Berg a écrit :
> > On Thu, 2013-09-19 at 07:58 +0200, Detlev Casanova wrote:
> > > Here is the output (attached file for formatting)
> >
> > Was that from the good case? The bad case would have been
> more
> > interesting.
>
> This is both cases. I made another one and here, I can give more
> details:
>
> Network manager is trying to list APs and fails until time
> 1379858724.386569
Ok, the logs indicate that the driver simply doesn't see any scan
results:
1379858724.381522: Received scan results (0 BSSes)
Then 20 seconds later (after the explicit iwlist), it finds some scan
results:
1379858746.953924: Received scan results (3 BSSes)
So I'm not sure what's going on here, but I don't think NetworkManager
is the issue; it's likely in the supplicant's scanning code or in the
driver itself. NetworkManager asks the supplicant to scan with both the
wildcard SSID and any hidden-tagged SSID, and the wildcard SSID should
ensure that all available APs are found.
Johannes, does anything else jump out at you in the logs?
Dan
> The The first "iwlist wlan0 scan" is done juste after the log line
> (1379858738.682054). It lists the APs in range in the console but
> not in the Network Manager ui.
>
> The second "iwlist wlan0 scan" is done at time 1379858739.802067
> and APs are being listed in the console and in the Network Manager
> UI.
>
> After that, NM will connect to the acces point with SSID "Maison".
>
> It also looks like the listing in Network Manager comes between the
> moment "iwlist wlan0 scan" is run for the second time and the
> moment is shows its output on the console.
>
> Detlev.
next prev parent reply other threads:[~2013-09-23 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 20:47 NetworkManager not listing access points Detlev Casanova
2013-09-19 4:16 ` Dan Williams
2013-09-19 5:58 ` Detlev Casanova
2013-09-21 20:51 ` Johannes Berg
2013-09-22 14:20 ` Detlev Casanova
2013-09-23 16:13 ` Dan Williams [this message]
2013-09-29 19:29 ` Detlev Casanova
2013-10-02 9:08 ` Johannes Berg
[not found] ` <2916718.7t7kLXuBQV@naboo>
2013-10-07 7:40 ` Johannes Berg
2013-10-11 15:43 ` Detlev Casanova
2013-10-17 14:38 ` Johannes Berg
2013-10-17 16:19 ` Will Hawkins
2013-10-21 13:06 ` Johannes Berg
2013-10-21 20:20 ` Will Hawkins
2013-09-29 21:10 ` Rafał Miłecki
2013-09-29 21:11 ` Rafał Miłecki
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=1379952829.2475.16.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=detlev.casanova@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=laurent.pinchart@ideasonboard.com \
--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 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.