• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.


Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

HE.net tunnel down

Started by vanfawx, May 01, 2019, 08:10:02 AM

Previous topic - Next topic


Last night my tunnel to seattle seems to have stopped working in the middle of the night. I can ping the IPv4 endpoint, but not the IPv6 server IP. Nothing has changed on my config, nor my internet service. I'm using pfsense 2.4.4p2. I've tried taking the interface down/up, but no difference. Is there anything up with the Seattle tunnel endpoint?

Thanks in advance! Here's some information. If you need something else, please let me know.

[2.4.4-RELEASE][root@gateway]/root: ifconfig gif0
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
tunnel inet -->
inet6 2001:470:a:45d::2 --> 2001:470:a:45d::1 prefixlen 128
inet6 fe80::21b:21ff:fe66:7578%gif0 prefixlen 64 scopeid 0x9
groups: gif
[2.4.4-RELEASE][root@gateway]/root: ping
PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=60 time=13.924 ms
64 bytes from icmp_seq=1 ttl=60 time=14.579 ms
64 bytes from icmp_seq=2 ttl=60 time=14.393 ms
64 bytes from icmp_seq=3 ttl=60 time=18.165 ms
--- ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 13.924/15.265/18.165/1.691 ms
[2.4.4-RELEASE][root@gateway]/root: ping6 2001:470:a:45d::1
PING6(56=40+8+8 bytes) 2001:470:a:45d::2 --> 2001:470:a:45d::1
--- 2001:470:a:45d::1 ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss