HEADSUP: 802.11 vap support merged

[Ben Kaduk]

On 4/27/08, Andrew Thompson <thompsa at freebsd.org> wrote:
> On Sat, Apr 26, 2008 at 08:57:27PM -0400, Ben Kaduk wrote:
>  > Hi Sam,
>  >
>  > On 4/22/08, Sam Leffler <sam at errno.com> wrote:
>  > > From UPDATING:
>  > >
>  > >  20080420:
>  > >        The 802.11 wireless support was redone to enable multi-bss
>  > >        operation on devices that are capable.  The underlying device
>  > >        is no longer used directly but instead wlanX devices are
>  > >        cloned with ifconfig.  This requires changes to rc.conf files.
>  > >
>  >
>  > Again, sorry for jumping in late.
>  >
>  > Do I interpret this correctly as that it is unsupported, now, to
>  > do something like `ifconfig ndis0 up`?
>  > In my present configuration, I can do:
>  > ifconfig wlan0 create wlandev ndis0
>  > ifconfig ndis0 up
>  > ...
>  > and get a useable connection, but:
>  > 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.

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.)

I also got some error messages when I had given ndis0 my static IP,
added wlan0 on top of it, and then tried to send traffic.  My understanding
is that this is not a supported operation, though, so I won't worry about it.

Let me know if you want more information/testing.

Thanks,

Ben Kaduk