Re: 0.9 problem

[Dan Williams <dcbw redhat com>]

On Fri, 2011-09-30 at 21:10 +0300, Алекс Скоропад wrote:
> 30.09.2011 20:23, Dan Williams пишет:
> > On Fri, 2011-09-30 at 20:03 +0300, Алекс Скоропад wrote:
> >> 30.09.2011 08:02, Dan Williams пишет:
> >>> On Sun, 2011-09-25 at 19:11 +0300, Алекс Скоропад wrote:
> >>>> Here they are:
> >>>> Daemon.log - http://goo.gl/gf0q3
> >>>> wpa_supplicant.log - http://goo.gl/VCEqA
> >>> In this case, can you add the following
> >>> to /etc/NetworkManager/NetworkManager.conf ?
> >>>
> >>> [logging]
> >>> level=DEBUG
> >>> domains=CORE,HW,DEVICE,WIFI,WIFI_SCAN
> >>>
> >>> Then restart NM, and try again?  It appears that your AP is not
> >>> broadcasting its SSID; but after the first time you connect NM should be
> >>> able to cache the BSSID and automatically connect the next time.  We
> >>> need to see if NM is actually receiving the scan result from the
> >>> supplicant first.
> >>>
> >>> Next, look at /var/lib/NetworkManager/seen-bssids and see if you find
> >>> the BSSID 00:0e:f4:e0:fb:28 in it.
> >>>
> >>> Dan
> >>>
> >> I added this section to NetworkManager.conf, but with this section
> >> network interface failed to configure:
> >> daemon.log - http://goo.gl/nk4t3
> >> wpa_supplicant.log - http://goo.gl/1u4mu
> > This could be one problem:
> >
> > Sep 30 19:29:49 Scaramush NetworkManager[1494]:<info>  (ra0): driver
> > does not support SSID scans (scan_capa 0x00).
> >
> > This indicates that the driver you have is does not correctly support
> > specific SSID scans, which are used to more quickly and easily connect
> > to hidden SSID networks.  This is a bug in the driver, as most upstream
> > drivers included in the Linux kernel have advertised support for this
> > feature since 2008 or 2009.
> >
> > Also, do you have any entry for 00:0e:f4:e0:fb:28
> > in /var/lib/NetworkManager/seen-bssids ?
> >
> > Dan
> >
> Well, the problem was solved with driver from ralink, but this strings
> 
> <info>  (ra0): driver does not support SSID scans (scan_capa 0x00).
> 
> are still in logs

Good to hear, but without the SSID scan capability it'll be somewhat
slower to connect to hidden SSID networks.  I've added more debug
logging to NM to address this problem going forward, so if it happens
again we have a better chance of determining why NM wasn't
autoconnecting even though it seems to have been able to match the AP up
with the stored SSID.

Dan