Situation:
We run a lot of RUT240 on mobile with VPN client connecting to our VPN server. The RUT240 have ping reboot functionality activated, it pings our internal VPN server adress that is only reachable when the VPN tunnel is connected.
The idea behind this is to let the router do automatical reboot after it failed to establish a VPN tunnel. This solved connectivity issues we had in the past. It's a workaround another problem, because sometimes the VPN does not connect and then we either have to reboot or disable the VPN profile by hand via a technician on site and activate it again. So we worked around this bug with ping reboot. We were told a few years ago to configure the ping reboot as "PING from mobile", as it failed when we used "automatically selected".
When we set it as "automatically selected", the ping reboot does not work. The VPN connection fails and until we restart the device on site by hand, never comes back.
Now since version 14.5 we noticed that the bug is still there, so we naturally selected "PING from mobile" again. However, now it seems that nothing works. It looks like that now "PING from mobile" literally uses the mobile WAN interface directly. Obviously, the internal VPN server IP is not reachable via mobile wan. Therefor, now all these routers reboot every 90 minutes even though the VPN connection is online and stable.
When we do a manual ping via SSH or the webinterface, it can ping our VPN server. Only ping reboot does not.
We solved it by discarding ping reboot and now reboot daily via automatic reboot. We ask to fix the ping reboot so it either works correctly weith "automatically selected" or, like in the past, notices that the IP to be pinged has to be routed to the tun interface. This was the case before the latest updates.
Currently ping reboot is unusable for our situation. We run over 600 routers and it's becoming arduous. This is all just a workaround another bug in the firmware. Very often we have to just flag and unflag VPN profile to make it work again. "Just" in brackets, because we have to send a technician several hundred kilometers on site to do that.
Please either fix the VPN tunnel hangup problem or ping reboot to route into tun interface like it did before.