Known working Wireless cards
-
Hi all,
Since the HW lists are getting old I'd like to have users report Cards that Works.
Please list the following output from Shell command:
pciconf -lv
Please also try to explain in detail:
-
Brand/Model/Version/ and how you used it (Client/AP/mesh etc.)
-
pfSense Version/build
No questions in this thread!
-
-
pfSense 2.1 - i386 (Alix Board, custom kernel, MWL_DEBUG=NO).
Marvell 88W8363
Rev A5 hardware, v3.6.2.2 firmware (regioncode 16)2 AP (1 virtual for captive portal)
ifconfig output (some values hide):
mwl0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 2290
ether 00:-:-:-:-:-
inet6 fe80::21f:f3ff:fec3:730%mwl0_wlan0 prefixlen 64 scopeid 0x9
inet 192.168.244.1 netmask 0xffffff00 broadcast 192.168.244.255
nd6 options=1 <performnud>media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap>status: running
ssid – channel 6 (2437 MHz 11g ht/40+) bssid 00:--:--:--:--:--
regdomain DEBUG indoor authmode WPA2/802.11i privacy MIXED deftxkey 3
AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 16 scanvalid 60
protmode CTS -ampdu ampdulimit 64k ampdudensity 4 shortgi smps burst
-apbridge dtimperiod 1</hostap></performnud></up,broadcast,running,simplex,multicast>
-
See my Signature below for chipset I'm currently running.
Seems to run fine ….. I have had some stuck beacon problems in the past every now and than. I would be forced to do a reboot and would clear up ..... recently this has not been occurring which I find to be rather strange behavior .... knock on wood.
Wikidevi Link list all Atheros chipsets ever manufactured.
-
I'm running an atheros 9280 in AP on pfsense 2.1 that I picked up off of ebay:
ath0@pci0:3:0:0: class=0x028000 card=0x655211ad chip=0x002a168c rev=0x01 hdr=0x00
class = network
-
lsf, I believe you meant to say, "pciconf -lv" rather than "pciconfig -lv".
-
Good this is sticky, I have read the last 10 pages and it appears varying results some guys use wireless adaptors/cards and still get the random rebooting/pfsense config crashing and getting wiped issues, even with compatible adaptors/cards !
Some people over the last few pages suggested these as options:
TP-Link TL-WN7200ND 150Mbps High Power Wireless USB Adapter
Ralink RT3072 Adapter (seemed good compatible wise)Seems these maybe good options to go for but it appears some got them and still had similar issues some went for weeks without issues though. Obviously don't take my word for it on the above wireless adaptors since some suggested it was hit and miss for them also.
One guy posted Its better to get a wireless router and use that as an access point, I agree I think this is the best route and will give it a try perhaps.
-
Well, I could recommend several cards working well with pfSense 2.0.3. But since pfSense 2.1.x I am having a lot of trouble with wireless at all. I think I have narroved it down to 802.1x authentication which makes any of may WLAN cards stop working as soon as it is enabled. Under 2.0.3 I am having no problem with 802.1x authentication. I have summarized my latest experiences with pfSense 2.1.1-PRERELEASE under:
https://forum.pfsense.org/index.php/topic,72483.0.htmlMost interesting question for me is: Is anybody using successfully 802.1x authentication with pfSense 2.1.x? If so, please give me feedback, because I am close to openening a ticket for it.
Hope, my post is not off-topic as questions are not wanted :) And I do not mind, if the thread opener feels, my post should be better moved to a new topic.
Regards,
Peter
-
Well, the avove mentioned general WLAN issue under pfSense 2.1.x is solved now with the latest 2.1 snapshot and I can give some more detailed feedback on the actual topic of this thread.
This Atheros AR5213A based Wistron CM9 miniPCI card is working under 2.0.x and 2.1.x:
ath0: <atheros 5212="">mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0 ath0: [ITHREAD] ath0: AR5212 mac 5.9 RF5112 phy 4.3</atheros>And this Atheros 9280 based UBIQUITI SR71-E miniPCIe card is working under pfSense 2.0.x:
ath0: <atheros 9280="">mem 0xa3000000-0xa300ffff irq 17 at device 0.0 on pci7 ath0: [ITHREAD] ath0: AR9280 mac 128.2 RF5133 phy 13.0</atheros>I could not yet test it under pfSense 2.1.x but expect it working there as well.
Peter
-
I have just upgraded my Soekris net6501 machine to pfSense 2.1.1 and can confirm the Atheros 9280 based UBIQUITI SR71-E miniPCIe card is still working nice - of course in abg modes only.
Regards,
Peter
-
Right now, I'm running:
pfSense 2.1.2-RELEASE (i386)
built on Thu Apr 10 05:23:34 EDT 2014
FreeBSD 8.3-RELEASE-p15
I bought a used BearExtender Mini b/g/n 1,000 mW / 1 Watt, USB 2.4 Ghz WiFi adapter, branded for Apple/Mac.
I think I ran a command on my linux box, which showed it to have a Ralink chip(set).
Within pfSense, it was able to associate it with a "guest" ssid, within range, but that's probably password redirected/port capture/walled garden/etc.
- It can scan, as seen on webConfigurator/GUI page, Status: Wireless
../status_wireless.php-
I pressed the DHCP "Renew" button on webConfigurator/GUI page, Status: Interfaces:```
../status_interfaces.php
* This caused pfSense to crash, necessitating a reboot. * I've had one other, since then, which happened when there was no human activity.
Since it's a USB device, I didn't use command:
pciconf -lvBut ran:
$ ifconfig | grep -A4 -i wireless media: IEEE 802.11 Wireless Ethernet autoselect mode 11b status: associated run0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether 00:1e:97:xx:xx:xx inet6 xxxx::xxx:xxxx:xxxx:xxxx%run0_wlan0 prefixlen 64 scopeid 0xd -- media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (autoselect) status: no carrier ssid "-------------" channel 9 (2452 MHz 11b) regdomain FCC country US outdoor authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60</up,broadcast,running,simplex,multicast>I also ran:
$ ifconfig run0_wlan0 run0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether 00:1e:97:xx:xx:xx inet6 xxxx::xxx:xxxx:xxxx:xxxx%run0_wlan0 prefixlen 64 scopeid 0xd nd6 options=1 <performnud>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (autoselect) status: no carrier ssid "-------------" channel 9 (2452 MHz 11b) regdomain FCC country US outdoor authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60</performnud></up,broadcast,running,simplex,multicast>- I see "txpower" = "30", but for the interface config, it's set to 99. It's a 1,000 mW device. This is dictated by:```
/etc/regdomain.xml
-
I did NOT find a setting for, 802.11n, but only "b" or "g", on the screen to setup the interface, the section:
Common wireless configuration - Settings apply to all wireless networks on run0.
-
The section: General configuration -> Speed and duplex -> Advanced, drop down list menu, had some entries without numbers. Those with max speed numbers, listed 54 M/s, as the top.
The pfSense Docs page that came up in a search, make no mention of this:
https://doc.pfsense.org/index.php/Wireless_Interfaces
However, from that page, following the link: list of supported cards, shows that this is normal.
This is spelled out in Category:Wireless -> Is 802.11n wireless supported
I also ran:
$ usbconfig ugen4.2: <product 0x3070="" vendor="" 0x148f=""> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON</product>An internet search yielded:
USB: 148F:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
I'd much prefer a decent Atheros Chip.
:-| :-/ :-\
-
450 Mbit/s Original Atheros AR9380 AR5BXB112 Mini PCIe WLAN
-
DELL DW1525 works (PCI-Express 1x card), Atheros AR9280 chipset.
Depending where you live, you might need to change regdomain in EEPROM.
there is link in one of the Mac forums with a good tool: (downloading presumes registration in forum)
http://www.insanelymac.com/forum/topic/299732-atheros-9k-series-rom-modding-tools-and-recovery-kit/aet_rw512_AnV.zip - contains source code, x86/x64 executables of eeprom tool and some sample firmwares
atheros_eeprom_tool-WIN8.1.zip - contains only executables modified for compatibility with Windows 8.1warning: if you go and try to change regdomain it must be in form of two digits (for example 37 for EU) or you are going to brick the card.
Why would you need EEPROM tools? In order to unlock "N" for AP mode or modification of regdomain (unlock "g" channels 11-14 where you should have them but don't)
-
pciconf -lvc
ral0@pci0:0:17:0: class=0x028000 card=0x28601814 chip=0x06011814 rev=0x00 hdr=0x00
class = network
cap 01[40] = powerspec 3 supports D0 D3 current D0card: EMP 9701
size: half-length mini-PCI
chipset: RT2860+RT2820
driver: ralhttp://www.freebsd.org/cgi/man.cgi?query=ral
AP mode, WPA2 security
2.2-RC 32 bit on Soekris NET6501
Only b/g mode supported in the driver, so if you are looking for n speeds, I recommend Atheros.
-
Asus USB-N66 working as Access Point out of the box on pfSense 2.2-RELEASE (amd64). Only 802.11a/b/g though - 802.11n does not seem to be supported by pfSense or the driver:
filtered output from dmesg (if it helps anyone):
usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 ugen0.1: <0x1912> at usbus0 uhub1: <0x1912 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 run0: <1.0> on usbus0 run0: MAC/BBP RT3593 (rev 0x0402), RF RT3053 (MIMO 3T3R), address 08:xx:xx:xx:xx:xx wlan0: changing name to 'run0_wlan1' run0: firmware RT3071 ver. 0.33 loaded
-
Please also try to explain in detail:
Brand/Model/Version/ and how you used it (Client/AP/mesh etc.)
pfSense Version/buildMini PCIe card pulled from broken laptop, not sure of exact device beyond AR9285, HostAP mode. pfSense AMD64 VGA 2.2.1.
This isn't the fairest test in the world but here are the results of speed tests to www.speedtest.net:
Wired network - D/L 66Mbs U/L 12Mb/s - My ISP baseline.
Wireless network - D/L 25Mb/s U/L 12Mb/s
–After setting the minimum standard to 802.11n (was g).
Wireless network D/L 36Mb/s U/L 12Mb/s
Two configuration changes (min standard 802.11n requires WME tickbox to be checked) and my throughput has increased 40%. All results are the average of three tests each so it isn't a glitch. It may be a fraction of what you might expect but exceeds my personal requirements.
$ pciconf -lv ath0@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 class = network
-
Mikrotik RB14eu+Mikrotik R11e-5HnD (Atheros AR9580)
Apr 30 10:06:43 pfSense kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000
Apr 30 10:06:43 pfSense kernel: ath0: AR9580 mac 448.4 RF5110 phy 0.0
Apr 30 10:06:43 pfSense kernel: ath0: [HT] 2 RX streams; 2 TX streams
Apr 30 10:06:43 pfSense kernel: ath0: [HT] 1 stream STBC transmit enabled
Apr 30 10:06:43 pfSense kernel: ath0: [HT] 1 stream STBC receive enabled
Apr 30 10:06:43 pfSense kernel: ath0: [HT] enabling short-GI in 20MHz mode
Apr 30 10:06:43 pfSense kernel: ath0: [HT] enabling HT modes
Apr 30 10:06:43 pfSense kernel: ar9300_hw_attach: ar9300_eeprom_attach returned 0
Apr 30 10:06:43 pfSense kernel: Restoring Cal data from OTP
Apr 30 10:06:43 pfSense kernel: Restoring Cal data from Flash
Apr 30 10:06:43 pfSense kernel: Restoring Cal data from Flash
Apr 30 10:06:43 pfSense kernel: Restoring Cal data from EEPROM
Apr 30 10:06:43 pfSense kernel: Restoring Cal data from DRAM
Apr 30 10:06:43 pfSense kernel: ar9300_flash_map: unimplemented for now
Apr 30 10:06:43 pfSense kernel: ar9300_hw_attach: calling ar9300_eeprom_attach
Apr 30 10:06:43 pfSense kernel: ar9300_attach: calling ar9300_hw_attach
Apr 30 10:06:43 pfSense kernel: ath0: <atheros ar9580="">mem 0xfe700000-0xfe71ffff irq 29 at device 0.0 on pci4</atheros>Seems to work. Though getting some ath driver related "spam" on VGA monitor.
" short-GI in 20MHz mode", wish I could get 40Mhz mode work. Works with WPA+WPA2 as well.
Speeds:
-
DON'T DO IT!!!
I tried, again, a couple times…
I'm now on 2.2.2.
Just enabling the interface causes panic, and it sticks in a reboot loop, until you unplug this device!
I saw a message on the console, about needing to run fsck.
It borked dhcpd, until I reverted to an earlier config.
Squid daemon keeps dieing...
I keep getting timeouts, on common, familiar websites.
I may be heading for a fresh install...
I bought a used BearExtender Mini b/g/n 1,000 mW / 1 Watt, USB 2.4 Ghz WiFi adapter, branded for Apple/Mac.
I think I ran a command on my linux box, which showed it to have a Ralink chip(set).
- I pressed the DHCP "Renew" button on webConfigurator/GUI page, Status: Interfaces:
../status_interfaces.php-
-
This caused pfSense to crash, necessitating a reboot.
-
I've had one other
-
$ ifconfig | grep -A4 -i wireless media: IEEE 802.11 Wireless Ethernet autoselect mode 11b status: associated run0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether 00:1e:97:xx:xx:xx inet6 xxxx::xxx:xxxx:xxxx:xxxx%run0_wlan0 prefixlen 64 scopeid 0xd -- media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (autoselect) status: no carrier ssid "-------------" channel 9 (2452 MHz 11b) regdomain FCC country US outdoor authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60</up,broadcast,running,simplex,multicast>$ ifconfig run0_wlan0
run0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
ether 00:1e:97:xx:xx:xx
inet6 xxxx::xxx:xxxx:xxxx:xxxx%run0_wlan0 prefixlen 64 scopeid 0xd
nd6 options=1 <performnud>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (autoselect)
status: no carrier
ssid "-------------" channel 9 (2452 MHz 11b)
regdomain FCC country US outdoor authmode OPEN privacy OFF txpower 30
bmiss 7 scanvalid 60</performnud></up,broadcast,running,simplex,multicast>$ usbconfig ugen4.2: <product 0x3070="" vendor="" 0x148f=""> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON</product> ```
-
I have installed Pfsense 2.3.1 on an 6 year old desktop EMachine ET-311G
rl0@pci0:1:6:0: class=0x020000 card=0xe1021acb chip=0x813910ec rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL-8100/8101L/8139 PCI Fast Ethernet Adapter'
class = network
subclass = ethernet
ath0@pci0:3:0:0: class=0x028000 card=0x3112168c chip=0x0030168c rev=0x01 hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'AR93xx Wireless Network Adapter'
class = networki bought a TP-Link N900 Wireless PCI Express Card with the Atheros AR9380 Chipset and Its been working fine some disconnect issues but its rare i think i just set it up wrong but i am using it as an AP with WPA2 AES Encryption!
-
Hi!
Is there anybody out there using a wifi USB stick with pfsense 2.3.1-1 successfully as WAN interface? Tried a ratek and a realtek, both without success…
kind regards
chemlud
-
I can report mixed success with a couple of different cards. Still looking for the "it just works" solution.
-
AzureWave AW-NB037: Based on Atheros WB195 reference design per WikiDevi. This was the card supplied when I bought the router as a package from Logic Systems. Uses ath(4) driver. FreeBSD only supported 802.11b/g until release 10.0, when 802.11n added. Hardware does 2.4GHz b/g/n, 1x1 (i.e. no MIMO). Nominally supports Bluetooth but FreeBSD drivers don't. Would sometimes lock up and generate many interrupts, slowing down router service.
-
Samsung based on Atheros AR9462 and WB222: Just obtained this used via eBay. Hardware can do 2.4 or 5GHz, a/b/g/n, plus Bluetooth. Uses ath(4) driver. Despite driver source provided by Qualcomm Atheros, FreeBSD driver is a work in progress, judging by the repo. Major holes in driver as of FreeBSD 10.3, appears some will be fixed in 11.0. Works passably on 5GHz with pfSense 2.3.2, can't get my iDevices to connect on 2.4GHz. No Bluetooth support in FreeBSD, not that I would use it anyway.
In a related annoyance, the FreeBSD documentation claims that the ath(4) driver supports ALTQ, but I haven't seen any evidence of it with these cards.
-
-
hi, anybody can give an working wireless cards for access point ? (awus036h (RTL8187) not working for acess point :-X )
-
In present time, What is the best card (mini PCIe card) that supports WIFI N ?
I'm looking for replace (AzureWave AW-NU706H), card is WIFI N, but pfsense allow only A/B/G.
https://forum.pfsense.org/index.php?topic=136224.0
-
In present time, What is the best card (mini PCIe card) that supports WIFI N ?
I'm looking for replace (AzureWave AW-NU706H), card is WIFI N, but pfsense allow only A/B/G.
https://forum.pfsense.org/index.php?topic=136224.0Ditto. What's the best internal Mini PCIe board of choice for FreeBSD 11.1 / pfSense 2.40? PC Engines sells this one, so I assume it's at the top or close to it?
https://pcengines.ch/wle200nx.htm
-
Ditto. What's the best internal Mini PCIe board of choice for FreeBSD 11.1 / pfSense 2.40? PC Engines sells this one, so I assume it's at the top or close to it?
https://pcengines.ch/wle200nx.htmYes, this card works, under pfSense 2.3.4p1 even perfect. Under 2.4.0 I am having smaller issues: https://forum.pfsense.org/index.php?topic=138260.0
I will create a ticket for it soon.
-
I have been trying unsuccessfully for a while to get pfsense working on a laptop to function as a wifi access point
I had an affiliate of mine order a WLE200NX wireless card for me after we tried a dozen different atheros wireless adapters in a handful of old laptops without any success
This card was suggested to me by a sales rep with netgate - after reading the previous post confirming that it should work, I'm strongly leaning towards the conclusion that I'm doing something wrong because while it works with windows, when the same box is nuked and paved with pfsense, the card cant be detected.
The process I used was to swap in the wifi adapter, then fresh install pfsense 2.4.2 (latest version as of this writing) on the laptop in question. At the end of the installation the application will ask to assign interfaces, at this stage, the wireless adapter is not listed (only the ethernet adapter is listed) and the card considered not compatible.
I don't want to hijack this thread though, but at the same time I thought I should post my experience as it appears to be relevant here. I created my own thread where I'm hoping someone can point out what I'm doing wrong and what the actual process to drop a card into a laptop and install pfsense is… Its here in the wireless section...
-
The process I used was to swap in the wifi adapter, then fresh install pfsense 2.4.2 (latest version as of this writing) on the laptop in question. At the end of the installation the application will ask to assign interfaces, at this stage, the wireless adapter is not listed (only the ethernet adapter is listed) and the card considered not compatible.
https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Wireless
-
OMG THANK YOU!
Any explanation of the trouble this has caused me or the relief you've brought me would be an understatement.
;D
-
Looking through the forum this seems to be the best place to ask this for I haven't seen it discussed elsewhere.
Can someone recommend an 802.11AC MiniPCIE card for use with pfSense? I had already bought one using the FreeBSD hardware list as a guide on what is compatible. However, I was told here:
https://forum.pfsense.org/index.php?topic=141663.0
that, not all FreeBSD drivers are included in the pfSense kernel, even though we are told this on the main pfSense main page.
Thanks!
-
I've used the TP-LINK TL-WDN4800 for a few years. It works very well because it uses the ath9k driver, but unfortunately I haven't gotten good reliability from them. Both of mine died after about two years. Sorry I don't have pciconf for it, but I'm using an old dual radio router as an AP while I decide if I want to replace the WDN4800 or find something else.
-
none2@pci0:0:20:3: class=0x028000 card=0x00348086 chip=0xa3708086 rev=0x10 hdr=0x00
vendor = 'Intel Corporation'
device = 'Wireless-AC 9560 [Jefferson Peak]'
class = network
cap 01[c8] = powerspec 3 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[40] = PCI-Express 2 root endpoint max data 128(128) FLR RO NS
cap 11[80] = MSI-X supports 16 messages
Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
ecap 0000[100] = unknown 0
ecap 0018[14c] = LTR 1
ecap 000b[164] = Vendor 1 ID 16Not sure why it lists it as none, but it is the built in wifi card with the mobo and PFSense can not see it. Kinda sucks cause it was the only reason I bought this mobo, I could have gone much cheaper but I wanted one with built in wifi
-
It's listed as none because there are no drivers for that particular 802.11ac card for FreeBSD (yet, see below). Do yourself a big favour and stop trying to get internal Wifi NICs working on pfSense/FreeBSD, get an external AP like one of the Ubiquiti entry level models.
https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4&manpath=freebsd-release-ports
-
Interesting this thread is so old, but still new posts. Are there any updates to this for latest PFSense using FreeBSD 11? I just wasted a few dollars on an wifi usb/AC adapter that I could have sworn was in 11's compatibility list. @kpa The problem is, we need captive portal for a guest wifi. We don't care if it's an older/slower model. The wifi has to be a USB adapter as well (Netgate SG-1000) as usb is the only option. There are lots of inexpensive usb wifi adapters that should work according to compatibility list, but If someone has a known working one, please post. Thank you!
-
@sbrock99 .. i have just bought a mb with this same wifi as you (AC 9560), did you find a way to get it to work?
I am trying to find a way but having no luck.
-
@no_one I gave up, the ones people say work, don't. Probably because the SG-1000 is different CPU then your normal freebsd box. What I did instead is get a USB to Ethernet plug and an external router. Not optimal and I can't do this at 10 locations, so we're looking at other routers... The USB to Ethernet plug seems more supported and worked straight away.
-
I have this WiFi card, could be supported on pfsense?
07:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
I forgot to mention that it's from lspci command in centOS 8.
-
It should be supported by the wpi driver.
Note the hostap mode is a bit odd on that card/driver if you wanted to use it as an access point.
Steve
-
@stephenw10 So we can't reverse it. And i still have to use kvm or proxmox.
-
Reverse it? Not sure what you mean. You should start a new thread and detail what it is you're trying to do.
-
@stephenw10 I mean put my lan as wan and wifi as AP. I already test it that way, this WiFi can not work in AP mode.
-
It doesn't surprise me that cannot work as an AP given it only support some quasi hostap mode. Nothing we can do about that.
