24.4.3- ping: sendto: Invalid argument

Started by hgerding, October 04, 2024, 05:38:06 PM

Previous topic - Next topic
We upgraded to 24.4.3 and now the internal routing does not work on one of our machines

we have a virtual IP letsay 172.1.1.10/24  and it can not longer ping 172.1.1.1

get a ping: sendto: Invalid argument

when I change and assign the virtual IP to the wan interface and then back to the lan interface it starts working until the next reboot

I also have routes let's say 192.168.4.0/24 that are pointing at 172.1.1.1 and I also get a sendto error, then I disable the route and re enable it then starts working

then I have a address of lets say 10.30.0.1/23 on the lan interface the same interface with the virtual IP and I try and ping the 192.168.4.0/24 range with the source being the 10.30.0.1 IP and I cannot get it to work. This ll worked fine before the upgrade

What could cause this to happen and any suggestions on fixing it.

Figured it out.

When you have a virtual IP of 172.16.0.5/24 (on LAN) and add a static route to point at 172.16.0.1 for the whole range (which is invalid), it causes the IP not to show up on the interface. But you can make it appear by assigning the virtual IP to a different interface and setting it back. (ie to WAN and then back to LAN)

Then when you disable the routes and enable the routes everything appears to work.

So the mistake was adding a local network as a route. (which probably happened months before and then the reboot killed it)

(The interface does not prevent you from adding a route when it exists as a virtual IP)