From owner-freebsd-net@FreeBSD.ORG  Thu Sep 13 02:58:22 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 6BDBD106564A;
	Thu, 13 Sep 2012 02:58:22 +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 540C48FC08;
	Thu, 13 Sep 2012 02:58:21 +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 q8D2wLF3071461;
	Wed, 12 Sep 2012 19:58:21 -0700 (PDT) (envelope-from yuri@rawbw.com)
Message-ID: <50514BCC.3010607@rawbw.com>
Date: Wed, 12 Sep 2012 19:58:20 -0700
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: Glen Barber <gjb@freebsd.org>
References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us>
In-Reply-To: <20120913015904.GC1341@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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 02:58:22 -0000

On 09/12/2012 18:59, Glen Barber wrote:
> What is 'uname -a'?

FreeBSD xxx.xxx.org 9.0-STABLE FreeBSD 9.0-STABLE #0: Mon Jul  9 
19:29:05 PDT 2012     xxx@xxx.org:/usr/obj/usr/src/sys/GENERIC i386

>
> I'm surprised you can have ndis(4) load during boot.  Recent machines I
> tried to do that have panic'd during boot.

I have these lines in /boot/loader.conf and if_ndis and ndis(4) based 
driver load fine:
ndis_load="YES"
if_ndis_load="YES"
bcmwl5_sys_load="YES"

>
> 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=kern/165630
>
> which I would would be MFC'd already...

What you are suggesting is for the case when loading if_ndis causes 
panic during boot.
In my case it loads fine during boot, but it's not clear why 
'/etc/rc.d/netif' doesn't activate it.
network works fine once all commands are run manually.

Yuri