ath (AR9280) with nanoBSD (fwd)

[Adrian Chadd]

It was to remove the wifi interface from needing to be an ifnet interface,
complete with the locking and lifecycle management.

Now the net80211 physical interfaces don't have to pretend to be normal
network interfaces. Which is good in the long run as there's a whole bunch
of functionality to implement that doesn't map cleanly to ifnet.

A
On Jun 30, 2016 4:06 AM, "Felix Friedlander" <felixphew0 at gmail.com> wrote:

>
> > On 30 Jun 2016, at 21:02, Ian Smith <smithi at nimnet.asn.au> wrote:
> >
> > Sorry Felix, didn't notice you hadn't cc'd the list .. hoping you don't
> > mind if I do, might save someone else from responding .. cheers, Ian
>
> Nope, that’s fine, I meant to but I forget all the time.
>
> Alpine, mutt and other CLI mail clients manage to do it automatically, so I
> wonder how the GUI clients have missed out…
>
> - Felix
>
> >
> > ---------- Forwarded message ----------
> > Date: Thu, 30 Jun 2016 20:52:43 +1000 (EST)
> > From: Ian Smith <smithi at nimnet.asn.au>
> > To: Felix Friedlander <felixphew0 at gmail.com>
> > Subject: Re: ath (AR9280) with nanoBSD
> >
> > On Thu, 30 Jun 2016 20:28:54 +1000, Felix Friedlander wrote:
> >>> On 30 Jun 2016, at 19:12, Ian Smith <smithi at nimnet.asn.au> wrote:
> >>>
> >>> On Wed, 29 Jun 2016 11:51:40 -0700, Adrian Chadd wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> It's there, it just doesn't show up in ifconfig anymore.
> >>>>
> >>>> sysctl net.wlan.devices
> >>>>
> >>>> if you create the interface (ifconfig wlan0 create wlandev ath0) then
> >>>> it'll show up!
> >>>
> >>> Just curious .. why was it considered a good idea not to have ifconfig
> >>> show wireless interfaces?  Won't this make for ongoing such confusion?
> >>
> >> As I understand it, it was to avoid duplication. You have to create a
> >> wlanN interface to use a wireless device, so you would end up with
> >> both athN and wlanN. Now ath (and every other wireless driver) donÿÿt
> >> directly appear in ifconfig, you only have one interface.
> >
> > Ah, that sounds fair enough.  I expect there'll be something in 11.0
> > release notes about that.
> >
> >> I believe there is a sysctl to list the hardware devices if you want.
> >
> > I guess that might be net.wlan.devices :)
> >
> > Ok, sorry for the side-track ..
> >
> > cheers, Ian
>
>