GWN7000 Prob when Load Balancing is used


I have a GWN7000 and i’m using Load Balancing with two separate lines on it.
Balancing over packets are perfect but the problem with security sites (like eBanking) is that they reject you when they see that the packets coming from two different ip’s.
Is there a solution for this?
(Thanks in advance).


I have exactly the same problem and I cannot enable the load balancing because of this. I tried to create rules in traffic rules section, that will drop the packages to WAN2 from specific IP but didn’t work. Is there any other suggestion?


@apollon102002 @tek640

another user had the same query and I’ve posted a response in a different thread. click on the link to view the thread.

Essentially, there are some nuances to how the GWN7000 handles static routes, that required some experimentation to get working correctly. You’ll have to read both my posts on this thread to get a full picture. Let me know if this helps.


I have this same issue. Ive tried static routes and they do not work using my router lan ip as next hop. according to some helpfull user who tested the only way to make static routes work is use the isp ip as the next hop. But if you have dynamic ip like me. It would be a short time limited solution.

I also have troubles making openvp to work with nordvpn provider. But that is for another post.


Use DDNS as a way around your dynamic IP:


Can you explain a little more in depth the way to do this? i have no clue how to sort it out using ddns


@scottsip DDNS wouldn’t work on the outbound route. Firstly, in the GWN DDNS can only be configured for one WAN link. Secondly, if the ISP provides private IP ranges (mine give 10.x.x.x addresses on the WAN for example), they cannot be resolved, and thirdly, the problem is with source and destination packets which are assigned to an IP out of the GWN - not name resolution.


@apollon102002 @tek640

Let me recreate the how-to I typed up here for ease of reading:

Scenario - we will use as the target site we want to route to, for purposes of illustration. You can substitute any public ip addresses for these, but keep in mind that if a website has multiple public IP’s you will have to create as many routes as IP’s to be able to test routing through a particular WAN connection. GWN does not allow you to use domain names or wildcards at this time.

The target public IP addresses are: and

You will have to use the ip address of your WAN connection.

For example:
My WAN1 IP address is . You can find the IP address for your WAN connections on the overview page.

So I configured the two routes to with a next hop of, and now all my traceroutes explicitly go to WAN1.

Create two static routes as follows:

name: whatever
interface: wan1/2/3
target network/host: ( public ip address - but you can use just about any public ip address)
next hop: x.x.x.x (specifc WAN IP Address for GWN)
metric: 42 (for WAN1=40, WAN2=41, WAN3=42)

name: whatever2
interface: wan1/2/3
target network/host: ( 2nd public ip address - but you can use just about any public ip address)
next hop: x.x.x.x (specifc WAN IP Address for GWN)
metric: 42 (for WAN1=40, WAN2=41, WAN3=42)

Test using tracert to see that the routes are the same. Before each test go to System>Settings>Debug>Connection Table on the GWN admin page and flush the table just to make sure your routing tables are clean.


Now, if your ISP gives you dynamic IP addresses this is not a perfect solution, but most broadband or fiber provider nowadays don’t change the IP address much.

Try that, it should work.


I got around this issue with my Peplink Balance router by binding a specific LAN IP/MAC address to a specific outbound WAN port. I see no way to do this on GWN7000.


To maximize network relabel laity, the GWN7000 supports traffic load balancing and failover. The GWN7000 features an embedded controller and automated .