Re: NM 7.0 not starting supplicant

[Dan Williams <dcbw redhat com>]

On Sat, 2009-02-21 at 11:52 +0000, Cliff McDiarmid wrote:
> Hi
> 
> I'm pulling my hair out with this problem
> 
> I can get a wireless connection manually, no problem, but I want to use the laptop away from home and want NM to handle the connections
> 
> I have the following installed to get wireless:
> 
> NM 7.0
> Wpa-supplicant-0.6.8
> Dbus-1,2,4
> Hal-0.5.9.1
> DHCP-4.1 client only
> Driver iwl3945
> 
> The supplicant conf file is in /etc
> 
> I'm not running the supplicant daemon at boot up(makes no difference if I do) - letting NM handle it all
> 
> I get the following error in /var/log when NM starts:
> 
> Feb 20 12:43:17 cliffhanger NetworkManager: <info>  starting... 
> Feb 20 12:43:17 cliffhanger NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess  
> Feb 20 12:43:17 cliffhanger NetworkManager: <info>  wlan0: driver is 'iwl3945'. 
> Feb 20 12:43:17 cliffhanger NetworkManager: <info>  wlan0: driver supports SSID scans (scan_capa 0x01). 
> Feb 20 12:43:17 cliffhanger NetworkManager: <info>  Found new 802.11 WiFi device 'wlan0'. 
> Feb 20 12:43:17 cliffhanger NetworkManager: <info>  (wlan0): exported as /org/freedesktop/Hal/devices/net_00_13_02_0d_3f_93 
> Feb 20 12:43:17 cliffhanger NetworkManager: <info>  Trying to start the supplicant... 
> Feb 20 12:43:17 cliffhanger NetworkManager: <info>  Trying to start the system settings daemon... 
> Feb 20 12:43:18 cliffhanger nm-system-settings: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc.
> Feb 20 12:43:21 cliffhanger NetworkManager: <info>  (wlan0): device state change: 1 -> 2 
> Feb 20 12:43:21 cliffhanger NetworkManager: <info>  (wlan0): bringing up device. 
> Feb 20 12:43:21 cliffhanger NetworkManager: <info>  (wlan0): preparing device. 
> Feb 20 12:43:21 cliffhanger NetworkManager: <info>  (wlan0): deactivating device (reason: 2). 
> Feb 20 12:43:21 cliffhanger NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
> 
> I've googled this error and have seen everything from missing scripts
> 
> /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service - I have this and the one in /etc/dbus-1

What do you get when you run this command?

sudo dbus-send --system --print-reply --dest=fi.epitest.hostap.WPASupplicant /fi/epitest/hostap/WPASupplicant fi.epitest.hostap.WPASupplicant.getInterface string:wlan0

It won't matter whether the supplicant is already running or not.

What are the contents of
your /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service file too?

Dan