Re: Problem in associating with a given AP

[Dan Williams <dcbw redhat com>]

On Tue, 2011-08-16 at 21:25 -0700, Vikram Ravindra wrote:
> Hi,
> 
> I believe that this is the extract of the log file that you are looking for.
> It shows that only the essid, scan_ssid and key_mgmt are written into the
> configuration file for the supplicant, and not the BSSID of the AP. Please
> let me know if there is something else that you may need.

The BSSID itself is typically not written to the supplicant because that
prevents roaming between APs in an SSID.  Additionally, the supplicant
will handle roaming between APs in the SSID based on signal strength and
other factors, so it's mostly pointless.  The only cases where it's
really useful to lock to a single AP's BSSID is when you have multiple
networks called eg 'linksys' that are not part of the same actual
network/SSID and you know exactly the one you need to use.

Dan

> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Activation (wlan0)
> Stage 1 of 5 (Device Prepare) scheduled...
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Activation (wlan0)
> Stage 1 of 5 (Device Prepare) started...
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Activation (wlan0)
> Stage 2 of 5 (Device Configure) scheduled...
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Activation (wlan0)
> Stage 1 of 5 (Device Prepare) complete.
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> (wlan0): supplicant
> connection state:  completed -> disconnected
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Activation (wlan0)
> Stage 2 of 5 (Device Configure) starting...
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> (wlan0): device
> state change: 4 -> 5 (reason 0)
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Activation
> (wlan0/wireless): connection 'Auto WMn3' requires no security.  No secrets
> needed.
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Config: added 'ssid'
> value 'WMn3'
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Config: added
> 'scan_ssid' value '1'
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Config: added
> 'key_mgmt' value 'NONE'
> Aug 17 09:42:43 localhost NetworkManager[14236]: <info> Activation (wlan0)
> Stage 2 of 5 (Device Configure) complete.
> 
> 
> On Wed, Aug 17, 2011 at 3:54 AM, Dan Williams <dcbw@...> wrote:
> 
>     On Sun, 2011-08-14 at 22:28 -0700, Vikram Ravindra wrote:
>     > hi,
>     >
>     > I am using DBus interface to communicate with the Network Manager. I
> have
>     > used the "ActivateConnection" method, and have passed all the
> necessary
>     > arguments (like the service name, object paths of wifi, AP, etc), but
> i find
>     > that the Network Manager is not writing the details of the BSSID into
> the
>     > wpa_supplicant's configuration file. Why is it so? Please ask me for
> details
>     > that you might need to answer my query. Thanks in advance!
> 
>     Can you post some logs from NM that show what's going on?  Usually they
>     go to /var/log/messages or /var/log/daemon.log.
> 
>     Dan
> 
> 
> 
> 
> 
> -- 
> Regards,
> Vikram Ravindra.
> 
> Dan Williams wrote:
> > 
> > On Sun, 2011-08-14 at 22:28 -0700, Vikram Ravindra wrote:
> >> hi,
> >> 
> >> I am using DBus interface to communicate with the Network Manager. I have
> >> used the "ActivateConnection" method, and have passed all the necessary
> >> arguments (like the service name, object paths of wifi, AP, etc), but i
> >> find
> >> that the Network Manager is not writing the details of the BSSID into the
> >> wpa_supplicant's configuration file. Why is it so? Please ask me for
> >> details
> >> that you might need to answer my query. Thanks in advance!
> > 
> > Can you post some logs from NM that show what's going on?  Usually they
> > go to /var/log/messages or /var/log/daemon.log.
> > 
> > Dan
> > 
> > 
> > _______________________________________________
> > networkmanager-list mailing list
> > networkmanager-list gnome org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > 
> > 
>