Re: networkmanager-0.9.8.9 will not connect to wifi with non-broadcast ssid

[Dan Williams <dcbw redhat com>]

On Wed, 2014-04-30 at 13:40 +0000, John Frankish wrote:
> > > > -----Original Message-----
> > > > From: John Frankish
> > > > Sent: Friday, 25 April, 2014 17:41
> > > > To: networkmanager-list gnome org
> > > > Subject: networkmanager-0.9.8.9 will not connect to wifi with
> > > > non-broadcast ssid
> > > >
> > > > I've been trying to connect to a wap that does not broadcast the
> > > > ssid for a while without success.
> > To debug that, can you grab some detailed wpa_supplicant logs?  Run these
> > two commands, and the supplicant should start dumping logs to
> > /var/log/wpa_supplicant.log:
> >
> > sudo dbus-send --system --print-reply
> > --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1
> > org.freedesktop.DBus.Properties.Set string:fi.w1.wpa_supplicant1
> > string:DebugTimestamp variant:boolean:true
> >
> > sudo dbus-send --system --print-reply
> > --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1
> > org.freedesktop.DBus.Properties.Set string:fi.w1.wpa_supplicant1
> > string:DebugLevel variant:string:"msgdump"
>
> Thanks for the suggestion.
>
> I did the following:
> Start the NetworkManager daemon
> "startx"
> Issued the commands:
> $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1 
> org.freedesktop.DBus.Properties.Set string:fi.w1.wpa_supplicant1 string:DebugTimestamp variant:boolean:true
>
> [method return sender=:1.5 -> dest=:1.32 reply_serial=2]
>
> $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1 
> org.freedesktop.DBus.Properties.Set string:fi.w1.wpa_supplicant1 string:DebugLevel variant:string:"msgdump"
>
> [method return sender=:1.5 -> dest=:1.33 reply_serial=2]
>
> And then used network-manager-applet to connect
>
> ..but no /var/log/wpa_supplicant.log was created.
>
> Did I make a mistake in the sequence or the dbus commands?

Hmm, it does make a difference how the supplicant is executed.  So if
it's started as a system service with the path to the logfile, you'll
get one, but it may not be done on your system.  So to make sure things
happen correctly, you can:

mv /usr/sbin/wpa_supplicant /
killall -TERM wpa_supplicant
/wpa_supplicant -dddtu  <pipe/tee to whatever file you want>

and then try to connect as you normally would to reproduce the problem.
That'll ensure that you can send the log output to exactly where you
want it to go.

Dan