the TL;DR is - we do support 11n, it's just done in net80211. So no,
you don't need to tell hostapd anything special about it for now.
On 28 May 2017 at 23:11, Pietro Sammarco via freebsd-wireless
> Hello folks. I recently bought a APU2C4 for the solely purpose to have it
> as a all in one FreeBSD router, firewall, HOSTAPD.
> It has got two mini PCIe Compex WLE200NX, which uses the Atheros AR9280
> ath0: <Atheros 9280> mem 0xfe400000-0xfe40ffff at device 0.0 on pci1
> ath0: [HT] enabling HT modes
> ath0: [HT] 1 stream STBC receive enabled
> ath0: [HT] 1 stream STBC transmit enabled
> ath0: [HT] 2 RX streams; 2 TX streams
> ath0: AR9280 mac 128.2 RF5133 phy 13.0
> ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0
> However though, I am running into a sort of nightmare with getting 802.11n
> to work with hostapd.
> Line 6: unknown configuration item 'ieee80211n'
> I could be totally wrong, but from what I understood IEEE80211N is disabled
> both from the hostapd binary included with system base(I am on FreeBSD
> 11-relese p9), as well as from the one in ports/pkg.
> Does this mean that I won't be getting no 802.11n love?
> If so, is there any reason of why 802.11n has been disabled from hostapd?
> If this turns out to be true, I honestly don't know whether is worth to
> venture compiling hostapd from source or rather going with pfsense, since
> they got it patched some 3 years ago.
> I appreciate your help.
> firstname.lastname@example.org mailing list
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"