From owner-freebsd-current@FreeBSD.ORG Wed May 30 01:26:31 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D2C1216A41F for ; Wed, 30 May 2007 01:26:31 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.freebsd.org (Postfix) with ESMTP id B77EE13C457 for ; Wed, 30 May 2007 01:26:31 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from [10.0.3.236] ([70.21.158.80]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JIT00I2IYO2FFP5@vms046.mailsrvcs.net> for freebsd-current@freebsd.org; Tue, 29 May 2007 20:26:27 -0500 (CDT) Date: Tue, 29 May 2007 21:33:16 -0400 From: "Alexandre \"Sunny\" Kovalenko" In-reply-to: <200705291430.14786.doconnor@gsoft.com.au> To: Daniel O'Connor Message-id: <1180488796.2977.6.camel@twinhead.rabbitslawn.verizon.net> MIME-version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port Content-type: text/plain Content-transfer-encoding: 7bit References: <200705291430.14786.doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: Re: No wpa_supplicant control socket at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2007 01:26:31 -0000 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.