Hi Everyone,
Doe diet pi support dual nics? I loaded up the hyper-v bullseye image and added to nics to it. Under networking, I can only do dhcp or static for one nic. How do i set options for the other nic?
Thanks
I think by default only eth0 and wlan0 are shown in the network section of dietpi-config, but you can just config your interfaces in /etc/network/interfaces.
Better to create an one manual configuration at /etc/network/interfaces.d to avoid other tools overwriting default configuration file 
What is the point of dietpi-config networking? If you have 2 nics, of whatever kind, they should be useable, configurable, simultaneously ootb. Espeically when they are both onboard. I think the network config of dietpi needs serioius work as the current implementation is severely limiiting to “dummy” configuration. One useable nic at a time on Zeros, at least, for sure. Haven’t had as many issues on other sbc with nic & wifi onboard. But forget trying to use DP to config 2 nics on zeros of any kind without just manually routing and hard coding all your ip info and never use dp config network again.
I keep coming back to this topic when I invariably Google how to use multiple interfaces with DietPi so I agree, as it stands the networking is a bit dated. Many SBCs have multiple interfaces and in my case I use DietPi as a VM for running services on but I keep having to “upgrade” to a full Ubuntu server install when I find that DietPi is a bit too minimal for the job at hand. This latest issue is that I’m running Technitium and need to add some “dummy” interfaces to allow multiple DHCP scopes but when I run dietpi-config it tries to use eth1 which is the additional interface which has no route/gateway so the update fails the first step, the network check. Seems I can’t set this anywhere despite eth0 being in /etc/network.interfaces and there being a separate file at /etc/network/interfaces.d/eth1. Wouldn’t be so bad if at least the dietpi-config network section had a “primary/default interface” option at the very least even if you can’t configure all interfaces from there.
Yes correct dietpi-config is able to manage eth0 only. However this is just the limitation if our script and we know about this. DietPi is a very small project, mainly maintained by a single developer. You are still able to manage the interface manually, similar to how you would do on every other Debian system having CLI only.