On Sat, 28 Oct 2017 19:26:01 +0000, rih5342 wrote:
> I get an IP address that DOES MATCH the ifconfig output.
You wouldn’t - 10.x.x.x is a private network. The public address is what
the website shows, which is what you should see.
That should be different than the address your ISP assigns your router.
If it is, congratulations, your VPN is working. If it isn’t, that
doesn’t mean your VPN isn’t working (it can mean that you’re running a
split-tunnel configuration with the router config, but for this type of
usage, you want it to not be a split-tunnel config).
If the address matches that of your router, then you need to talk to your
VPN provider to find out what’s wrong in the config file you’re using.
My procedure for testing whether a VPN is working or not…
I determine what my Default Gateway should be by running the following. It should identify all gateway addresses including both the normal LAN gateway when the VPN is not enabled plus the VPN gateway if it’s configured and available. You should be able to know which gateway address is appropriate for you network connections by knowing what your IP address is both when running the VPN and not.
ip route
Then,
I run the traceroute command to some Internet address and I generally specify an IP address so name resolution is not an issue(nameservers are frequently mis-configured or dependent on VPN functionality which can screw things up), your traceroute command or any other even without flags is sufficient(I recommend something simple like below). You only want to know the address of the first hop, which would be your currently active Default Gateway