On Sat, Oct 24, 2026 at 07:37:28 +0200, [email protected] wrote: > What confuses me is that, according to the OP the one address > changes from 172.18.x.x to 65.254.x.x. I didn't even know dhcpd > can do this. Or I'm misunderstanding something.
As already pointed out, the OP is using dhcpcd, not dhcpd. Also, I suspect there's been a transcription error in the IP address, and that it was really 169.254.x.x and not 65.254.x.x. An address in the 169.254. space would be assigned by the DHCP client after it fails to contact a DHCP server. So, as near as I can tell without the OP actually giving us any details: 1) The machine is probably configured with a static 172.18. address on what was originally the inward-facing interface. A cable has been plugged into this interface. 2) There is nothing else currently on the 172.18. network for it to talk to. 3) The OP ran dhcpcd $inward_interface because they thought they were supposed to do this. There was no DHCP server response, so dhcpcd assigned a random 169.254. address. 4) The outward facing interface is DOWN because there's no cable plugged into it. It might (or might not) have been configured to get an IP address from a DHCP router, which is no longer present. So much confusion could be avoided if the OP would show us the actual configuration.
