Running a freshly installed and updated OS Lite (64). I have not done anything with it, except for installing two Argon 40 scripts so that its Argon One case & fan works.
When an ethernet cable is plugged in through a 2.5 ghz usb-ethernet adapter through one of the USB 3.0 ports, RPI5 connects to both wireless and wired lan, and seems to get two IP addresses. While I am a total noob, I read that this should not be happening: rasp pi should automatically prefer a wired lan connection?
I first checked my router to see that RPI was connected to through wireless and wired. Later I ran "nmcli device" and "ip route:"
nmcli device
DEVICE TYPE STATE CONNECTION
eth1 ethernet connected Wired connection 2
wlan0 wifi connected preconfigured
lo loopback connected (externally) lo
p2p-dev-wlan0 wifi-p2p disconnected --
eth0 ethernet unavailable --
ip route
default via 192.168.178.1 dev eth1 proto dhcp src 192.168.178.60 metric 100
default via 192.168.178.1 dev wlan0 proto dhcp src 192.168.178.59 metric 600
192.168.178.0/24 dev eth1 proto kernel scope link src 192.168.178.60 metric 100
192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.59 metric 600
It does say wlan0 is disconnected, but that does not seem to stop it from having two IP addresses and establishing two connections to the router? I hope to have this running 24/7 and having two connection presumably consumes extra power without any real benefits. So I would much rather get it only connect to wired lan, if there is a wired lan connection present. The best solution I could find online is installing and using the ifplugd daemon.
Is there a simpler solution to the problem?
When an ethernet cable is plugged in through a 2.5 ghz usb-ethernet adapter through one of the USB 3.0 ports, RPI5 connects to both wireless and wired lan, and seems to get two IP addresses. While I am a total noob, I read that this should not be happening: rasp pi should automatically prefer a wired lan connection?
I first checked my router to see that RPI was connected to through wireless and wired. Later I ran "nmcli device" and "ip route:"
nmcli device
DEVICE TYPE STATE CONNECTION
eth1 ethernet connected Wired connection 2
wlan0 wifi connected preconfigured
lo loopback connected (externally) lo
p2p-dev-wlan0 wifi-p2p disconnected --
eth0 ethernet unavailable --
ip route
default via 192.168.178.1 dev eth1 proto dhcp src 192.168.178.60 metric 100
default via 192.168.178.1 dev wlan0 proto dhcp src 192.168.178.59 metric 600
192.168.178.0/24 dev eth1 proto kernel scope link src 192.168.178.60 metric 100
192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.59 metric 600
It does say wlan0 is disconnected, but that does not seem to stop it from having two IP addresses and establishing two connections to the router? I hope to have this running 24/7 and having two connection presumably consumes extra power without any real benefits. So I would much rather get it only connect to wired lan, if there is a wired lan connection present. The best solution I could find online is installing and using the ifplugd daemon.
Is there a simpler solution to the problem?
Statistics: Posted by noob101 — Mon Apr 21, 2025 2:27 pm — Replies 2 — Views 49