I am trying to create my own tunnel endpoint on a VPS in Australia (because there is no HE pops here, which makes for very high latency).
Unfortunately, I only have the one /64 available to my VPS to use: 2400:c400:626:3020:: /64
My VPS is running CentOS 7 minimal and has been configured with the following:
ip tunnel add sit1 mode sit ttl 255 remote 188.8.131.52 local 184.108.40.206
ip link set dev sit1 up
ip -6 addr add 2400:c400:626:3020::3/64 dev sit1 # There is a reason for choosing :3 explained later
ip -6 route add 2400:c400:626:3020::/64 dev sit1 metric 1
On the client side, I am using an ASUS DSL-AC68U VDSL modem/router. It has a configuration page specifically for tunnels (handy!). It has been configured as follows:
Connection type: Tunnel 6in4
Server IPv4 Address: 220.127.116.11
Client IPv6 Address: 2400:c400:626:3020::2
IPv6 Prefix Length: 64
Server IPv6 Address: 2400:c400:626:3020::3
Tunnel MTU: 1480
Tunnel TTL: 255
[b]IPv6 Lan Setting[/b]
LAN IPv6 Address: 2400:c400:626:3020::1 # Can't modify this. Auto chosen from lan prefix
LAN Prefix Length: 64
LAN IPv6 Prefix: 2400:c400:626:3020::
[b]IPv6 DNS Setting[/b]
IPv6 DNS Server 1: 2001:4860:4860::8888
IPv6 DNS Server 2: 2001:4860:4860::8844
IPv6 DNS Server 3: ~blank~
[b]Auto Configuration Setting[/b]
Enable Router Advertisement: Enable
So far bidirectional communication has been established between the VPS and the Router. They can both ping each other.
Using the Routers built-in testing tools (ping, traceroute, nslookup) i tried to ping ipv6.google.com but did not receive any replies.
On the VPS, I ran tcpdump on sit1 and that showed the incoming traffic from the router, but nothing going back out to the router (except the ping to-from the vps).
I've eliminated the possibility of firewalls being in the way by disabling the on both ends.
I suspect that this is a routing issue on the VPS side.
Can someone point me in the right direction on how to solve this? I would be greatly appreciative.
Thanks in advance for your help.