SixXS::Sunset 2017-06-06

failing traceroute
[gb] Carmen Sandiego on Monday, 18 April 2005 17:53:59
Hi all, I have been trying to set up my IPv6 tunnel using aiccu between my openBSD box and the PoP. The traceroute fails when I run aiccu test. can anyone offer any advice? Thanks Pete traceroute log bash-3.00# aiccu test sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)" sock_printf() : "client TIC/draft-00 AICCU/2005.01.31-console-openbsd OpenBSD/3.6" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1113838667" sock_printf() : "username PN11-6BONE" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 945400a09f92ef079fb865ffb47863e1" sock_printf() : "authenticate md5 0eca4467565a5d0d373ec421b778126b" sock_getline() : "200 Succesfully logged in using md5 as PN11-6BONE (Peter Nuttall) from 80.46.11.211" sock_printf() : "tunnel list" sock_getline() : "201 Listing tunnels" sock_getline() : "T6838 2001:4bd0:2000:4b::2 80.46.11.211 gblon01" sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>" sock_printf() : "tunnel show T6838" sock_getline() : "201 Showing tunnel information for T6838" sock_getline() : "TunnelId: T6838" sock_getline() : "Type: 6in4-static" sock_getline() : "IPv6 Endpoint: 2001:4bd0:2000:4b::2" sock_getline() : "IPv6 POP: 2001:4bd0:2000:4b::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "POP Id: gblon01" sock_getline() : "IPv4 Endpoint: 80.46.11.211" sock_getline() : "IPv4 POP: 85.116.5.101" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T6838 sock_printf() : "QUIT Tschau!" Tunnel Information for T6838: POP Id : gblon01 IPv6 Local : 2001:4bd0:2000:4b::2/64 IPv6 Remote : 2001:4bd0:2000:4b::1/64 Tunnel Type : 6in4-static Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (80.46.11.211) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 80.46.11.211 (80.46.11.211): 56 data bytes 64 bytes from 80.46.11.211: icmp_seq=0 ttl=30 time=0.977 ms 64 bytes from 80.46.11.211: icmp_seq=1 ttl=30 time=0.977 ms 64 bytes from 80.46.11.211: icmp_seq=2 ttl=30 time=0.978 ms --- 80.46.11.211 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.977/0.977/0.978/0.025 ms ###### Did this work? [Y/n] ####### [2/8] Ping the IPv4 Remote/POP Outer Endpoint (85.116.5.101) ### These pings should reach the POP and come back to you ### In case there are problems along the route between your ### host and the POP this could not return replies ### Check your firewall settings if problems occur PING 85.116.5.101 (85.116.5.101): 56 data bytes 64 bytes from 85.116.5.101: icmp_seq=0 ttl=54 time=103.516 ms 64 bytes from 85.116.5.101: icmp_seq=1 ttl=54 time=100.587 ms 64 bytes from 85.116.5.101: icmp_seq=2 ttl=54 time=51.759 ms --- 85.116.5.101 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 51.759/85.287/103.516/23.739 ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the POP (85.116.5.101) over IPv4 ### This traceroute should reach the POP ### In case this traceroute fails then you have no connectivity ### to the POP and this is most probably the problem traceroute to 85.116.5.101 (85.116.5.101), 64 hops max, 40 byte packets 1 router (192.168.0.1) 0.8 ms 0.8 ms 0.8 ms 2 lo99.mk-lns-16.as9105.net (212.74.111.145) 26.368 ms 26.367 ms 27.339 ms 3 vlan31.switch4-mk.as9105.net (80.40.255.193) 26.367 ms 29.294 ms 109.375 ms 4 ge10-0-40.mk0.as9105.net (80.40.119.229) 56.640 ms 27.344 ms 27.343 ms 5 pos3-0.lon10.as9105.net (212.74.108.10) 34.179 ms 80.78 ms 28.320 ms 6 so-1-0-0.lon12.ip.tiscali.net (213.200.77.253) 30.274 ms 71.287 ms 107.416 ms 7 so-1-0-0.lon22.ip.tiscali.net (213.200.81.117) 56.637 ms 31.250 ms 27.344 ms 8 vl-668-hobgoblin.sov.kewlio.net.uk (213.200.78.139) 31.250 ms 31.250 ms 30.273 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * 31 * * * 32 * * * 33 * * * 34 * * * 35 * * * 36 * * * 37 * * * 38 * * * 39 * * * 40 * * * 41 * * * 42 * * * 43 * * * 44 * * * 45 * * * 46 * * * 47 * * * 48 * * * 49 * * * 50 * * * 51 * * * 52 * * * 53 * * * 54 * * * 55 * * * 56 * * * 57 * * * 58 * * * 59 * * * 60 * * * 61 * * * 62 * * * 63 * * * 64 * * * ###### Did this work? [Y/n] n
failing traceroute
[ch] Jeroen Massar SixXS Staff on Tuesday, 19 April 2005 11:16:00
There is an ICMP filter at/behind the last hop, thus you can ignore it.

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

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