ip addr del 192.168.0.156/23 dev eth0
or whichever address you want to get rid of. Of course, the DHCP client
might still be running, in which case it'll just ask for an address again.
--
Russell Senior
[email protected]
On 12/18/25 20:11, Kevin Neely via PLUG wrote:
I have some devices on my network (raspberry pis, running raspberry pi
OS) that started with DHCP and then I assigned the network parameters
using nmcli. To my surprise, they seem to keep the DHCP configuration
/and/ the one I assigned statically and I'm struggling to figure out
how to remove the offending entry. here is an example:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
link/ether b8:27:eb:8b:2d:bdbrd ff:ff:ff:ff:ff:ff
inet 192.168.0.11/23 brd 192.168.1.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet 192.168.0.156/23 brd 192.168.1.255 scope global secondary
dynamic noprefixroute eth0
valid_lft 83356sec preferred_lft 83356sec
Relevant info from "nmcli con show "Wired connection 1"
pv4.addresses: 192.168.0.11/23
ipv4.gateway: 192.168.0.1
the .11 address is the static one, as the DHCP scope is 21-200 or so.
In this case, performing a "nmcli con show "Wired connection 1""
doesn't show the .156 address in any of the settings. I've been
poking around in a bunch of places and at this point, I'm confused as
to what is even managing the network interface. Like DNS resolution,
this seems to have become pretty abstracted over the years as
distributions have migrated from one subsystem to another.
Any pointers on where to look is appreciated!
Kevin
