Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "ax200"
-
## Building my own router
Damn it! I've got to read more before making decisions :) I already do that, but I need yet *MORE* reading.
So I bought a miniPC which I'm planning to turn into a router. I wanted to install AX200 (wifi6) card in it but it could only see the bluetooth part of it (using btusb kernel module).
What I did NOT know about wifi cards and mPCIe slots
M2 is only a form-factor. It defines what the connector looks like. Over that connector multiple different protocols could be used. m2 (NGFF) WIFI cards are usually using PCIe proto. And USB.
https://delock.com/infothek/M.2/...
My so-desired AX200 uses both PCIe and USB protocols: USB for BT and PCIe for the actual wifi.
https://ark.intel.com/content/www/.... The same spec applies to both: m2 and mPCIe card versions.
Now my mini PC has a mPCIe slot but the label on the board says "USB wifi". Which suggests that it only accepts the USB-related pins of mPCIe (as wiki says about mPCIe: "The host device supports both PCI Express and USB 2.0 connectivity, and each card may use either standard.").
So I guess that means I'm stuck with a useless mPCIe port :D shit..
Now my best bet is to wait for USB dongles supporting wifi6 and use usb AC adapters until then. Well... It's not an optimal outcome. But still IMO a better solution than an embedded router from the shelf!
(No, I'm not giving up and buying another used/new PC :) )
At last I can calm down and stop searching for magical pcie-to-usb adapters :) Phew... That's a relief!1 -
When your minipc finally arrives, you're all excited to finally get your hands on pfsense/bsd, and you find out bsd is still struggling with wifi5, not to mention wifi6 which you've bought to have high-end networking at home..
Bummer9 -
## building my own router
I hoped things would go more smoothly :)
Anyway, my new miniPC easily accepted CentOS 8 - no fuss here. And I've got to say - I love CentOS8 so far! Shell has amazing nifty tricks, UI (gnome3) is also snappy, video/audio/ethernet,.. everything works.
What I did NOT expect is hardware being off. Well okay, the price was low - it was obvious smth is not right. But still.. I decided to build my own router so that I could swap wifi card whenever I want. So that I could run my own network services in there. Turns out - the card swapping is not as easy as one might think.
I got the AX200 WiFi6 card for that very purpose. But once plugged in the OS can only see it's bluetooth module. Weird... What's even weirder is that even though the card is PCIe, the OS uses btusb module to talk to that device. What? USB?? emm.. What??
And there it is. After opening it up again I noticed that the mPCIe area is marked with a label: "USB WIFI / WWAN". USB? Does that mean this PCIe slot is wired into the USB bus? Not impossible I guess.
Googling for a "pcie wifi over usb" or smth like that brought me to one reddit (I think?) where someone wanted to build a DIY wifi mPCIe -> USB adapter and someone else adviced hime that (for some reason) at best he could only get bluetooth working (hey! just like me!). It's got to do smth with pcie channels and USB being too weak to handle all that load, or smth.. IDK, I'm not a HW guy.
Well that sucks then! I have a mPCIe slot that does not work as a PCIe. Shit! So I guess the best I could do is to plug back in the same wifi card that came with the device. It smells like 2003 - supports only g protocol. Fine, let's try that. Maybe I'll find a way to work around this mPCIe limitation later on (USB adapter or smth... except there are no USB WIFI6 dongles yet :( ). So I plug it back in and start turning it into a router. Disable NetworkManager, configure static NCs' settings, install dhcpd, hostapd, bind and others. Looks like all is done! Now it's time to start it all. systemctl start hostapd --> FAILED. wtf? journalctl says it could not initialize a driver. umm okay? Why? Forums say I should airodump-ng check and kill whatever's using that device. Fine. airodumo reveals avahi and wpa_suppl are still using it. kill, kill, GOTTA KILL 'EM ALL!! Starting hostapd again -- same shit... wtf?
iw list
My gawd... That shitty network card does not even support AP mode :( I mean.. My USB wifi dongle for 2€ supports 2x more modes, is faster, has better range and is easier to work with than this old tart!
Yeah. That was an interesting day. When enfironment engineers break my testing environments at work I'm glad I have where to spend my time now.
BTW any ideas how to bypass this mPCIe nonsense? Come on, there are USB GPUs out there.. Why can't they make a USB (or dual-USB if they really need to) mPCIe adapter?8