1
General Discussion / WAN Balancing Not working
« on: May 28, 2020, 02:55:25 pm »
Is it just me or does WAN Balancing not work?
Failover seems to work fine, but if I put two WAN connections in Tier 1 then I get constant DNS or page load failures - having to refresh the page to get it to load. If I switch to failover it works fine. (WAN1 on Tier 1 and WAN2 on Tier 2 (also tried reversing this to verify it's not a WAN connection issue).
I've followed the guide to a tee and also tried a fresh install on new hardware (previously Hyper-V VM and now on a qotom PC).
1. Gateway groups created (packet loss and latency failover)
2. DNS pointing to each separately
3. Monitoring to google and cloudflare dns
4. Firewall points to gateway group
5. DNS firewall rule created for firewall
6. Using Unbound DNS (I've tried to focus on one WAN as well as all interfaces)
7. Default gateway switching is enabled.
8. Sticky connections enabled
9. Running the latest update (20.1.7)
I've also had to create traffic shapers to avoid bufferbloat; aside from that (and 1 VLAN) it's a fresh/default installation.
My connections are:
WAN1. LTE ISP CE (they have a router and give me a 192.168.209.x address on wan interface)
WAN2. LTE ISP CE (same ISP but give a 192.168.0.x address on wan2 interface)
(WAN 3 is not in balancing for groups above (it's in failover only))
WAN3. PPPoE ISP (modem has router that does the PPPoE connections and I've assigned 192.168.100.x address to the wan3 interface)
Questions:
1. Should I be selecting Upstream Gateway in the Single Gateway for any of these WAN single Gateways?
2. Far Gateway?
3. Priority (They were all the same - I changed values and seem to have better results - WAN3 was showing as default gateway - now it's on the bottom)).
I've had to resort to making an alias of half the IPs and put them in groups - so one group is in WAN 1 and everyone else is on WAN 2. I want to load-balance everyone though - this doesn't seem like a resolution....
Failover seems to work fine, but if I put two WAN connections in Tier 1 then I get constant DNS or page load failures - having to refresh the page to get it to load. If I switch to failover it works fine. (WAN1 on Tier 1 and WAN2 on Tier 2 (also tried reversing this to verify it's not a WAN connection issue).
I've followed the guide to a tee and also tried a fresh install on new hardware (previously Hyper-V VM and now on a qotom PC).
1. Gateway groups created (packet loss and latency failover)
2. DNS pointing to each separately
3. Monitoring to google and cloudflare dns
4. Firewall points to gateway group
5. DNS firewall rule created for firewall
6. Using Unbound DNS (I've tried to focus on one WAN as well as all interfaces)
7. Default gateway switching is enabled.
8. Sticky connections enabled
9. Running the latest update (20.1.7)
I've also had to create traffic shapers to avoid bufferbloat; aside from that (and 1 VLAN) it's a fresh/default installation.
My connections are:
WAN1. LTE ISP CE (they have a router and give me a 192.168.209.x address on wan interface)
WAN2. LTE ISP CE (same ISP but give a 192.168.0.x address on wan2 interface)
(WAN 3 is not in balancing for groups above (it's in failover only))
WAN3. PPPoE ISP (modem has router that does the PPPoE connections and I've assigned 192.168.100.x address to the wan3 interface)
Questions:
1. Should I be selecting Upstream Gateway in the Single Gateway for any of these WAN single Gateways?
2. Far Gateway?
3. Priority (They were all the same - I changed values and seem to have better results - WAN3 was showing as default gateway - now it's on the bottom)).
I've had to resort to making an alias of half the IPs and put them in groups - so one group is in WAN 1 and everyone else is on WAN 2. I want to load-balance everyone though - this doesn't seem like a resolution....