ANSWERED ipv6 works with other VPNs but not AirVPN

[airbubble 0]

Hello, AirVPN forum. This is my first post here. Just switched to AirVPN today from a different provider because I was unhappy with their terms and customer service. I'm a happy AirVPN user so far, except that I can't get ipv6 to work. It worked with previous provider but I do not want to go back.

Here are some details: I use AirVPN's wireguard config file in my wireless router, so that all wireless devices connected to the router reach the internet through the VPN tunnel. With old VPN provider, router itself as well as all wireless clients could successfully ping ipv6 addresses. With AirVPN, neither the router iteself nor wireless clients can ping ipv6 addresses 

Here are some commands run in my router when I was using the old VPN provider. Notice that ping6 is working:
 

$ ping6 ipv6.google.com
PING ipv6.google.com (2607:f8b0:4004:c1b::65): 56 data bytes
64 bytes from 2607:f8b0:4004:c1b::65: seq=0 ttl=105 time=24.324 ms
64 bytes from 2607:f8b0:4004:c1b::65: seq=1 ttl=105 time=22.455 ms
64 bytes from 2607:f8b0:4004:c1b::65: seq=2 ttl=105 time=23.873 ms
64 bytes from 2607:f8b0:4004:c1b::65: seq=3 ttl=105 time=22.314 ms
64 bytes from 2607:f8b0:4004:c1b::65: seq=4 ttl=105 time=22.489 ms
^C
--- ipv6.google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 22.314/23.091/24.324 ms

