> Another reason not to use it! Perfectly valid reason! I in fact am buying Orange Pi SBCs this days > I used it as a hotspot. Armbian has some weird obsolete

> Another reason not to use it! Perfectly valid reason! I in fact am buying Orange Pi SBCs this days > I used it as a hotspot. Armbian has some weird obsolete NetworkManager, that does not work with WPA2. OpenWRD does not support other functions I need. I don't follow that. Armbian has the same package versions as Debian. I just checked on an Armbian Bullseye I have in an Armv7 board and it has support for WPA2 Personal, WPA2 Enterprise, and WPA3. If you want to keep a regular Linux distribution probably your best bet is using something like 'hostapd' > And I did not use buildin networking managment, because it keept switching network interface names (multiple WIFI and LAN cards over USB). I can bind NetworkManager config to MAC and skip interface names completely. You can set those names static easily with systemd. Create a file for every nic like '/etc/systemd/network/10-eth10.link' and fill it like: [Match] MACAddress=75:1a:d3:80:85:59 [Link] Name=eth10 And then update your initramfs: update-initramfs -u And ready! :) > It is the most basic task for Linux computer... Well, it depends for whom. Also, you need adequate software and hardware. About wireless, the chipset in an RPi4 is designed for clients, not APs, and its capabilities on having multiple clients are quite limited: https://github.com/raspberrypi/linux/issues/3010 https://github.com/raspberrypi/linux/issues/3010 Routers like the Omnia Turris, Mikrotik, PC Engines... use specific mini PCIe cards that can be as expensive as a full Raspberry Pi 4, just for the wireless. https://www.discomp.eu/wireless-minipci-cards_c14501412.html https://www.discomp.eu/wireless-minipci-cards_c14501412.html