General • Re: Routing Bug or config Error?

Okay so, in order to rule that out, I have adjusted the Wireguard setup and made a P2P-Connection for every Node independently.
I now have 3 WG Interfaces, with 10.100.51.5, 10.100.52.5, 10.100.53.5 being the corresponding addresses of 2nd hops.

I have adjusted this in the routes as well, so that I have the 3 default routes 0.0.0.0/0 routed over those IPs mentioned above, as described already in the setup.

There is also a 4th default route from my WAN Connection.

The interesting behavior of trace route now is:
if the Gateway of the VLAN, lets say 10.100.53.5 is down, the 2nd Hop is now the Gateway of the WAN connection, in all 3 VLANs

In my understanding, the route should fail as the 2nd hop is not reachable and not be routed through a random available route?
I have tried changing the routing rule to lookup-only-in-table for all of the routes, yet that did not change anything

Does this have something to do with scope and target scope, reading into it says:

Not all routes that are in routing table are active. Main condition for route to be active is state of its nexthop. It should be resolvable. Inactive routes are not used for packet forwarding. Dynamic routing protocols will only redistribute active routes.

-> https://wiki.mikrotik.com/wiki/Manual:U ... attributes

Any idea on how to prevent this?

Also, thanks a lot for helping me troubleshoot this!

Statistics: Posted by keskol — Sat Jan 27, 2024 2:24 pm

---