$ ifconfig
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx 
          inet addr:73.150.xxx.xxx  Bcast:255.255.255.255  Mask:255.255.248.0
          inet6 addr: fe80::5653:edff:fe2f:b85e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6836 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6715 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4591526 (4.3 MiB)  TX bytes:1066938 (1.0 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:805 errors:0 dropped:0 overruns:0 frame:0
          TX packets:805 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:114412 (111.7 KiB)  TX bytes:114412 (111.7 KiB)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:172.18.xxx.xxx  P-t-P:172.18.237.167  Mask:255.255.255.255
          inet6 addr: fd00:0:1337:cafe:1111:1111:ce1f:fe0a/128 Scope:Global
          UP POINTOPOINT RUNNING NOARP  MTU:1420  Metric:1
          RX packets:4320 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2464 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4111840 (3.9 MiB)  TX bytes:585204 (571.4 KiB)

wlan1     Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
          inet addr:192.168.x.x  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fd11:1111:cafe:cafe::1/64 Scope:Global
          inet6 addr: fe80::2c0:caff:feb6:74e4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3111 errors:0 dropped:4 overruns:0 frame:0
          TX packets:4578 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:512444 (500.4 KiB)  TX bytes:870050 (849.6 KiB)

$ sudo ip -6 route show
2001:558:1005:e2::/64 dev eth0 proto kernel metric 256 expires 2591020sec pref medium
fd00:0:103:1::/64 dev eth0 proto kernel metric 256 expires 2591020sec pref medium
fd00:0:1337:cafe:1111:1111:ce1f:fe0a dev tun0 proto kernel metric 256 pref medium
fd11:1111:cafe:cafe::/64 dev wlan1 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev wlan1 proto kernel metric 256 pref medium
default dev tun0 metric 1024 pref medium

Here are the same commands run on my router when router is connected to AirVPN: 

$ ping6 ipv6.google.com
PING ipv6.google.com (2607:f8b0:4004:c1b::65): 56 data bytes
^C
--- ipv6.google.com ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

$ ifconfig
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
          inet addr:73.150.xxx.xxx  Bcast:255.255.255.255  Mask:255.255.248.0
          inet6 addr: fe80::5653:edff:fe2f:b85e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:691 errors:0 dropped:0 overruns:0 frame:0
          TX packets:848 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:220921 (215.7 KiB)  TX bytes:175057 (170.9 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:77 errors:0 dropped:0 overruns:0 frame:0
          TX packets:77 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:10499 (10.2 KiB)  TX bytes:10499 (10.2 KiB)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.152.xx.xx  P-t-P:10.152.73.73  Mask:255.255.255.255
          inet6 addr: fd7d:76ee:e68f:a993:5ff1:3f35:a372:a4c9/128 Scope:Global
          UP POINTOPOINT RUNNING NOARP  MTU:1420  Metric:1
          RX packets:299 errors:0 dropped:0 overruns:0 frame:0
          TX packets:345 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:127856 (124.8 KiB)  TX bytes:89264 (87.1 KiB)

wlan1     Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
          inet addr:192.168.x.x  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fd11:1111:cafe:cafe::1/64 Scope:Global
          inet6 addr: fe80::2c0:caff:feb6:74e4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1381 errors:0 dropped:5 overruns:0 frame:0
          TX packets:1514 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:244829 (239.0 KiB)  TX bytes:363686 (355.1 KiB)

$ sudo ip -6 route show
2001:558:1005:e2::/64 dev eth0 proto kernel metric 256 expires 2591903sec pref medium
fd00:0:103:1::/64 dev eth0 proto kernel metric 256 expires 2591903sec pref medium
fd11:1111:cafe:cafe::/64 dev wlan1 proto kernel metric 256 pref medium
fd7d:76ee:e68f:a993:5ff1:3f35:a372:a4c9 dev tun0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev wlan1 proto kernel metric 256 pref medium
default dev tun0 metric 1024 pref medium

It's not a DNS issue because, as you can see, in both cases ipv6.google.com is being resolved to the same ipv6 address.

Searching through the forum uncovered some threads like this one......about potential issue being that AirVPN clients are given an ipv6 addresses are in the fde6:: scope, but my router does not have /etc/gai.conf so my issue may be different.

Can anyone kindly point me in the right direction?

[ss11 20]

Do you use an IPv6 address or IPv4 address as the entry address for your wireguard AirVPN server?
There has to be a way to adapt your router to use ULAs (unique local addresses) for general scope. What router brand and model is that?

[airbubble 0]

Hi ss11. Router uses IPv4 as entry address. Here is the AirVPN wg config file I'm using:

[Interface]
Address = 10.152.73.73/32,fd7d:76ee:e68f:a993:5ff1:3f35:a372:a4c9/128
PrivateKey = xxxxxxxxxx
MTU = 1420
DNS = 10.128.0.1, fd7d:76ee:e68f:a993::1

[Peer]
PublicKey = xxxxxxxxxx
PresharedKey = xxxxxxxxxx
Endpoint = 198.44.136.30:51820
AllowedIPs = 0.0.0.0/0,::/0

I tried using a different wg config file with IPv6 as entry address, but it results in no connectivity whatsoever (neither IPv4 nor IPv6).

Router is a repurposed x86_64 laptop. It runs Tiny Core Linux and everything is setup using just CLI. It's a Busybox environment but iproute2 and several GNU utilities are installed. I can install whatever tools are needed to troubleshoot/solve the problem. Edited ... by airbubble
clarify that more than busybox is available. fix typo.

[airbubble 0]

I opened a ticket with AirVPN support and they just confirmed that there are IPv6 routing issues with all servers in the city I was trying to connect to (NYC, USA). It sounds like some cables are being repaired/replaced in the next 48 hours. I tried a server in a different city and all is well.

Sorry for the noise.

[ss11 20]

Glad to hear you fixed it.  AirVPN treats IPv6 seriously and it's one of the reasons I adore AirVPN. If you'd tell me back when IPv6 RFC was approved that it will take 20+ years and still not be at 100% , and people that don't use it still exist, I would have lost that bet for sure.

[go558a83nk 364]

8 hours ago, ss11 said:

Glad to hear you fixed it.  AirVPN treats IPv6 seriously and it's one of the reasons I adore AirVPN. If you'd tell me back when IPv6 RFC was approved that it will take 20+ years and still not be at 100% , and people that don't use it still exist, I would have lost that bet for sure.

I've yet to have an ISP that supports IPv6 besides mobile data.