Date: Fri, 2 May 2008 11:44:06 +1200 From: Andrew Thompson <thompsa@FreeBSD.org> To: Ben Kaduk <minimarmot@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: HEADSUP: 802.11 vap support merged Message-ID: <20080501234406.GB69163@citylink.fud.org.nz> In-Reply-To: <47d0403c0805011546k60ad7a84m5bd8bbf145519850@mail.gmail.com> References: <480D6667.4020509@errno.com> <47d0403c0804261757w5eb90be4k1f4f06521fe01bd@mail.gmail.com> <20080427040021.GC98671@citylink.fud.org.nz> <47d0403c0805011546k60ad7a84m5bd8bbf145519850@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 01, 2008 at 06:46:06PM -0400, Ben Kaduk wrote: > On 4/27/08, Andrew Thompson <thompsa@freebsd.org> wrote: > > On Sat, Apr 26, 2008 at 08:57:27PM -0400, Ben Kaduk wrote: > > > Hi Sam, > > > > > > ifconfig ndis0 up > > > gives me a panic (hand transcribed) > > > Fatal trap 12: page fault while in kernel mode > > > ndis_setstate_80211 > > > > > > I can see why this would happen, can you try this patch. > > > > Sorry for the delay; I just got to test the patch. > > It works, in that the machine no longer panics when I try to frob ndis0 > directly. I can still create a wlan0 on top of ndis0, and this appears to > send and receive traffic properly. Great, thanks for testing. > I can assign ndis0 an IP address and netmask with ifconfig, but > ifconfig ndis0 scan is ``unable to get scan results''. > (I also can't give ndis0 an ssid (SIOCS80211: Invalid argument), and > thus can't send traffic directly on ndis0.) So the vap parent is now just a bystander, you no longer frob it directly. You should be using the wlan0 device for scanning, assigning addresses, etc. cheers, Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080501234406.GB69163>