SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #673991
Ticket Status: User

PoP: iedub01 - HEAnet (Dublin)

iedub01 appears to have lost tunnel routing information
[ie] Shadow Hawkins on Tuesday, 19 February 2008 14:06:03
Static tunnel on OpenBSD 4.1 was working correctly until some time on Sunday at which time iedub01 stopped responding to pings. I have since recieved two tunnel notifications. Tunnel ID is T2629, name cobbled.net Subnet ID is R1299 Yesterday (2008-02-19) all pings to and from the gateway and POP failed although it appeared that some TCP traffic was, erratically getting through, although I cannot be sure that applications were not falling back to IPv4. Both tunnel and subnets appear to be enabled on sixxs.net home page. = interface configuration information = gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 groups: gif egress physical address inet 84.203.180.117 --> 193.1.31.74 inet6 fe80::a00:20ff:fe18:cad5%gif0 -> prefixlen 64 scopeid 0x9 inet6 2001:770:100:21::2 -> 2001:770:100:21::1 prefixlen 128 = routing configuration = Destination Gateway Flags Refs Use Mtu Interface ::/104 ::1 UGRS 0 0 - lo0 ::/96 ::1 UGRS 0 0 - lo0 default 2001:770:100:21::1 UGS 2 1404447 - gif0 ::1 ::1 UH 15 113255 33224 lo0 ::127.0.0.0/104 ::1 UGRS 0 0 - lo0 ::224.0.0.0/100 ::1 UGRS 0 0 - lo0 ::255.0.0.0/104 ::1 UGRS 0 0 - lo0 ::ffff:0.0.0.0/96 ::1 UGRS 0 0 - lo0 2001:770:100:21::1 2001:770:100:21::2 UH 1 17671 - gif0 2001:770:100:21::2 link#9 UHL 0 6 - lo0 2001:770:113:ce4::/64 link#2 UC 2 0 - qe0 2001:770:113:ce4::a 08:00:20:18:ca:d6 UHL 1 14803 - lo0 2001:770:113:ce4::35 08:00:20:18:ca:d6 UHL 0 1015 - lo0 2001:770:113:ce4::a1 08:00:20:b5:f9:f6 UHLc 0 93235 - qe0 2001:770:113:ce4::a3 00:04:ac:97:6a:04 UHLc 0 27 - qe0 2001:770:113:ce5::/64 link#3 UC 2 0 - qe1 2001:770:113:ce5::a 08:00:20:18:ca:d7 UHL 0 0 - lo0 2001:770:113:ce5:209:5bff:fe3b:cedb 00:09:5b:3b:ce:db UHLc 0 17 - qe1 2001:770:113:ce5:230:5ff:fe08:b3d8 00:30:05:08:b3:d8 UHLc 0 3681 - qe1 2001:770:113:ce6::/64 link#4 UC 1 0 - qe2 2001:770:113:ce6::a 08:00:20:18:ca:d8 UHL 0 0 - lo0 2001:770:113:ce6:204:76ff:fe16:5709 00:04:76:16:57:09 UHLc 0 1353 - qe2 2002::/24 ::1 UGRS 0 0 - lo0 2002:7f00::/24 ::1 UGRS 0 0 - lo0 2002:e000::/20 ::1 UGRS 0 0 - lo0 2002:ff00::/24 ::1 UGRS 0 0 - lo0 fe80::/10 ::1 UGRS 0 0 - lo0 fe80::%le0/64 link#1 UC 0 0 - le0 fe80::a00:20ff:fe18:cad5%le0 08:00:20:18:ca:d5 UHL 0 0 - lo0 fe80::%qe0/64 link#2 UC 0 0 - qe0 fe80::a00:20ff:fe18:cad6%qe0 08:00:20:18:ca:d6 UHL 0 0 - lo0 fe80::%qe1/64 link#3 UC 2 0 - qe1 fe80::209:5bff:fe3b:cedb%qe1 00:09:5b:3b:ce:db UHLc 0 69 - qe1 fe80::230:5ff:fe08:b3d8%qe1 00:30:05:08:b3:d8 UHLc 0 280 - qe1 fe80::a00:20ff:fe18:cad7%qe1 08:00:20:18:ca:d7 UHL 0 0 - lo0 fe80::%qe2/64 link#4 UC 1 0 - qe2 fe80::204:76ff:fe16:5709%qe2 00:04:76:16:57:09 UHLc 0 3058 - qe2 fe80::a00:20ff:fe18:cad8%qe2 08:00:20:18:ca:d8 UHL 0 0 - lo0 fe80::%qe3/64 link#5 UC 0 0 - qe3 fe80::a00:20ff:fe18:cad9%qe3 08:00:20:18:ca:d9 UHL 0 0 - lo0 fe80::%lo0/64 fe80::1%lo0 U 0 0 - lo0 fe80::1%lo0 link#8 UHL 0 0 - lo0 fe80::%gif0/64 link#9 UC 0 0 - gif0 fe80::a00:20ff:fe18:cad5%gif0 link#9 UHL 0 0 - lo0 fec0::/10 ::1 UGRS 0 0 - lo0 ff01::/16 ::1 UGRS 0 0 - lo0 ff01::%le0/32 link#1 UC 0 0 - le0 ff01::%qe0/32 link#2 UC 0 0 - qe0 ff01::%qe1/32 link#3 UC 0 0 - qe1 ff01::%qe2/32 link#4 UC 0 0 - qe2 ff01::%qe3/32 link#5 UC 0 0 - qe3 ff01::%lo0/32 ::1 UC 0 0 - lo0 ff01::%gif0/32 link#9 UC 0 0 - gif0 ff02::/16 ::1 UGRS 0 0 - lo0 ff02::%le0/32 link#1 UC 0 0 - le0 ff02::%qe0/32 link#2 UC 0 0 - qe0 ff02::%qe1/32 link#3 UC 0 0 - qe1 ff02::%qe2/32 link#4 UC 0 0 - qe2 ff02::%qe2/32 link#4 UC 0 0 - qe2 ff02::%qe3/32 link#5 UC 0 0 - qe3 ff02::%lo0/32 ::1 UC 0 0 - lo0 ff02::%gif0/32 link#9 UC 0 0 - gif0 = relevant pf rules = inet6_if="gif0" pass out on $inet6_if inet6 keep state pass inet6 proto icmp6 icmp6-type echorep queue bulk pass inet6 proto icmp6 icmp6-type echoreq queue bulk pass inet6 proto icmp6 icmp6-type unreach queue bulk pass inet6 proto icmp6 icmp6-type timex queue bulk = traceroute to iedub01 = traceroute6 to iedub01.sixxs.net (2001:770:18:8::4) from 2001:770:100:21::2, 64 hops max, 12 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * ... = ping pop (iedub01) = PING6(56=40+8+8 bytes) 2001:770:100:21::2 --> 2001:770:18:8::4 --- iedub01.sixxs.net ping6 statistics --- 1 packets transmitted, 0 packets received, 100.0% packet loss = ping tunnel endpoint = PING6(56=40+8+8 bytes) 2001:770:100:21::2 --> 2001:770:100:21::1 --- 2001:770:100:21::1 ping6 statistics --- 1 packets transmitted, 0 packets received, 100.0% packet loss
iedub01 appears to have lost tunnel routing information
[ch] Jeroen Massar SixXS Staff on Tuesday, 19 February 2008 16:09:01
I can ping the PoP's endpoint fine: 64 bytes from 2001:770:100:21::1: icmp_seq=1 ttl=55 time=30.8 ms and also your tunnel endpoint: 64 bytes from 2001:770:100:21::2: icmp_seq=1 ttl=64 time=11.4 ms Where does this go wrong?
iedub01 appears to have lost tunnel routing information
[ie] Shadow Hawkins on Tuesday, 26 February 2008 12:23:05
i can only guess that there is some erratic problem with heanet as i cannot, again, ping anything from inside the tunnel and attempts from outside also fail with the following message (from http://www.berkom.blazing.de/tools/ping.cgi). == PING 2001:770:100:21::2(2001:770:100:21::2) 56 data bytes From 2001:770:18:8:206:5bff:fe3d:e533 icmp_seq=1 Destination unreachable: Address unreachable From 2001:770:18:8:206:5bff:fe3d:e533 icmp_seq=2 Destination unreachable: No route From 2001:770:18:8:206:5bff:fe3d:e533 icmp_seq=3 Destination unreachable: No route From 2001:770:18:8:206:5bff:fe3d:e533 icmp_seq=4 Destination unreachable: No route From 2001:770:18:8:206:5bff:fe3d:e533 icmp_seq=5 Destination unreachable: No route --- 2001:770:100:21::2 ping statistics --- 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4037ms == looking at the routing statistics it would appear that tunnel jumped to life again on the 19th (when you performed your test) and died again on the 24th for still unknown reason. any advise / direction appreciated.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 19 February 2008 16:09:05
Message is Locked
The state of this ticket has been changed to user

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker