ipv6 packets getting lost after switching to new vpn provider

[GNUser]

Hello forum. My IPv6 skills are not the best. Maybe one of you can help me.

My wireless router is just an old laptop running TCL15 x86_64. The router connects to a paid VPN service so that all of my family members' wifi devices access the internet through the VPN tunnel for increased privacy. I use the wireguard config file provided by the VPN provider.

This past weekend I switched VPN providers because I was unhappy with previous provider's policies and customer service. The transition went smoothly except that now the router cannot ping any ipv6 addresses. I asked for help on the new provider's forum but no promising leads so far.

Here is the working setup with prior VPN provider:

Code: [Select]

$ 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 is the broken situation when using the new VPN provider:

Code: [Select]

$ 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

$ sudo traceroute6 ipv6.google.com
traceroute to ipv6.google.com (2607:f8b0:4004:c0b::8a), 30 hops max, 72 byte packets
 1  fd7d:76ee:e68f:a993::1 (fd7d:76ee:e68f:a993::1)  21.069 ms  38.482 ms  18.051 ms
 2  2607:9000:a000:25::1 (2607:9000:a000:25::1)  27.101 ms  28.720 ms  27.374 ms
 3  *  *  *
 4  2607:f740:70:101::5 (2607:f740:70:101::5)  26.790 ms  23.661 ms  30.469 ms
 5  *  *  *
 6  *  *  *
 7  *  *  *
 8  *  *  *
 9  *^C

It's not a DNS issue because  ipv6.google.com  is resolving to the same address with both providers. Both providers say the support IPv6. The wireguard config files of the two providers are very similar.

The main difference I'm noting is with the IPv6 address on the VPN interface:
Old provider: inet6 addr: fd00:0:1337:cafe:1111:1111:ce1f:fe0a/128 Scope:Global
New provider: inet6 addr: fd7d:76ee:e68f:a993:5ff1:3f35:a372:a4c9/128 Scope:Global

Maybe in order for things to work with the address they are giving me I need to set up a special route? I'm out of ideas. Any guidance would be very much appreciated.

[patrikg]

test-ipv6.com

[GNUser]

Hi patrikg. My router is CLI only, so a website is not going to help, unfortunately.

[gadget42]

definitely would like to know what you find out and whether it was at your end or airvpn.

[GNUser]

Hi gadget42. I think the problem may be missing routes (either in my routing table or theirs). ping6 only works for airvpn.org and, surprisingly, debian.org. I cannot ping any other domain using IPv6 when VPN is connected.

If I find a fix I'll make sure to post it here.

[GNUser]

AirVPN just confirmed that they are having IPv6 routing issues with all servers in the city I was trying to connect to (NYC, USA). I tried a server in a different city and all is well.

Sorry for the noise.