Tunnelbroker ipv6 - LAN cannot ping

No, the LAN to WAN forwarding is in place:

And according to the tracert output, ICMPv6 can traverse the tunnel endpoint but can't go outside of the tunnel broker network.

You are absolutely right. This should be escalated to HE by posting on their forums or sending them an email. Although I wonder if this could be an MTU issue?

1 Like

I wonder if there's a Windows IPv6 setting issue.

  • You've yet to show us that your Windows machine is getting a public HE IPv6 address.
  • Also, you haven't showed us your config after making the suggested changes.
user@machine:~$ ping6 www.google.com
PING www.google.com(xxx-in-x04.1e100.net (2607:f8b0:4004:811::2004)) 56 data bytes
64 bytes from xxx-in-x04.1e100.net (2607:f8b0:4004:811::2004): icmp_seq=1 ttl=57 time=3.79 ms
64 bytes from xxx-in-x04.1e100.net (2607:f8b0:4004:811::2004): icmp_seq=2 ttl=57 time=3.55 ms
64 bytes from xxx-in-x04.1e100.net (2607:f8b0:4004:811::2004): icmp_seq=3 ttl=57 time=3.56 ms
^C
--- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 3.559/3.639/3.792/0.128 ms

I'm using HE.

He did. The very first screenshot in his opening post shows that his PC can connect using IPv6 and that it is using the HE tunnel.

2 Likes

Aaaah yes...this ping thing is a weird issue....