NordVPN Curiosity with 2.8.1
-
I had NordVPN installed in OpenVPN on pfSense 2.7.2 and running just fine in avoiding geoblocks. Before upgrading to 2.8.1 I created a configuration backup. The upgrade concluded normally. Immediately I observed that I was now being geoblocked in the upgraded 2.8.1. I then restored the 2.7.2 configuration to the 2.8.1 installation and normality returned. I have repeated this process twice now with the same result.
While it seems I have solved my geoblock problem on 2.8.1 I thought I’d raise the above observation in case it helps someone else.
-
geoblocking is 'WAN' IP based.
Did your WAN = VPN WAN IP change while using 2.8.1 ?@BrucexLing said in NordVPN Curiosity with 2.8.1:
While it seems I have solved my geoblock problem on 2.8.1 I thought I’d raise the above observation in case it helps someone else.
How can someone find this helpful ? By telling it solvable ? What about : how did you solve it ?
-
@Gertjan It may help someone if they discover that they have become geoblocked after the upgrade to 2.8.1. It may be that if they then follow my solution of restoring an earlier config backup from 2.7.2 they could possibly resolve their problem. No guarantees, but worth a try.
Not sure if the WAN IP (or the VPN IP) changed, but it happened as described 3 out of 3 times.
-
@BrucexLing What probably happened is that the OpenVPN link didn't come up after first upgrade. There is no other rational explanation for your problem. Also, I'm surprised that folks are still using OpenVPN when wireguard is easier to configure and faster.
-
@KOM said in NordVPN Curiosity with 2.8.1:
Also, I'm surprised that folks are still using OpenVPN when wireguard [ . . . ]
Because they're not mutually exclusive.
[ . . .] is easier to configure and faster.
You know what they say about opinions...
-
@tinfoilmatt I'm not sure what you're trying to say, nor why you're saying it.
-
@KOM said in NordVPN Curiosity with 2.8.1:
I'm not sure what you're trying to say, nor why you're saying it.
I was responding to your implication that one must opt to use either OVPN, or WG. They don't.
And also your suggestion that WG is "easier to configure and faster." This is merely your opinion stated as fact.
-
@tinfoilmatt That's a stretch, bud. I never implied any such thing, but it isn't exactly common to run a home VPN with multiple protocols.
Also, have you ever configured OpenVPN and Wireguard yourself? I'm genuinely asking as I can't quite understand how you would think OpenVPN is as easy or easier when there are literally multiple pages of config you have to deal with versus a pair of keys and transit network for Wireguard.
Lastly, measured performance shows WG to be several times faster than OpenVPN so I don't know what you're talking about here either.
-
@KOM said in NordVPN Curiosity with 2.8.1:
KOM
6 days ago@BrucexLing What probably happened is that the OpenVPN link didn't come up after first upgrade. There is no other rational explanation for your problem.
I'm 97% sure that the OpenVPN link did come up. I cycled through this sequence 3 times - same result. If it weren't so time consuming I'd do it again to be 100%. It's a pity there is not a memstick installer for 2.8.1. It would have made the experience so much more pain free.
-
Not questioning your personal reason for using a so called "privacy" VPN, but you might want to arm yourself with some valuable information.
It may not be providing what you think it does. -
@elvisimprsntr Thanks for that elvisimprsntr. I don’t use “privacy” vpns for privacy, just for casual defense against geo-blocking and it works for me. Thumbs up for that video though.
