DietPi LAN problems at startup

General Discussion
1

System information:

root@DietPi:~# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=10
G_DIETPI_VERSION_SUB=2
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
root@DietPi:~#

root@DietPi:~# echo $G_DISTRO_NAME $G_RASPBIAN
trixie
root@DietPi:~#

root@DietPi:~# uname -a
Linux DietPi 6.12.74+deb13+1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.74-2 (2026-03-08) x86_64 GNU/Linux
root@DietPi:~#

root@DietPi:~# dpkg --print-architecture
amd64
root@DietPi:~#

root@DietPi:~# echo $G_HW_MODEL_NAME
Native PC (x86_64)
root@DietPi:~#

Since a couple of weeks I have LAN problems when starting DietPi in the morning.

The first time I start up (power on) there is no connection to the DietPi server (no access from Powershell and no Ping). If I than turn off (power off) and than turn on (power on) agian than I do get connection to DietPi.

Ethernet lights are blinking all the time. Have changes LAN-cable, port and Switch - did not fix the problem.

When it is running I do get this information:

root@DietPi:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 48:21:0b:60:d7:7f brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.22/24 brd 192.168.178.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fd11:968c:ed9c:0:4a21:bff:fe60:d77f/64 scope global dynamic mngtmpaddr proto kernel_ra
       valid_lft 7099sec preferred_lft 3499sec
    inet6 2003:e1:9714:b600:4a21:bff:fe60:d77f/64 scope global dynamic mngtmpaddr proto kernel_ra
       valid_lft 7099sec preferred_lft 1107sec
    inet6 fe80::4a21:bff:fe60:d77f/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c8:5e:a9:7b:a3:95 brd ff:ff:ff:ff:ff:ff
root@DietPi:~#


root@DietPi:~# dmesg | grep -i eth
[    1.427851] Intel(R) 2.5G Ethernet Linux Driver
[    1.517834] igc 0000:56:00.0 eth0: MAC: 48:21:0b:60:d7:7f
[    3.206850] Bluetooth: hci0: DSM reset method type: 0x00
[    7.401636] igc 0000:56:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
root@DietPi:~#


root@DietPi:~# journalctl -u networking.service
Apr 03 09:38:35 DietPi systemd[1]: Starting networking.service - Raise network interfaces...
Apr 03 09:38:35 DietPi systemd[1]: Finished networking.service - Raise network interfaces.
root@DietPi:~#



root@DietPi:~# journalctl -u ifup@eth0
Apr 03 09:38:35 DietPi systemd[1]: Starting ifup@eth0.service - ifup for eth0...
Apr 03 09:38:35 DietPi ifup[931]: udhcpc: started, v1.37.0
Apr 03 09:38:35 DietPi ifup[931]: udhcpc: broadcasting discover
Apr 03 09:38:38 DietPi ifup[931]: udhcpc: broadcasting discover
Apr 03 09:38:41 DietPi ifup[931]: udhcpc: broadcasting discover
Apr 03 09:38:41 DietPi ifup[931]: udhcpc: broadcasting select for 192.168.178.22, server 192.168.178.1
Apr 03 09:38:41 DietPi ifup[931]: udhcpc: lease of 192.168.178.22 obtained from 192.168.178.1, lease time 864000
Apr 03 09:38:41 DietPi systemd[1]: Finished ifup@eth0.service - ifup for eth0.
root@DietPi:~#

There are two other Windows PC - but there is no problem with them

Torben

2

When running

apt-get update
apt-get install ifupdown iproute2 isc-dhcp-client

I do get this information:

root@DietPi:~# apt-get update
apt-get install ifupdown iproute2 isc-dhcp-client
Hit:1 https://deb.debian.org/debian trixie InRelease
Get:2 https://deb.debian.org/debian trixie-updates InRelease [47.3 kB]
Get:3 https://deb.debian.org/debian-security trixie-security InRelease [43.4 kB]
Get:4 https://deb.debian.org/debian trixie-backports InRelease [54.0 kB]
Get:5 https://deb.debian.org/debian-security trixie-security/main amd64 Packages [119 kB]
Hit:6 https://dietpi.com/apt trixie InRelease
Get:7 https://deb.debian.org/debian trixie-backports/main amd64 Packages.diff/Index [63.3 kB]
Get:8 https://deb.debian.org/debian trixie-backports/main amd64 Packages T-2026-04-05-1400.15-F-2026-04-05-0200.13.pdiff [1253 B]
Get:8 https://deb.debian.org/debian trixie-backports/main amd64 Packages T-2026-04-05-1400.15-F-2026-04-05-0200.13.pdiff [1253 B]
Fetched 328 kB in 1s (345 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ifupdown is already the newest version (0.8.44+deb13u1).
iproute2 is already the newest version (6.15.0-1).
iproute2 set to manually installed.
Suggested packages:
  resolvconf avahi-autoipd isc-dhcp-client-ddns
Recommended packages:
  isc-dhcp-common
The following NEW packages will be installed:
  isc-dhcp-client
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1099 kB of archives.
After this operation, 2953 kB of additional disk space will be used.
Do you want to continue? [Y/n]
3

should be known. Try this one Network | DHCP fails after too short timeout · Issue #8039 · MichaIng/DietPi · GitHub

4

Thanks. Do you mean this?

sudo systemctl restart ifup@eth0 # it will succeed now, only fails on boot
sudo apt install dhcpcd-base
sudo apt autopurge udhcpc

Or will it be fixed in an upcomming update?

Torben

5

I have already updated to DietPi v10.2.3

Is it than this:

sudo apt install isc-dhcp-client
sudo apt autopurge dhcpcd-base udhcpc

Torben

6

This one

sudo apt install dhcpcd-base
sudo apt autopurge udhcpc
7

THX - it seems that the problem has been fixed.

Torben

8

Everything works just fine agian.

If I upgrade to NUC16 later this year what need to be done? Or has it been fixed in the lastest version? Or do I have to install dhcpcd-base again on the new NUC?

THX

Torben

9

the package udhcpc is not installed since we detected the challange. Nothing you need to take care off anymore.

10

THANKS :slight_smile: