Print

[glitchworks]

Something up with tserv1.nyc4.he.net today? I don't see it on the tunnel stats page at all, and my tunnel isn't receiving anything from HE. I've had this tunnel up and running since 2013 so I'm sure I've got it configured properly. I went ahead and set up my own 6in4/protocol 41 from the office to one of my colocated servers just to verify that the ISP hadn't decided to block 6in4 tunnels or something, and that worked fine.

[JRMTL]

Also seeing issues with tserv4.nyc4 as well. was working fine this morning but as soon as I rebooted my router which gave a new ipv4 address I lost all ipv6 connectivity. Oddly enough I have another site still connected to that pop which has not lost connectivity.

so far I checked that ddns updated my ipv4 endpoint ok or at least the tunnel config page says it's been updated.
first wireshark capture shows 209.51.161.14 is replying with icmp type 3 code 3 port unreachable.

have you already submitted a ticket?

[JRMTL]

Connectivity has been restored in my case.

I received the following reply from the ticket I submitted earlier

"It wasn't taking updates earlier, but should be fine now."