Remember correctly that my vyos device is behind my pfSense router. I’m using the WAN ip address from pfSense that is exposed to the world as the local-ip for the tunnel (I figured I wanted it to match what hurricane electric showed on the registry). I also set up an ICMP pass rule to allow hurricane electric to ping my outside router.
I also went back and re-created this situation in
Version: VyOS 1.3.0-rc1
Release Train: equuleus
The behavior I’m getting there is a little different. In this case IPv4 continues to work correctly even though I still can’t send v6 packets.
The box seems to think that the tunnel is up, but I’m not sure I agree with it.
vyos@vyos:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
eth0 192.150.23.231/24 u/u wan
lo 127.0.0.1/8 u/u
::1/128
tun0 2001:470:a:454::2/64 u/u HE.NET IPv6 Tunnel
vyos@vyos:~$ ping6 2a00:1450:400e:803::200e
PING 2a00:1450:400e:803::200e(2a00:1450:400e:803::200e) 56 data bytes
From 2001:470:a:454::2: icmp_seq=1 Destination unreachable: Address unreachable
From 2001:470:a:454::2: icmp_seq=2 Destination unreachable: Address unreachable
From 2001:470:a:454::2: icmp_seq=3 Destination unreachable: Address unreachable
From 2001:470:a:454::2: icmp_seq=4 Destination unreachable: Address unreachable
^C
--- 2a00:1450:400e:803::200e ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 71ms
vyos@vyos:~$ traceroute 2a00:1450:400e:803::200e
traceroute to 2a00:1450:400e:803::200e (2a00:1450:400e:803::200e), 30 hops max, 80 byte packets
1 2001:470:a:454::2 (2001:470:a:454::2) 0.021 ms !H 0.005 ms !H 0.005 ms !H
The trace route makes it look like vyos is trying to place the packet in the end of the tunnel, but then it’s not going anywhere. Am I reading that right?
Thanks again for all your help,
Chris