APU set up with Wi-Fi
-
What wifi card do you have?
The APU has only PCIe slots or USB for expansion options.Steve
-
This is my APU.
This is my Wi-Fi card.From what I read, the APU has 2 x miniPC express slots, but I can't find them to connect the Wi-Fi card into?
-
That is a half-sized card.
The slots on the board are designed for full-sized cards.
You need a full-sized card like this one: http://pcengines.ch/wle200nx.htm -
Ok, thanks.
I still don't see where the card will plug into the APU board though? -
here:
edit: better example:
https://forum.pfsense.org/index.php?topic=59555.msg405522#msg405522
Linked an image of my board with
left to right:
WLAN card
Dual Gbit card
The last card with the same formfactor is the SSD.
Physically and electrically the same connector, but a different protocol (SATA instead of PCIe). -
You can get an adapter to fit a half size card:
http://www.mini-box.com/Mini-PCI-E-Half-to-Full-Size-Extension-Card-Wireless-WIFI-PCI-Adapter-Bracket?sc=8&category=1363However more importantly I'm not sure that card will work with pfSense. It might be supported by the iwn driver in 2.2 (it's not mentioned explicitly in the driver).
Steve
-
Thank you.
The Wi-Fi card fits in the APU slots. (I connected to the left slot).
I then went to pfSense GUI > Interfaces > (assign) > Wireless > Add > Parent interface: no option to choose > Mode: Access Point > Description: Wi-Fi > Save > error: The following input errors were detected: The field 'Parent interface' is required.I'm guessing the Wi-Fi card is compatible with pfSense.
Not sure why pfSense hasn't found the card yet? -
I assume you're running 2.1.3? Probably there's no driver for it.
Try running 'pciconf -lv' at the command line and see if it appears there.
Steve
-
Yes, the version is 2.1.3-RELEASE (amd64)
built on Thu May 01 15:52:13 EDT 2014
FreeBSD 8.3-RELEASE-p16
You are on the latest version.I don't see the Wi-Fi card, but I might have missed it as I'm not quite sure what to look for.
I see the re0, re1 and re2 Ethernet ports, but they don't seem to show a cable connection on re0 and re1, but perhaps the command only shows the interfaces, not more details about connections.$ pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x15101022 chip=0x15101022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI pcib1@pci0:0:4:0: class=0x060400 card=0x12341022 chip=0x15121022 rev=0x00 hdr=0x01 class = bridge subclass = PCI-PCI pcib2@pci0:0:5:0: class=0x060400 card=0x12341022 chip=0x15131022 rev=0x00 hdr=0x01 class = bridge subclass = PCI-PCI pcib3@pci0:0:6:0: class=0x060400 card=0x12341022 chip=0x15141022 rev=0x00 hdr=0x01 class = bridge subclass = PCI-PCI atapci0@pci0:0:17:0: class=0x010601 card=0x43911002 chip=0x43911002 rev=0x40 hdr=0x00 class = mass storage subclass = SATA ohci0@pci0:0:18:0: class=0x0c0310 card=0x43971002 chip=0x43971002 rev=0x00 hdr=0x00 class = serial bus subclass = USB ehci0@pci0:0:18:2: class=0x0c0320 card=0x43961002 chip=0x43961002 rev=0x00 hdr=0x00 class = serial bus subclass = USB ohci1@pci0:0:19:0: class=0x0c0310 card=0x43971002 chip=0x43971002 rev=0x00 hdr=0x00 class = serial bus subclass = USB ehci1@pci0:0:19:2: class=0x0c0320 card=0x43961002 chip=0x43961002 rev=0x00 hdr=0x00 class = serial bus subclass = USB none0@pci0:0:20:0: class=0x0c0500 card=0x15101022 chip=0x43851002 rev=0x42 hdr=0x00 class = serial bus subclass = SMBus atapci1@pci0:0:20:1: class=0x01018a card=0x439c1002 chip=0x439c1002 rev=0x40 hdr=0x00 class = mass storage subclass = ATA isab0@pci0:0:20:3: class=0x060100 card=0x439d1002 chip=0x439d1002 rev=0x40 hdr=0x00 class = bridge subclass = PCI-ISA pcib4@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 rev=0x40 hdr=0x01 class = bridge subclass = PCI-PCI ohci2@pci0:0:20:5: class=0x0c0310 card=0x43991002 chip=0x43991002 rev=0x00 hdr=0x00 class = serial bus subclass = USB pcib5@pci0:0:21:0: class=0x060400 card=0x00001002 chip=0x43a01002 rev=0x00 hdr=0x01 class = bridge subclass = PCI-PCI ohci3@pci0:0:22:0: class=0x0c0310 card=0x43971002 chip=0x43971002 rev=0x00 hdr=0x00 class = serial bus subclass = USB ehci2@pci0:0:22:2: class=0x0c0320 card=0x43961002 chip=0x43961002 rev=0x00 hdr=0x00 class = serial bus subclass = USB hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x17001022 rev=0x43 hdr=0x00 class = bridge subclass = HOST-PCI hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x17011022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x17021022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x17031022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb5@pci0:0:24:4: class=0x060000 card=0x00000000 chip=0x17041022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb6@pci0:0:24:5: class=0x060000 card=0x00000000 chip=0x17181022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb7@pci0:0:24:6: class=0x060000 card=0x00000000 chip=0x17161022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb8@pci0:0:24:7: class=0x060000 card=0x00000000 chip=0x17191022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI re0@pci0:1:0:0: class=0x020000 card=0x012310ec chip=0x816810ec rev=0x06 hdr=0x00 class = network subclass = ethernet re1@pci0:2:0:0: class=0x020000 card=0x012310ec chip=0x816810ec rev=0x06 hdr=0x00 class = network subclass = ethernet re2@pci0:3:0:0: class=0x020000 card=0x012310ec chip=0x816810ec rev=0x06 hdr=0x00 class = network subclass = ethernet
-
Hmm, not there at all.
Is it in the slot correctly? Do you have the half to full adapter to make it sit level?
One of those slots is actually an mSATA slot not PCIe, are you maybe using that by mistake? Try a different slot.Steve
Edit:Typo
-
So, I plugged my Wi-Fi card into the middle APU slot which is PCIe 2.
Seems to have the same results.$ pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x15101022 chip=0x15101022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI pcib1@pci0:0:4:0: class=0x060400 card=0x12341022 chip=0x15121022 rev=0x00 hdr=0x01 class = bridge subclass = PCI-PCI pcib2@pci0:0:5:0: class=0x060400 card=0x12341022 chip=0x15131022 rev=0x00 hdr=0x01 class = bridge subclass = PCI-PCI pcib3@pci0:0:6:0: class=0x060400 card=0x12341022 chip=0x15141022 rev=0x00 hdr=0x01 class = bridge subclass = PCI-PCI atapci0@pci0:0:17:0: class=0x010601 card=0x43911002 chip=0x43911002 rev=0x40 hdr=0x00 class = mass storage subclass = SATA ohci0@pci0:0:18:0: class=0x0c0310 card=0x43971002 chip=0x43971002 rev=0x00 hdr=0x00 class = serial bus subclass = USB ehci0@pci0:0:18:2: class=0x0c0320 card=0x43961002 chip=0x43961002 rev=0x00 hdr=0x00 class = serial bus subclass = USB ohci1@pci0:0:19:0: class=0x0c0310 card=0x43971002 chip=0x43971002 rev=0x00 hdr=0x00 class = serial bus subclass = USB ehci1@pci0:0:19:2: class=0x0c0320 card=0x43961002 chip=0x43961002 rev=0x00 hdr=0x00 class = serial bus subclass = USB none0@pci0:0:20:0: class=0x0c0500 card=0x15101022 chip=0x43851002 rev=0x42 hdr=0x00 class = serial bus subclass = SMBus atapci1@pci0:0:20:1: class=0x01018a card=0x439c1002 chip=0x439c1002 rev=0x40 hdr=0x00 class = mass storage subclass = ATA isab0@pci0:0:20:3: class=0x060100 card=0x439d1002 chip=0x439d1002 rev=0x40 hdr=0x00 class = bridge subclass = PCI-ISA pcib4@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 rev=0x40 hdr=0x01 class = bridge subclass = PCI-PCI ohci2@pci0:0:20:5: class=0x0c0310 card=0x43991002 chip=0x43991002 rev=0x00 hdr=0x00 class = serial bus subclass = USB pcib5@pci0:0:21:0: class=0x060400 card=0x00001002 chip=0x43a01002 rev=0x00 hdr=0x01 class = bridge subclass = PCI-PCI ohci3@pci0:0:22:0: class=0x0c0310 card=0x43971002 chip=0x43971002 rev=0x00 hdr=0x00 class = serial bus subclass = USB ehci2@pci0:0:22:2: class=0x0c0320 card=0x43961002 chip=0x43961002 rev=0x00 hdr=0x00 class = serial bus subclass = USB hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x17001022 rev=0x43 hdr=0x00 class = bridge subclass = HOST-PCI hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x17011022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x17021022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x17031022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb5@pci0:0:24:4: class=0x060000 card=0x00000000 chip=0x17041022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb6@pci0:0:24:5: class=0x060000 card=0x00000000 chip=0x17181022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb7@pci0:0:24:6: class=0x060000 card=0x00000000 chip=0x17161022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI hostb8@pci0:0:24:7: class=0x060000 card=0x00000000 chip=0x17191022 rev=0x00 hdr=0x00 class = bridge subclass = HOST-PCI re0@pci0:1:0:0: class=0x020000 card=0x012310ec chip=0x816810ec rev=0x06 hdr=0x00 class = network subclass = ethernet re1@pci0:2:0:0: class=0x020000 card=0x012310ec chip=0x816810ec rev=0x06 hdr=0x00 class = network subclass = ethernet re2@pci0:3:0:0: class=0x020000 card=0x012310ec chip=0x816810ec rev=0x06 hdr=0x00 class = network subclass = ethernet none1@pci0:4:0:0: class=0x028000 card=0x40608086 chip=0x088e8086 rev=0x24 hdr=0x00 class = network
Also, the card doesn't sit flat. The card sits on an angle sticking up about 15 degrees.
I think the Wi-Fi card is the correct model as I bought the same model as per what's being sold here.
I'm not sure if the half size card will help? From what I understand, the half size card lets me screw down the Wi-Fi card to the APU. However the APU has no screw holes with the half size card or with the Wi-Fi card.
-
PCIe cards need to be screwed down to make proper contact with the slot. Because the APU doesn't have mountings for half cards you need the extension to make it fit the full size mountings.
However your card is now connected, you can see it listed as none1 in your pciconf output. It shows as none because there is no driver attached to it. There's not going to be a driver until 2.2 at the earliest and probably not then either (to make this work currently in FreeBSD you'd need to patch the driver yourself). You would be much better off with a different card.Steve
-
Oh, okay.
Would you or anyone know of a Wi-Fi card then that would work now?The other interesting thing is that the Wi-Fi pigtails I bought fits in one of the pfSense port holes, but not in the 2nd one.
-
The Atheros AR9280 based Ubiquiti AR71-e is known to work. So I would expect this to work:
http://www.ebay.com.au/itm/Atheros-AR5009-AR9280-AR5BH92-pci-E-card-300Mb-Dual-Band-2-4-5-0GHz-A03-/291006772296?pt=AU_Components&hash=item43c15af448
No promises though. ;)
I believe there were some other cards mentioned specifically in the APU thread.
Edit: Here for example:
https://forum.pfsense.org/index.php?topic=59555.msg402212#msg402212Steve
-
Thanks for the suggestion.
I ordered that link.
Still not sure how the screw holes will hold down the Wi-Fi card, as the APU has no screw holes for the mini or this link to the full size card.
The mini ones right now sit at a 15 degree angle, so as long as the full size Wi-Fi card works without the screws, should be ok. -
Ah, Ok now I look at a larger photo I see it has a pair of plastic pegs with metal clips instead of screws. Better in many ways.
Steve
-
Wow, you have good eyes :-)
Yes, not that you suggested that, I can see the plastic pegs/clips on my APU and know what they're for.
Ok, I'll wait for the new Wi-Fi card to arrive.
Can't wait to ditch my old cheap Wi-Fi router.Then just a nice big switch board to handle the network as I will lose the 4 ports on the old Wi-Fi router.
My current little 8 port switch can be removed too for one nice big switch.
Any good switches friendly to pfSense? -
Not much difference between switches with regards to pfSense. You could get one that supports VLANs to allow for any future network segregation you might want. If you're getting a large switch it will probably be managed and have that anyway.
Steve
-
Ok, the 2nd Wi-Fi card arrived.
I stuck it into the ALIX MOBO PCIe > logged into pfSense > Interfaces > but no OPTn to select?
How do I configure the Wi-Fi card?
I'm following this pfSense guide. -
All new interfaces have to be first assigned, either from the console menu or from the webgui interfaces menu. PfSense can't read your mind so by default it does nothing with new interfaces.