I got a high site with a Hex Lite on it. An EoIP tunnel runs from it to another site with both end points pingable.
The tunnel is connected meaning I can see the IPs of the units connecting via it on the neighbors list.
The issue is that unless I run torch on one of the interfaces (eth 1-5) data doesn’t go through the tunnel. None of the IPs in the tunnel can ping one another.
Running 6.35.4 but upgrade it to 6.38.5 with same issue.
It used to work before I had a power failure on the site so I think I might need to replace the unit but its quite drive up a mountain and hoped someone might help before I really need to go there.
Currently I just keep Winbox open and run torch and everyone is happy.
I have similar problem with wAP R, version 6.43.4, i build eoip over lte to central office, and eoip only work (passed traffic) when i run torch (at any interface) at wAP winbox
) is not the same as fast-path (L2 feature - configured in
/interface bridge settings
).
@globalrebel: I am quite surprised to be honest. I have EoIP on few routers and it works fine even with enabled fast-path. In addition, according to manual, EoIP should support fast-path since 6.33 . To me, it sounds like some additional issue which, by coincidence, affects your eoip while fastpath is active.
what I meant by my short reply, that EOIP probably runs over an existing & secured tunnel (pptp, ipsec, …). This tunnels may require to exclude it’s packets from being fasttracked.
and just for info, torch disabled FP & FT (=FP+conn tracking)
@globalrebel> : I am quite surprised to be honest. I have EoIP on few routers and it works fine even with enabled fast-path. In addition, > according to manual> , EoIP should support fast-path since 6.33 . To me, it sounds like some additional issue which, by coincidence, affects your eoip while fastpath is active.
We have EoIP a long time used and works perfectly for SXT-LTE even with enabled fast-path, but it dont work for wAP routers (only).
