0

I asked a question regarding some faulty kernel routing tables configuration that I had in one of my machines due to an unexpected power outage. That event left the machine with a messed up network (netplan btw) config and I did my best to leave it functional.

Finally, I was able to find out a solution for the issue that I asked in the aforementioned question, but the fix is not persistent over restarts. That is, every time I restart the machine, I have to manually run:

# ip address delete 172.17.0.1/24 dev enp67s0f0

I have looked for ways to make this persistent but none of them seem to work and I don't exactly know how I can keep this permanent. Any feedback will be highly appreciated!

Improve this question
2
  • That's not an iptables config though. And the easiest way to make "undo something" persistent is to make "do nothing" persistent, no?
    – Tom Yan
    Commented Jan 20, 2023 at 10:46
  • Oops, sorry if I'm mixing terms here. I'm fairly new to Linux networking. It makes sense but not sure what's the opposite rule of that one.
    – albertoperdomo2
    Commented Jan 20, 2023 at 10:48

1 Answer 1

Reset to default
2

Deletion is already permanent, because addresses are not stored permanently in ip addr – the interface always starts with zero addresses on every boot; some software has to re-add them every time. So you have to remove the address from the place that is causing it to be re-added.

Most of the time, that would be your regular network configuration tool – Netplan, or systemd-networkd, or ifupdown (aka /etc/network/interfaces); maybe a stray DHCP client (dhcpcd or dhclient). In your specific case though, it may also come from Docker configuration which is using the wrong interface.

Improve this answer
1
  • I'll check this and reach back. Thanks for the explanation!
    – albertoperdomo2
    Commented Jan 20, 2023 at 12:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .