The framework exists so NICs that allow multiple virtual interfaces can. The iwn driver currently doesn't support this - it only supports one.
I'm not sure about why wpa_supplicant is chewing so much CPU time and why it isn't shut down cleanly. You can use service to shut down a single interface - I don't recall why. Try service netif stop wlan0 ? -a On 25 November 2014 at 13:31, Bastian <bastian-bsd...@t6l.de> wrote: > On 24Nov14 08:27 -0800, Adrian Chadd wrote: >> You need to create wlan0 first before you use it. >> >> # ifconfig wlan0 create wlandev iwn0 >> # ifconfig wlan0 up >> # ifconfig wlan0 list scan (bringing it 'up' will start scanning) >> > > Many thanks. I skiped that one while reading the manual. But now it > works well. > > May I assume, that you can create multiple wlan\d devices on one and the > sane iwn0 kernel device? > > > Now, I have wpa_supplicant working, in a way that it is automatically > searching for an available wifi network. This is triggered in the > /etc/rc.conf file during boot. > > I may have some follow-up questions: > > Q: service netif stop, shuts everything down, but the wpa_supplicant > process withstands from going down and starts to loop 100% cpu cyles > :/ > > Q: How can I just shutdown a single network interface? Keeping others > up and with the adjustment of the default routing. > > > Many thanks in advance, > > -- > Bastian _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
