Tunnel using tserv5.lon1 (216.66.80.26) not working

[theonly]

Hello,

I noticed a few days ago that all IPv6 connectivity that I had suddenly stopped working. I can ping the IPv4 server responsible for my tunnel (216.66.80.26), but I cannot ping6 even my tunnel gateway (2001:470:1f08:1b::1) at all.

I use net-tools to set up the tunnel, the client endpoint being behind NAT (which has never been an issue up until now). I would provide ping6 and traceroute6 outputs but neither generate anything useful.

What might be of some help is that I looked at this topic and tried setting the server IPv4 endpoint to 80.167.222.169 and ping 2001:470:28:940:de6e:7f3e:5430:8ed8 which worked fine and I was able to ping6 that address.

Has anyone experienced similar issues or maybe have an idea of what might be going wrong?

Thanks,
Victor

Code Select Expand


sit0      Link encap:IPv6-in-IPv4 
          inet6 addr: ::127.0.0.1/96 Scope:Unknown
          inet6 addr: ::192.168.1.16/96 Scope:Compat
          UP RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sit1      Link encap:IPv6-in-IPv4 
          inet6 addr: fe80::a08:1/64 Scope:Link
          inet6 addr: 2001:470:1f09:1b::1000/128 Scope:Global
          inet6 addr: 2001:470:1f08:1b::2/64 Scope:Global
          inet6 addr: fe80::c0a8:110/64 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:7720 (7.5 KiB)


[cholzhauer]

Did you check the tunnel status page to see if it's up?

Have you emailed ipv6@he.net?

[theonly]

Yes, the tunnel endpoint is up according to the status page.
No, I haven't emailed HE.Net in case the issue lies somewhere within my configuration (though I hadn't changed anything before it happened) and decided to ask here before emailing them.

[kasperd]

First you should check what the configuration of the tunnel looks like on the HE end of the connection. When you login on tunnelbroker.net, you can see the configuration of your tunnel(s). The first thing I would pay attention to is the client IPv4 address. If your IPv4 address is dynamic, you need to update it.

If your problem isn't caused by your IPv4 address changing, then it is most likely caused by something happening on the HE end of the connection. In that case I suggest you email ipv6@he.net

[theonly]

I already checked - it's not a dynamic IP and it all seems to be in order. I'll send them an email tomorrow.

Cheers

[aandaluz]

I'm also experiencing this exact issue at home with my asus n55u router.  Other endpoints work fine (Amsterdam, Paris) , but not London. For the time being, I'll stick to the amsterdam endpoint, although it would be great to get  london up and running, since it has lower latency(48-50ms)  than amsterdam (58-60ms).

[snarked]

Delete this address from your sit1 interface:  2001:470:1f09:1b::1000/128
The ONLY global IPv6 address on your sit1 interface should be the assigned tunnel endpoint (ending in ::2).

PS:  Your sit0 interface has no IPv6 address.  It should have a 6to4 (2002::/16) address.
Also:  Is there some reason why the device which is performing IPv4 NAT isn't the IPv6 tunnel endpoint?  That's usually the easiest place to put it.

[kasperd]

Delete this address from your sit1 interface:  2001:470:1f09:1b::1000/128
The ONLY global IPv6 address on your sit1 interface should be the assigned tunnel endpoint (ending in ::2).

The tunnel server are treating both of them the same anyway. Only prefix::0 and prefix::1 are treated as special by the tunnel server. If you avoid using those two address on your LAN, you could use the entire tunnel prefix as another routed /64.

Your sit0 interface has no IPv6 address.  It should have a 6to4 (2002::/16) address.

The example configuration provided by HE didn't include any 6to4 addresses. And 6to4 is not mandatory. You can set up a 6in4 endpoint without any 6to4 addresses.

Also:  Is there some reason why the device which is performing IPv4 NAT isn't the IPv6 tunnel endpoint?  That's usually the easiest place to put it.

It is the best place, if that device supports 6in4. If the device does not support 6in4 tunnelling, it is not the best place to put a 6in4 tunnel endpoint.

[snarked]

RE: sit1:  By placing the routed address on the interface, it denies that network from the local Ethernet.  If he has a single machine, that's ok, but the second he adds another machine, local routing won't work.

Re: 6to4: True, but then he shouldn't be bringing up that interface if no 2002::/16 address is to be configured.

Re: endpoint:  Most current equipment supports this.