I just installed DiePi 8.11 on an NanoPi R1 via ethernet.
Because the R1 has a WAN and a LAN Port, I had to fiddle around to get a working network port.
Sadly the default install uses only the slow eth0 (WAN) port. Eth1 stays unused.
I did not find any DietPi documentation how to setup network outside of dietpi-config. But in Debian docs I found that I had to edit /etc/network/interfaces.
After rebooting the system eth1 is up and running. But every time the system reboots, or just after a reconnect the mac address is changed.
Thats ugly, because my router detects unknown mac addresses. And sends me tons of info mails.
The changing mac adresses prevents me to set the mac as “static” in the dhcp server (dnsmasq) on the router.
Since the mac on eth0 did not change, but on eth1 does: What is the DiePi way to get a non changeing mac ?
And …
Should I remove eth0 from /etc/network/interfaces ?
At the moment I only need one eth interface at the R1, since I’m trying to setup a octoprint server.
But that may change in future, and I like to understand how the system is working …
For network hardware I prefer using OpenWrt.
I’m running a NanoPi R2S as main router to my external IPv6 fiber line. Some Archer C7 as dump AP’s, some GS108 switches, and a Freifunk Offloader running on Proxmox. Combined with some VLAN’s, Wireguard, adguard, …
My question in the first post was how the problem is handled under DietPi !!
This question is ultimately completely independent of any SBC. I think it is strategically unwise that the answer is now reduced to a NanoPi. Ultimately, all SBCs that have multiple ethernet interfaces are actually affected.
It only makes sense to first find a solution for a dedicated device if there is no general strategy under DietPi on how to deal with it.
And making adjustments in /etc/network/interfaces.d/… is a way that is completely unusual in other non-Debian-based distributions.
For example, Arch Linux based distributions do not even have a /etc/network directory…
You answered yourself. Using /etc/network/interfaces is quite standard on Debian based system where ifupdown is manging network connecting’s. Comparing it with a non-Debian system doesn’t make sense.