Date: Sun, 9 Aug 2015 23:09:01 +0300 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Gavin Atkinson <gavin@FreeBSD.org> Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: [head up!] WiFi drivers changes Message-ID: <20150809200901.GC889@glebius.int.ru> In-Reply-To: <alpine.BSF.2.20.1508092028370.21405@ury.york.ac.uk> References: <20150806151355.GL889@FreeBSD.org> <alpine.BSF.2.20.1508092028370.21405@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 09, 2015 at 08:32:15PM +0100, Gavin Atkinson wrote: G> On Thu, 6 Aug 2015, Gleb Smirnoff wrote: G> > As part of the "opaque ifnet project" [1], all 802.11 (WiFi) drivers G> > undergo change of not being an interface anymore. Historically in FreeBSD G> > 802.11 stack, 802.11 devices called if_attach() and created an interface. G> > Later this was generalized and real functioning interface is created by G> > net80211 stack. However, remnant of parent interface remained. If you G> > are running Intel Centrino wireless, then you got iwn0 interface and G> > wlan0 interface. However, the former doesn't do anything. You can't G> > assign addresses to it or modify any of it parameters. Or you can G> > modify them, but that affects nothing. G> G> You could, however, change the Ethernet address of the underlying G> interface before creating the wlanX interfaces, which woud then be used by G> the child interfaces. This has traditionally been the only way you could G> change the Ethernet interface of a wifi device - changing it after G> creating the wlanX interface does not work. G> G> How will this be done in the new world? In new world you can change it on wlanX. I've tested on iwn(4), it worked for me, although association went not so quickly as before. -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150809200901.GC889>