Connection succeeds, don't receive IP

moot

Sometime in the last day or so I stopped receiving a new IP after connecting. Connection succeeds, but nothing routes over the VPN interface.

Connecting to: us-west.privateinternetaccess.com

Are there known issues right now? It's not a cache issue or anything like that.

Thanks.

moot

To clarify this, it looks like the VPN interface itself receives an IP, but a "curl ipinfo.io' still shows my static IP. It's not a DNS leak issue (at least on my end).

Max-P

Can you post us the output of 

ip addr
ip ro

While connected to the VPN? This should give us the information we need to know why it's not being routed properly.

moot

Here you go, thanks!

# ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

    link/ether 56:00:00:61:6b:d4 brd ff:ff:ff:ff:ff:ff

    inet 45.63.91.212/23 brd 45.63.91.255 scope global dynamic noprefixroute ens3

       valid_lft 73456sec preferred_lft 73456sec

3: ens7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

    link/ether 5a:00:00:61:6b:d4 brd ff:ff:ff:ff:ff:ff

5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100

    link/none

    inet 10.24.10.6 peer 10.24.10.5/32 brd 10.24.10.6 scope global noprefixroute tun0

       valid_lft forever preferred_lft forever

# ip ro

default via 45.63.90.1 dev ens3 proto dhcp

default via 10.24.10.5 dev tun0 proto static metric 50

default via 45.63.90.1 dev ens3 proto dhcp metric 100

10.24.10.1 via 10.24.10.5 dev tun0 proto static metric 50

10.24.10.5 dev tun0 proto kernel scope link src 10.24.10.6 metric 50

45.63.90.0/23 dev ens3 proto kernel scope link src 45.63.91.212 metric 100

45.63.90.1 dev ens3 proto static scope link metric 100

104.200.151.39 via 45.63.90.1 dev ens3 proto static metric 100

169.254.169.254 via 45.63.90.1 dev ens3 proto dhcp

169.254.169.254 via 45.63.90.1 dev ens3 proto dhcp metric 100

Max-P

Thanks for the additional information!

I suspect the issue is with your routing table: your network interface appears to be configured twice.

default via 45.63.90.1 dev ens3 proto dhcp
default via 10.24.10.5 dev tun0 proto static metric 50
default via 45.63.90.1 dev ens3 proto dhcp metric 100

You have two default routes to your ISP sandwiched between PIA's default route, so it's likely the reason why you're still leaking through your ISP.

How are you connecting to your ISP? Are you just using NetworkManager or something like dhcpcd/dhclient/netctl/systemd-networkd/wicd?

You can probably try removing the extra route, but it won't persist across reboots:

sudo ip ro del default via 45.63.90.1 dev ens3

It's also possible however that doing so will end up removing both of them.

Another possible approach is to do what the app does:

sudo ip ro add 0.0.0.0/1 via 10.24.10.5 dev tun0
sudo ip ro add 128.0.0.0/1 via 10.24.10.5 dev tun0

This essentially adds two routes that are one bit more precise than the default one, so it will be used regardless. Note that with this one, you will need to add the two routes every single time you connect OpenVPN, and won't persist across reboots either.

Hope this helps!