Date: Tue, 29 May 2007 21:33:16 -0400 From: "Alexandre \"Sunny\" Kovalenko" <alex.kovalenko@verizon.net> To: Daniel O'Connor <doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: Re: No wpa_supplicant control socket at boot Message-ID: <1180488796.2977.6.camel@twinhead.rabbitslawn.verizon.net> In-Reply-To: <200705291430.14786.doconnor@gsoft.com.au> References: <200705291430.14786.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2007-05-29 at 14:30 +0930, Daniel O'Connor wrote: > I find that wpa_supplicant has no control socket when it is run at > startup, however if I restart it it comes good. > > Does anyone else see this? > > I have these options in my wpa_supplicant.conf file.. > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > You did not provide enough information about your setup, so I am not sure that my answer would be very helpful ;-( I do run wpa_supplicant at startup by means of ifconfig_ath0="WPA 10.x.x.x netmask x.x.x.x" in rc.conf I have the same entries as you at the top of wpa_supplicant.conf and I am able to use wpa_cli right after boot, which is what I suspect you refer to when you are talking about control socket being available. I do load if_ath, wlan_wep and wlan_tkip by means of the loader.conf entries. If there are other bits of setup you would like to compare, please, let me know. --- Alexandre "Sunny" Kovalenko.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1180488796.2977.6.camel>