Hi,
I encounter a strange issue today.
I had a failure on my primary link and another failure on my dynamic ip update script for my secondary link…
When the primary link came back, i tested my secondary link input rules and routes (when my 2 links are up and running).
A simple curl from an internet test server to my secondary ip link (LTE) took very long time (at least 20-30s) to answer.
However, output (NAT) from LAN to internet via the secondary link do not have any issue and work as expected.
Of course i do not have any issue on my primary link (input/output).
I defined a simple route in main table to force output to the server where i tested input (curl) and after that, it worked as expected. The requests on the secondary link answer very quick as expected.
In conclusion, there seems to be an routing issue, but i do not understand where i made a mistake.
My router is a CCR2116 with RouterOS 7.7.
Here is the config in attachment, could you please check if everything is fine ?
EDIT1 : i tried to use tools/Torch to check, and as soon as i enable Torch, everything work perfectly ! I stop Torch issue come back again !
EDIT2 : upgraded to the last 7.10.2, no change. I even tried to completely disable recursive monitoring for primary link, (and only use distance) no change
EDIT3 : in real failover (when primary link is really down), no issue, the secondary ip (failover link) work and answer very quickly
EDIT4 : using packet sniffer tool has the same effect that Torch. As soon as i enable, it works perfectly. It seems that it is the promiscious mode that make it works. VERY strange…
EDIT5 : opened a support ticket SUP-121920
thanks !
router1 (1).rsc (5.69 KB)