DualWAN and routing issue



  • I think I found a solution to my problem, but in case someone else runs across the same thing (or in case there is a better solution):

    There seems to be a potential issue with the use of the routing table, specifically routes from static or openbgp or openvpn, in combination with a MultiWan setup.
    If you have a host which is directed to a specific gateway using a rule on the LAN interface, then it will use that gateway not just for the internet, but for routes that can be reached over OpenVPN, etc.

    In my case I had a site to site tunnel from
    10.100.10.0/24  to 10.100.8.0/24

    10.100.10.0 had MultiWan and was unable to reach hosts on 10.100.8.0, whereas hosts on 10.100.8.0 could reach hosts on 10.100.10.0 just fine.

    My solution was to add rules at 10.100.10.0 with higher priority than those specifying which WAN gateway to use.
    So I made a rule for 10.100.8.0/24 and said to use the default gateway (rather than one of the two specific one), and it started working just fine.

    Is there a smarter way to handle this though? I don't want to forget if I add another tunnel down the road or something similar, and forget to add another rule for the new tunnel to make sure it's traffic goes to the default gateway.


Locked