@Ducdanh Nguyen it should work. https://developer.android.com/tools/adb

@Cancer Netplan is from Canonical, so I'd guess ubuntu would likely use a similar setup https://netplan.io/ https://netplan.readthedocs.io/en/stable/netplan-tutorial/#running-netplan-for-the-first-time https://docs.armbian.com/User-Guide_Networking/ and the renderers can be NetworkManager or Systemd-Networkd as described in their pages as well. The setup is less than intuitive, but that I'm more familiar with NetworkManager. What I did instead is that, for my netplan config /etc/netplan/10-dhcp-all-interfaces.yaml: network: version: 2 renderer: NetworkManager # Different than 'networkd' I only used a 'minimal' config as like above. That would make it use NetworkManager as the renderer. I think it is also necessary to install NetworkManager for some e.g. 'minimal IOT' images apt install NetworkManager Then that if you are running it with a keyboard, monitor with gnome graphical interface you can use a gui editor like nm-connection-editor network-manager-applet https://wiki.archlinux.org/title/NetworkManager to setup the network configs, the Gui is kind of 'guided' and tends to be 'easier' for beginners. if you don't have that I think there is nmtui - text based with (ncurses) menus nmcli - command line cli configs if you are using nmcli say operating from a text console, there are some tutorials you may find through a web (e.g. google) search https://www.cyberciti.biz/faq/redhat-network-interface-configuration/ https://www.tecmint.com/nmcli-configure-network-connection/ https://www.cyberciti.biz/faq/how-to-add-network-bridge-with-nmcli-networkmanager-on-linux/ https://dev.to/faaiq_amarullah/managing-networking-based-on-rhel-8-202e in general, while editing network interfaces, I take 'ample precautions' and operate over the serial debug console (using a usb-uart dongle), as you may get 'locked out' if you are in one of the network connections that you are editing. If you are using a full desktop say with a monitor and keyboard, that's ok as well. I think the 'iot minimal' images some of those use Systemd-Networkd as default, so some of the setup may still be in Systemd e.g. Systemd-resolved. That could affect your DNS resolver configs, what I did is I googled for configs about Systemd-resolved and maintained my primary and secondary (DNS) nameservers in /etc/systemd/resolved.conf I'm not too sure if that is after all necessary. NetworkManager is 'higher level' than configuration commands as like ip or ifconfig, in a sense that it 'manages' the interfaces. while ip and ipconfig are normally per-invocation command, NetworkManager stores its setup in /etc/NetworkManager. One should normally use the gui or nmcli / nmtui commands to configure them instead of editing the files directly. And remember to save the configs as permanent instead of temporary while using the gui, nmcli or nmtui. With that normally the configs will persist across reboots. This is probably more organised perhaps 'simplier' than say editing scripts say using the 'old' way say in /etc/interfaces. After you configured interfaces e.g. with nmcli, nmtui or the gui editors, normally to check status of the interfaces you could run commands like nmcli c show (show connections) nmdli d status (show devices) etc to show the state of interfaces configured by NetworkManager. the 'lower level' commands like ip (or ifconfig (apt install net-tools to get that) ip link (show link status) ip a (show addresses) can also be used to check on the status of the intefaces.

I don't like brainless matrix. Not using ifconfig however newer doesn't always mean better especially when it's not fool proof configured. Nevermind. When in new basic images we have 3 programs/processes instead of one for network and system after reboot doesn't come to back without checking configuration something is wrong. if one is new to new config must find what manages the network. Question is who are images for? Not for newbies for sure. Correct me if I'm wrong in any point: I can see in docs on main pages that netplan.io controls configuration. Really? Network manager does it however is masked and netplan is redirected to network manager config from what I've seen. When somebody doesn't know newer stuff must investigate/ask/look for solution or having at least admin knowledge in this matter. docs say that at first boot I should see: ``` Internet connection was not detected. Connect via wireless? [Y/n] y Multiple wireless adaptors detected. (...) ``` Never have seen such thing at all in armbian Docs should show defaults properly and if one needs more the rest in deeper details. However it doesn't look

@usual user The USB and Ethernet ports are exposed, but how would that work exactly? I don't know how to make the software boot from USB or Ethernet and even if I did I don't know what to boot into that can write an image file to the emmc chip. I can find no info on this on radxa or armbian sources.

@bushw ok this is what i saw in my setup running as an ap (I used netplan and NetworkManager - but I do not use its AP (wifi hotspot) features ) > sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ^ empty sudo nft list ruleset ^ empty my setup is documented here: https://gist.github.com/ag88/de02933ba65500376d1ff48e504b1bf3 I'm running and using hostapd for AP, for one thing hostapd produce logs for every client that connects to the wifi AP, that is far better than the 'built-in' 'easy' AP say with NetworkManager. Now I'd try to explain why you observe what you observe: --------- Network Manager could be using DNSmasq https://en.wikipedia.org/wiki/Dnsmasq https://thekelleys.org.uk/dnsmasq/doc.html when it setup the AP, it creates an NAT so that the wifi-subnet can access the upstream network https://tldp.org/HOWTO/html_single/Masquerading-Simple-HOWTO/ in addition,, DNSmasq also provides a dhcp server (to distribute ip addresses to the connecting wifi clients) and ipv6 router advertisement. that is what makes it 'simple'. don't like that? install and setup hostapd https://w1.fi/hostapd/ install and setup a dhcp server if you need it https://www.isc.org/dhcp/ install and setup radvd if you need ipv6 https://github.com/radvd-project/radvd those 3 above can normally be installed via apt next configure and setup the network interfaces and hostapd like what I did: key is (*unmanage* the WiFi interface and use hostapd to manage it, manual configure it) https://gist.github.com/ag88/de02933ba65500376d1ff48e504b1bf3 then you can choose to setup a network bridge or routing as you deemed fit. or even NAT - via ip tables or nftables https://wiki.nftables.org/wiki-nftables/index.php/Main_Page ^ if you do this, then that is what dnsmasq (probably called by NetworkManager) tries to do for you to make it 'easy' but if you configure everything yourself, using hostapd and the respective individual tools (dhcp server, radvd etc), no interference from Netplan, NetworkManager , dnsmasq, doesn't touch your iptables or nftables --- this mode: AP for wifi interface is a *feature* that you used in NetworkManager (dnsmasq) this is different from saying that Netplan and/or NetworkManager * *maliciously* change firewall configs for all possible combinations of network interfaces and configurations* don't like that AP feature / implementation in NetworkManager? you could probably take it up with RedHat https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/networking_guide/getting_started_with_networkmanager I'm not sure what other ways are there to configure the AP in NetworkManager so that it doesn't do NAT you would need to experiment if you are using the mode: AP feature in NetworkManager, there are likely various config options https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/proc_configuring-rhel-as-a-wpa2-or-wpa3-personal-access-point_configuring-and-managing-networking https://www.baeldung.com/linux/nmcli-wap-sharing-internet doing everything manually for WiFi AP using hostapd land individual tools, lets you control every single aspects of the network configs, I prefer this myself over the 'simple' approach e.g. that offered by NetworkManager, this include your firewall rules iptables, nftables etc, it is in part because the 'simple' AP offered by NetworkManager does so using NAT which is basically firewall rulesets i.e. iptables, nftables, if you don't want it to 'touch' that, then you would need to setup things manually and not use NetworkManager's AP mode.