SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3719033
Ticket Status: Resolved

PoP: chzrh02 - Init7 AG (Zurich)

chzrh02 still (again?) problems
[ch] Shadow Hawkins on Sunday, 20 February 2011 12:30:24
Ticket 3688869 is now on state "resolved" but I still can't reach chzrh02 from 3 different tunnel endpoints:
# ifconfig gif0 gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280 tunnel inet 62.2.45.169 --> 213.144.148.74 inet6 fe80::215:17ff:fea9:e815%gif0 prefixlen 64 scopeid 0x5 inet6 2001:1620:f00:7::2 --> 2001:1620:f00:7::1 prefixlen 128
POP is reachable by IPv4
# ping -c 4 213.144.148.74 PING 213.144.148.74 (213.144.148.74): 56 data bytes 64 bytes from 213.144.148.74: icmp_seq=0 ttl=58 time=5.572 ms 64 bytes from 213.144.148.74: icmp_seq=1 ttl=58 time=5.633 ms 64 bytes from 213.144.148.74: icmp_seq=2 ttl=58 time=5.557 ms 64 bytes from 213.144.148.74: icmp_seq=3 ttl=58 time=5.607 ms --- 213.144.148.74 ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 5.557/5.592/5.633/0.030 ms
Not so any IPv6 destinations
# ping6 -c 4 2001:1620:f00:7::1 PING6(56=40+8+8 bytes) 2001:1620:f00:7::2 --> 2001:1620:f00:7::1 --- 2001:1620:f00:7::1 ping6 statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss # ping6 -c 4 ipv6.google.com PING6(56=40+8+8 bytes) 2001:1620:f00:7::2 --> 2a00:1450:8002::6a --- ipv6.l.google.com ping6 statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 20 February 2011 13:26:21
Message is Locked
The state of this ticket has been changed to resolved

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

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