sgjava Posted September 7, 2018 Posted September 7, 2018 It seems the networking in Armbian 5.59 is messed up. It creates a eth0 adapter (disabled) and Wired network 1 adapter. You can delete these in nmtui, but they always return. I had the same issue with NanoPi Duo using mainline Stable. I can get it to work a bit using armbian-config, removing all interfaces and configuring IP, but it gets screwed up again. I cannot trust to run 5.59 headless because I have no way to get into the SBC without hooking video back up.
Igor Posted September 7, 2018 Posted September 7, 2018 C2 network is known to make troubles. I hope with each related patch that comes around that it will fix issues ... the last one claimed network troubles were fixed. I didn't notice them which doesn't mean anything. In general, it depends on which version do you use - Debian or Ubuntu, armbian-config is not very polished yet so it could make some troubles ... network (address) settings should be in users domain. We try to keep it simple and the same on all. If you have troubles, try to disable "advanced" NetworkManager networking and use ifupdown.
sgjava Posted September 8, 2018 Author Posted September 8, 2018 @Igor I fixed this by using armbian-config, clearing interfaces and using /etc/network/interfaces. Now I can reboot with a static address. With NanoPi Duo I had to remove netplan and use ifupdown for eth0, but the xradio wifi stuff seems to be missing from the kernel (modules, etc.). But in essence they exhibited the same issue with eth0. 1
stareintheair Posted October 7, 2018 Posted October 7, 2018 I am experiencing the similar network issues. My C2 didn't get an IPv4 address via DHCP only an IPv6 address. I have to use my router to figure out that IPv6 and connect to it. With the hints from Igor I got IPv4 also working: systemctl disable NetworkManager Add add the following to `/etc/network/interfaces`: auto eth0 iface eth0 inet dhcp iface eth0 inet6 auto privext 0 `privext 0` is optional. It disables the IPv6 privacy extension for server use. I had a lot of trouble with that too before I disabled NetworkManager. And of course: reboot I hope this will be fixed soon.
Recommended Posts