-
-
Notifications
You must be signed in to change notification settings - Fork 537
Description
Creating a bug report/issue
- I have searched the existing open and closed issues
Required Information
-
DietPi version |
cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=13
G_DIETPI_VERSION_RC=2
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
G_LIVE_PATCH_STATUS[0]='not applicable'
G_LIVE_PATCH_STATUS[1]='not applied'
G_LIVE_PATCH_STATUS[2]='not applied' -
Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN -
bookworm
-
Kernel version |
uname -a -
6.12.25-current-rockchip64 #1 SMP PREEMPT Fri Apr 25 08:48:08 UTC 2025 aarch64 GNU/Linux -
SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3) -
NanoPi R5S/R5C (aarch64)
-
Power supply used | (EG: 5V 1A RAVpower)
-
5V4A
-
SD card used | (EG: SanDisk ultra)
emmc
Additional Information (if applicable)
- Software title | (EG: Nextcloud)
- Was the software title installed freshly or updated/migrated?
- Can this issue be replicated on a fresh installation of DietPi?
- Bug report ID |
echo $G_HW_UUID
Steps to reproduce
After the latest update after a reboot, my network port has switched form the LAN port to the WAN port. I am not sure if this happened because of the update or just a coincidence as I haven't rebooted this device for a while. However, I had my ethernet cable plugged into the LAN port and set to eth0 . After reboot, I had to switch the cable to the WAN port for it to get access to the network. The interesting part is that it's still eth0.
I do have a custom file for a static MAC address because these devices don't have an assigned MAC and it randomizes with every reboot. the MAC address didn't change although the cable is not plugged into the WAN port.
Seems that eth0 and eth1 were switched around and the WAN was assigned priority. (On a side note, I am not sure if in the past I had forced eth0 to be the LAN port)
How do I switch that back. I would like to continue to use the LAN port for my eth0.
Expected behaviour
LAN should maintain eth0
Actual behaviour
WAN port is taking over eth0
Extra details
:~# lspci
0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
0000:01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
0002:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
lshw -C network
*-network DISABLED
description: Wireless interface
product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 00
serial: 48:8f:4c:d4:76:14
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rtw_8822ce driverversion=6.12.25-current-rockchip64 firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11
resources: irq:88 ioport:1000(size=256) memory:f4200000-f420ffff
*-network
description: Ethernet interface
product: RTL8125 2.5GbE Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0002:01:00.0
logical name: eth0
version: 05
serial: 00:70:3d:f0:e4:0e
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.12.25-current-rockchip64 duplex=full firmware=rtl8125b-2_0.0.2 07/13/20 ip=192.168.0.133 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:79 ioport:200000(size=256) memory:f0200000-f020ffff memory:f0210000-f0213fff
echo /sys/class/net/*
/sys/class/net/eth0
/sys/class/net/lo
/sys/class/net/wlan0