Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12
  1. #11
    Join Date
    Jan 2021


    Hey guys, I solved it by adding Mikrotik hEX router between 2nd VSDL bond and Untangle.
    I see you advised to do the same.

    Just to sum up the story:
    Untangle runs on dedicated miniPC, so like an appliance (no VM or hypervisor involved).
    4 VDSL links are merged into two bonds (two links merged to one bond via a terminator with RJ45 out). Terminators are delivered by ISP and no changes are allowed, proprietary device. One bond has public static IP assigned, but that doesn't make a difference. Connection is realized via PPPoE with username/pwd, but with specific VLAN ID (same for both bonds). In the end there's one ISP box/device routing all VSDL connections in the area. Hence the same gateway problem.
    Mikrotik hEX router was installed between second VSDL bond and Untangle. One more NAT introduced, yes, but changed the gateway for Untangle, so worth the trouble.
    Once Mikrotik hEX was added to the equation, WAN Balancer works just fine and Untangle route table now looks as expected.

    Thanks everyone for contribution. Cheers.

  2. #12
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Phoenix, AZ


    You can disable the 2nd NAT, just untick the NAT box on the WAN interface aimed at the Mikrotik, and go slap some static routes in the Mikrotik for any networks beyond Untangle, and target the routes to the IP on Untangle's WAN.

    Friends don't let friends double NAT!
    Rob Sandling, BS:SWE, MCP
    Phone: 866-794-8879 x201

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

SEO by vBSEO 3.6.0 PL2