I recently moved my Fedora server (version 41) to its own VLAN. It previously had a static IP address of 192.168.1.4, but now I've changed it to a new static IP of 192.168.3.2 through the router (using pfSense, if that's relevant). However, every time I reboot the server, it reverts back to the old 192.168.1.4 IP. After booting, I have to manually flush the IP addresses on the NIC and restart NetworkManager to get the server connected with the correct new IP. This is frustrating since it's a server! I've already found a solution regarding a static IP for dracut-sshd that was causing issues, but I would love to know if there are any other points I should consider to avoid similar problems in the future. Thanks!
3 Answers
Sounds like it could be a NetworkManager issue. You might want to check if anything in the /etc directory still has that old IP by running `sudo find /etc/ -type f -exec egrep -iHn '192.168.1.4' {} +`. Could help you pinpoint the source.
Actually, I figured it out! I had set a static IP for dracut-sshd, which was causing the conflict. Once I corrected that, everything worked fine. Thanks for the suggestions, though!
Have you checked if your router logs any lease assignments? It’s also worth looking at the NetworkManager logs on the machine to see what’s happening when it tries to grab that old IP on boot. If it’s a server, setting a static IP directly on the server instead of relying on DHCP could help you avoid this issue altogether. Just a thought!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures