Changed R8000 to RT AC3200 for load balancing but alas it does not work...

[Ajai]

So I changed my perfectly good R8000 to a RT AC3200 since I had two ethernet based internet connections from different providers "Primary & Backup" and when I found out about dual WAN I was hooked. After some enquirers on snb I went ahead and gave back the R8000 for partial store credit and bought the RT AC3200 which is a nightmare when it comes to load balancing. Dont get me wrong it as good if not better than the R8000 in other department "Other than the looks" but load balancing has failed for me miserably.

Here are the ways in which the RT AC3200 torments me daily with regards to dual WAN:

1. Using only one line at a time not both so its not really load balancing
2. Changing the active line for some reason resulting in any active download being canceled/paused
3. Once in a while the internet goes out for no apparent reason removing the primary connection or restarting makes the net live again.

After assistance from Asus support I got the following advices for the problems with Dual WAN:

1. Sir that line must have a much higher ratio set or the speed of the line must be much more than the second connection.
2. Sir it might not be able to ping the IP so it must have changed the line.
3. Sir be sure you dont have over lapping IPs in the WAN's

After hours online I still have not found anything that solved my problem I will RMA this junk and give it another shot otherwise go back to the R8000 or any thing AC3200. I have configured it to have equal ratio, the speeds of the lines are the same 2MBps. If this thing cant ping while downloading at max speed why did I spend so much on it?. Overlapping IP's with two different ISP's how is that even possible, one is 10.209.6.x the other is 10.10.6.x.

Pretty sad really I had huge hopes from load balancing

 

[pete y testing]

1. Using only one line at a time not both so its not really load balancing

yes as it is load balancing not line bonding and or aggregation

load balancing sends all one type of protocol to one provision which another protocol type the other provision etc etc

 

[texashoser]

If you search the other threads, you'll find that the dual WAN function has been problematic and buggy since it was released. It just doesn't work well.

With regards to #1, per-packet load balancing couldn't work in the first place because both ends have to support it, not to mention you have to different ISP's. The best it can do is to send one stream/connection over one ISP and send the next stream/connection to the other ISP. Because of this, if the two internet connections have very different speeds, you're going to be limited by the slower ISP. In this case, using failover is better, but load balancing has bugs as well.

 

[geekmaster]

"3. Sir be sure you dont have over lapping IPs in the WAN's ... Overlapping IP's with two different ISP's how is that even possible, one is 10.209.6.x the other is 10.10.6.x."

Not only is it possible that two different 10.x.x.x IP addresses are overlapping, but BY DEFAULT, all IP addresses in the 10.x.x.x subnet are in the SAME IP subnet, because the default subnet mask for the 10.x.x.x private IP range is 255.0.0.0.

You must either change your subnet masks to 255.255.255.0, or use the 192.168.x.x private IPs, which use a more limited 255.255.255.0 subnet mask.

Since the IPv4 address space has become exhausted, increasing numbers of ISPs are using PRIVATE IP address ranges (meant for use on LANS) for their customers. You WAN address is not a public internet address -- it is part of your ISPs private LAN, and both ISPs use the same LAN IP subnet 10.x.x.x.