From owner-freebsd-net@FreeBSD.ORG Fri Sep 14 18:32:32 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43B5010656A8; Fri, 14 Sep 2012 18:32:32 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 27D738FC14; Fri, 14 Sep 2012 18:32:31 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8EIWVJi071200; Fri, 14 Sep 2012 11:32:31 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <5053783E.3080504@rawbw.com> Date: Fri, 14 Sep 2012 11:32:30 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Glen Barber References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> <20120913165111.GA2436@glenbarber.us> <5052D82E.4050005@rawbw.com> <50536DBA.9000000@rawbw.com> <20120914175402.GC1323@glenbarber.us> In-Reply-To: <20120914175402.GC1323@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 18:32:32 -0000 On 09/14/2012 10:54, Glen Barber wrote: > Ok. Thanks for letting us know. Now wpa_supplicant starts and is operational, however '/etc/rc.d/netif start' always issues this warning: Starting wpa_supplicant /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Starting Network: lo0 ndis0 re0. Also (as a result) dhclient isn't started, but succeeds when started manually. wpa_supplicant started by hand doesn't print any errors. I can't find any option in wpa_supplicant.conf making it to write a log what is wrong. On linux it seems to be -f option for the log file. Any way to make netif more verbose? Yuri