Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Sep 2012 11:49:50 -0700
From:      hiren panchasara <hiren.panchasara@gmail.com>
To:        Yuri <yuri@rawbw.com>
Cc:        Glen Barber <gjb@freebsd.org>, freebsd-net@freebsd.org
Subject:   Re: Why wpa_supplicant doesn't start with ndis0 interface?
Message-ID:  <CALCpEUEgwa-Dt3batjHVtvC2Un1pH=NcvsO=eLWqu8x%2BOjSEpQ@mail.gmail.com>
In-Reply-To: <5053783E.3080504@rawbw.com>
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> <alpine.BSF.2.00.1209131841480.24688@wonkity.com> <5052D82E.4050005@rawbw.com> <50536DBA.9000000@rawbw.com> <20120914175402.GC1323@glenbarber.us> <5053783E.3080504@rawbw.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 14, 2012 at 11:32 AM, Yuri <yuri@rawbw.com> wrote:

> 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?

Not sure if you looked at - man wpa_supplicant, which has
-d for debugging
-s for pumping messages to syslog

Thanks,
Hiren



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALCpEUEgwa-Dt3batjHVtvC2Un1pH=NcvsO=eLWqu8x%2BOjSEpQ>