Is there a way I can stop the Peplink from using both Public IP addresses?
Basically, when I try to login to some sites its says “you changed your IP” and I get kicked out.
1 Like
Yes - this normally happens on https sites - make sure you have a http persistence rule enabled in your outbound policies. That keeps all https traffic destined to the same public IP on the same WAN.
YOu can always add another rule to include additional traffic types if needs be.
4 Likes
Hi Martin,
Thank you very much for your response.
Regards
Hess
1 Like
Hi Martin,
I was in that section but i cant find what to change.
Can you please be a little more specific?
EG what field to change?
I just want both my public WAN addresses to only pick one. I am still having conflicting IP address issues with certain sites.
Is it websites and normal web traffic? If so is it http or https ?
The rule should be here but in your case I’d put it at the top of any other rules just to be sure its working:
Of course if the websites are not https then you’ll need to add another rule to catch that traffic and apply persistence to it also.
Thanks Martin.
I get that far but how do I in there stop both IP addresses?
Do I just set one WAN only for Http and https? is that what you mean? currently I have Weighted Balance with both WANS of load 10.
Your screenshot shows a Weighted Balance Rule
that you have called HTTPS_Persistance
A HTTPS Persistence Rule is set by changing the algorithm:
This is what the help text says about this rule:
" Persistence - Traffic coming from the same machine will be persistently routed through the same WAN connection."
BUT you would likely already have a HTTPS_Persistence rule as its there as part of factory settings. If you don’t, add a new that looks like this and drag it above your weighted balance rule:
1 Like
I removed the HTTPS persistence rule at the advice of Peplink support due to things slowing to a crawl / stop working when the interface being used got overloaded or slowed to a crawl (connections would not automatically switch to the other WAN). So far been working well with the persistence rule removed. No websites are giving issues. It could be luck but I am going to keep testing and hope there are no errors because the internet is much more responsive now and if I had to put back the persistence rule I would be unhappy.
The issue with persistence is that I can only use 1 WAN at a time.
Weight balances is ideal because it merges 2 of my connections and gives me almost double the speed.
EG
WAN 1 = 97MBPS
WAN 2 = 50-80MBPS
Weight Balance then merges and gives me around the 150MBPS mark which is perfect. However by doing this it shows the Public IP of both WAN connections which is what is causing my issues.
Can I keep Weight Balance but make the device only show 1 Public WAN.
Yes and No. Each online https website / server / service can only use one WAN at a time because that’s what you want it to do so you don’t get messages from it about IP address changing. But you can use both wans and spread the access requests to the remote server IPs over them,
To do that set the Mode to By Destination and the Load Distribution to Custom.
Not unless you use SpeedFusion Bonding to a hosted Fusionhub so that the only IP visible is the single WAN IP of the fusionhub rather than the WAN links on your local device. Then you can use both WANs at the same time. However I’d try the config above first.
2 Likes