server ping-restart does not notify client

[cogninaut]

Hello everyone,

I am trying to set up my server to recover gracefully when there is a fault with routing on the client side. This typically happens when the wifi drops, or you manually disable and then enable the ethernet interface. The

route remote_host 255.255.255.255 net_gateway

is then deleted from the route table and the client can no longer communicated with the server because it tries to route the packet through the tunnel

In this situation initially the client still receives the pings from the server so it thinks the connection is ok. The server will eventually ping-restart itself, drop the connection and send no more pings. After another ping-restart interval passes the client will then itself restart establishing a new connection

what is odd is that the server does not notify the client before it drops the connection, at it does when for example your restart it, which leads to having to wait twice the ping-restart interval until the connection is re-established.

Is that the intended behavior, not notifying the client on a ping-restart? Note that the client does notify the server when it ping-restarts.

Also I am thinking of reducing the ping-restart interval to 20 seconds, with ping 3-5 seconds, to achieve a more acceptable time that the connection is down. Do you see any problems with this?

Any insights will be greatly appreciated
Thanks in advance