You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is still the issue, that on many routers after the WAN reconnect/disconnect/go online/offline the session for this MLVPN-WAN-Interface behind a NATed Router comes never up again:
With AVM Fritzboxes ist works, but not with OpenWRT, Tomato or any Type of Telekom LTE-Routers, or mainly all
Huawei devices for LTE...
When The LTE Network resets/restarts, the session belongs to always down. With a /etc/init.d/mlvpn restart the missing session instead comes asap again up.
Looks like, there is a cleaner previous session clossing nessassary when a link is considered offline, so a new NAT-compatible session can be re-established without cold restarting the mlvpn client daemon.
I asume this has todo by reusing a still open Session on a specific Port to the Router, without clean close/clean/restart on the fly to make it work with any Router not just a few AVM Fritzboxes ?
Actualy there is a cron job needed to parse for an "!lteblableh" and then RESTART the entire daemon - but this interrupts the actualy running sessions. In case the LTE link comes not asap up, this ends in a continous 60 seconds cold restart until the LTE link is up again, which is a terrible quickfix and is not very reliable for production.
The text was updated successfully, but these errors were encountered:
There is still the issue, that on many routers after the WAN reconnect/disconnect/go online/offline the session for this MLVPN-WAN-Interface behind a NATed Router comes never up again:
With AVM Fritzboxes ist works, but not with OpenWRT, Tomato or any Type of Telekom LTE-Routers, or mainly all
Huawei devices for LTE...
When The LTE Network resets/restarts, the session belongs to always down. With a /etc/init.d/mlvpn restart the missing session instead comes asap again up.
Looks like, there is a cleaner previous session clossing nessassary when a link is considered offline, so a new NAT-compatible session can be re-established without cold restarting the mlvpn client daemon.
I asume this has todo by reusing a still open Session on a specific Port to the Router, without clean close/clean/restart on the fly to make it work with any Router not just a few AVM Fritzboxes ?
Actualy there is a cron job needed to parse for an "!lteblableh" and then RESTART the entire daemon - but this interrupts the actualy running sessions. In case the LTE link comes not asap up, this ends in a continous 60 seconds cold restart until the LTE link is up again, which is a terrible quickfix and is not very reliable for production.
The text was updated successfully, but these errors were encountered: