IP Routes cannot be persistently SET or REMOVED

[Zarox666]

Describe the issue you are experiencing

Independant if IP Routes are removed via ip route del or via route del they reapear after restart.
Analog any routes set via ip route add or via route add disapear after restart.

What operating system image do you use?

ova (for Virtual Machines)

What version of Home Assistant Operating System is installed?

6.1.56

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

1. Set a IP route
2. Restart
3. Check if IP Route is still there

Anything in the Supervisor logs that might be useful for us?

nope

Anything in the Host logs that might be useful for us?

nope

System information

System information

Version	core-2023.10.3
Installation Type	Home Assistant OS
Development	false
Supervisor	true
Docker	true
User	root
Virtual Environment	false
Python Version	3.11.5
Operating System Family	Linux
Operating System Version	6.1.56
CPU Architecture	x86_64
Timezone	Europe/Berlin
Configuration Directory	/config

Core metrics

Processor usage

0.1 %

Memory usage

2.1 %

Supervisor metrics

Processor usage

0 %

Memory usage

0.7 %

Additional information

When I started using HA about 1 year ago this worked, however I cannot say what HA Version that was.
I have succesfully added routes in the config that are still there today.
However due to changes in the Network Infrastructure these routes need to be deleted now, thus I discovered that no modification (neither deleting nor adding) to the routing table survives a reboot.
Also see: https://community.home-assistant.io/t/declare-a-static-route-to-reach-other-lan/311442/8

[agners]

The ip route command changes the Linux (kernel) routing table directly. This routing table is (and always was) volatile. This means any ip route command, on HAOS as well as other Linux distributions, is not persistent.

Typically, routes get added automatically (e.g. as learned by the DHCP server).

The ha network command currently doesn't support static routes. You'd need to use the underlying NetworkManager directly. You can check if you've added static routes this way previously using

nmcli con show "Supervisor enp1s0"

(replace enp1s0 with the primary network interface name in your installation)

To clear any static routes, something along this lines should work:

nmcli con modify "Supervisor enp1s0" ipv4.routes ""

[Zarox666]

as a Windows guy I find it hillarious that you cannot set persistent routes by the route command.
Anyway... yes nmcli showed the routes I try to remove.
However when I type the modify command it fails:

Interesting as it even suggests ipv4.routes "" for the autocomplete. Not sure why its going on about ipv4.dns-data....

[agners]

I've seen that previously, but don't remember what the problem was exactly 🙈

Can you clear that first?

nmcli con modify "Supervisor enp1s0" ipv4.dns-data ""

[Zarox666]

I've seen that previously, but don't remember what the problem was exactly 🙈

lol, jeah I know that too well myself :-)
Thanks for the help by the way.

When I do an nmcli con show it does not show any field called ipv4.dns-data.
thus when I try to empty the value it says

[Zarox666]

Well well searching the internet....
look what I found:

hassio-addons/addon-ssh#583

So far I tried running it through the SSH Addon... let me try on the VM directly.

[Zarox666]

ok that one does not even know nmcli

[agners]

You need to use login to get to the OS shell.

[Zarox666]

thanks!
There it works.

So to sum up:
If you want to configure (add or remove) static routes you need to
a) do it through the nmcli con modify "Your connection name" ipv4.routes Comand
b) you have to execute this comand on the VM itself after login in to it and not through the SSH Terminal addon.

Let me restart to see if the routes stay gone.

[Zarox666]

It worked :-) Thanks!