Hi everybody,
i have bought an asus router (RT - AC2900), and installed last merlin version (386_12_4).
i'am testing features & and theses reliabilties.
So my router is dualwan (not bridged), so each wan ports have local IP
- primary wan is a 4G connexion on port LAN1
- secondary is ADSL box on port WAN
for my testing case and to get something simple, i have used only one VPN connexion which route all outgoing connection for lan 192.168.1.0/24 to this VPN connection.
Initial test state:
- all WAN connexion ok
- vpn connection established
- LAN 192.168.1.0/24 reachable.
Test: poweroff the 4G connexion
expected behaviour:
- ASUS router switch secondary wan (ADSL box)
- vpn connection lost & reconnection
- lan 192.168.1.0/24 reachable
Result:
- asus router switch to secondary wan
- vpn connection is correctly reconnected
- lan 192.168.1.0/24 not reachable
from the result state i have tested 2 cases
1) if i power up the 4G router, i go back to test initial state (all is working ... after vpn reconnection etc..)
2) if i reboot the asus router (4G router is still power off), then all is working fine on secondary WAN
it seems routing table could be not correctly initialized when switching from an interface WAN to another ?
i don't think the problem is coming from the VPN provider as i have same behaviour with another vpn provider.
i don't know what to provide, but i guess that the test case is easy to reproduce by "specialists"
regards
i have bought an asus router (RT - AC2900), and installed last merlin version (386_12_4).
i'am testing features & and theses reliabilties.
So my router is dualwan (not bridged), so each wan ports have local IP
- primary wan is a 4G connexion on port LAN1
- secondary is ADSL box on port WAN
for my testing case and to get something simple, i have used only one VPN connexion which route all outgoing connection for lan 192.168.1.0/24 to this VPN connection.
Initial test state:
- all WAN connexion ok
- vpn connection established
- LAN 192.168.1.0/24 reachable.
Test: poweroff the 4G connexion
expected behaviour:
- ASUS router switch secondary wan (ADSL box)
- vpn connection lost & reconnection
- lan 192.168.1.0/24 reachable
Result:
- asus router switch to secondary wan
- vpn connection is correctly reconnected
- lan 192.168.1.0/24 not reachable
from the result state i have tested 2 cases
1) if i power up the 4G router, i go back to test initial state (all is working ... after vpn reconnection etc..)
2) if i reboot the asus router (4G router is still power off), then all is working fine on secondary WAN
it seems routing table could be not correctly initialized when switching from an interface WAN to another ?
i don't think the problem is coming from the VPN provider as i have same behaviour with another vpn provider.
i don't know what to provide, but i guess that the test case is easy to reproduce by "specialists"
regards
Last edited: