From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 01:59:12 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 28CC71065670; Thu, 13 Sep 2012 01:59:12 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id EA3DB8FC0A; Thu, 13 Sep 2012 01:59:11 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:100]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 501E423F6D9; Wed, 12 Sep 2012 21:59:08 -0400 (EDT) Date: Wed, 12 Sep 2012 21:59:04 -0400 From: Glen Barber To: Yuri Message-ID: <20120913015904.GC1341@glenbarber.us> References: <505136E8.6010708@rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nmemrqcdn5VTmUEE" Content-Disposition: inline In-Reply-To: <505136E8.6010708@rawbw.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) 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: Thu, 13 Sep 2012 01:59:12 -0000 --nmemrqcdn5VTmUEE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 12, 2012 at 06:29:12PM -0700, Yuri wrote: > I have the ndis based driver preloaded during boot. It creates ndis0=20 > interface. > /etc/rc.conf has the following lines: > wlans_ndis0=3D"wlan0" > ifconfig_wlan0=3D"WPA DHCP" >=20 > However, wlan0 device isn't being created during system boot or during=20 > '/etc/rc.d/netif start'. > '/etc/rc.d/wpa_supplicant start' also silently doesn't do anything. >=20 > Only commands typed manually: > > ifconfig wlan create wlandev ndis0 > > wpa_supplicant -D ndis -i wlan0 -c /etc/wpa_supplicant.conf > > dhclient wlan0 > start wireless network. >=20 > On another machine with ath0 wireless interface similar configuration=20 > works fine. >=20 > How can I understand why wireless doesn't start during boot? >=20 What is 'uname -a'? I'm surprised you can have ndis(4) load during boot. Recent machines I tried to do that have panic'd during boot. Can you try creating a crontab entry to load ndis(4) post-boot? # start ndis(4) post-boot @reboot root /sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1 Something similar to that worked for me to get the device to work close to boot time, without panic. Once loaded, wpa_supplicant(8) worked fine. Please also see: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/165630 which I would would be MFC'd already... Glen --nmemrqcdn5VTmUEE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQUT3oAAoJEFJPDDeguUaj6XUH/RGJJcOZ/6sgHtUh98MulS02 UQpsAdEpafkC833jWXfcFg/0fz0sdPRuoRbeVeuZLyZ/98dBQ1bBCBk3d1Q10bnp pVACFzuL9Lqg8seF/VsRuPgcY/9IxkNJG40vAPEPsEvZ0OQKf2P4tm5w+1UXEOrA T5DgPVkeuvUVxlqbsgSBM0hzICZ+Msq0gt/4civkkN0C0X+M5jrxC8Fb8OiHSpi1 VzYArOCwMMeE5qbJuSUN81edJka5MVBW7vYM9eUFgorAGfKW2MpCtHVXQw9KVwgg 01KqUHiT6V9ev5tbvAHSbH/mWckmkzoHB+sUGBm6zVC5jsLnTcspgN7H2UFYUfA= =yr0H -----END PGP SIGNATURE----- --nmemrqcdn5VTmUEE--