SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #660538
Ticket Status: User

PoP: simbx01 - Amis (Maribor)

icmp6 echo request (ping)
[cz] Shadow Hawkins on Sunday, 27 January 2008 03:50:58
Hello, I have just started... and I have some problems making the tunnel work. I have a friend with a 6to4 router... I successfully ping his ipv4 address and I successfully ping also ipv6 address written as ::ipv4. If I'm correct, it replies to icmp6 ping sent through ipv4. It doesn't work for me with this tunnel.... is it turned off? Any other suggestion how to test simple stuff like this? Or could it be turned on, eventually?
icmp6 echo request (ping)
[cz] Shadow Hawkins on Sunday, 27 January 2008 04:40:42
New info.... I got the tunnel running. I can now ping info.nix.cz: [admin@pavlix-router] /ipv6 address> /ping 2001:ae8:4:0:230:48ff:fe42:48c5 2001:ae8:4::230:48ff:fe42:48c5 64 byte ping: ttl=53 time=101 ms 2001:ae8:4::230:48ff:fe42:48c5 64 byte ping: ttl=53 time=99 ms 2001:ae8:4::230:48ff:fe42:48c5 64 byte ping: ttl=53 time=98 ms And www.ipv6.org: [admin@pavlix-router] /ipv6 address> /ping 2001:6b0:1:ea:202:a5ff:fecd:13a6 2001:6b0:1:ea:202:a5ff:fecd:13a6 64 byte ping: ttl=52 time=121 ms 2001:6b0:1:ea:202:a5ff:fecd:13a6 64 byte ping: ttl=52 time=120 ms 2001:6b0:1:ea:202:a5ff:fecd:13a6 64 byte ping: ttl=52 time=122 ms But I cannot ever ping the PoP: [admin@pavlix-router] /ipv6 address> /ping 2001:15c0:65ff:14f::1 2001:15c0:65ff:14f::1 ping timeout 2001:15c0:65ff:14f::1 ping timeout 2001:15c0:65ff:14f::1 ping timeout Though I can see it in traceroute to my country's native ipv6 (info.nix.cz): [admin@pavlix-router] /ipv6 address> /tool traceroute 2001:ae8:4:0:230:48ff:fe42:48c5 ADDRESS STATUS 1 2001:15c0:65ff:14f::1 57ms 56ms 79ms 2 2001:15c0:ffff:7::1 56ms 56ms 58ms 3 2001:15c0:ffff:9::2 59ms 60ms 60ms 4 2001:608::3:0:0:218f:1 82ms 83ms 83ms 5 2001:608::10:0:0:0:115 88ms 83ms 82ms 6 2001:608::11:0:0:0:111 83ms 82ms 83ms 7 2001:608::e75:0:0:0:29 87ms 82ms 83ms 8 2001:608::e04:0:0:0:66 89ms 95ms 89ms 9 2001:7f8::cb9:0:1 91ms 91ms 90ms 10 2001:668::2:0:0:1:442 89ms 94ms 90ms 11 2001:668::2:0:0:1:652 89ms 89ms 89ms 12 2001:668::2:0:0:1:292 99ms 98ms 99ms 13 2001:7f8:14::2 102ms 99ms 107ms 14 2001:ae8:4::230:48ff:fe42:48c5 98ms 98ms 104ms And the statistics don't work... it still says the tunnel is not working (100% Loss), though I'm successfully using it. Nevertheless, thank you for this great service!
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Monday, 28 January 2008 11:57:11
Message is Locked
The state of this ticket has been changed to user
icmp6 echo request (ping)
[ch] Jeroen Massar SixXS Staff on Monday, 28 January 2008 11:57:34
As asked for clearly: Read the "Reporting Problems" section on the Contact page.
icmp6 echo request (ping)
[cz] Shadow Hawkins on Monday, 28 January 2008 14:33:03
NIC handle: PSH3-SIXXS Connections, NAT: There is one NAT to the telefonica o2 network on my router and I have a permanent public ip address. The router is a Mikrotik Routerboard with RouterOS 3.0. [admin@pavlix-router] > ip address print Flags: X - disabled, I - invalid, D - dynamic # ADDRESS NETWORK BROADCAST INTERFACE 0 10.0.0.34/24 10.0.0.0 10.0.0.255 ether5 1 192.168.109.1/24 192.168.109.0 192.168.109.255 ether1 2 192.168.115.1/24 192.168.115.0 192.168.115.255 ether2 3 D 192.168.112.66/24 192.168.112.0 192.168.112.255 ether3 4 D 88.101.155.136/32 194.228.196.39 0.0.0.0 pppoe-o2 5 D 192.168.111.32/32 192.168.111.1 0.0.0.0 pptp-out1 [admin@pavlix-router] > ip route print Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit # DST-ADDRESS PREF-SRC GATEWAY-STATE GATEWAY DISTANCE INTERFACE 0 A S 0.0.0.0/0 reachable 194.228.196.39 2 pppoe-o2 1 A S 0.0.0.0/0 reachable 194.228.196.39 1 pppoe-o2 2 A S 0.0.0.0/0 reachable 194.228.196.39 2 pppoe-o2 3 A S 10.0.0.0/8 reachable 192.168.111.1 1 pptp-out1 4 ADC 10.0.0.0/24 10.0.0.34 0 ether5 5 A S 192.168.109.0/24 192.168.112.66 reachable ether1 1 ether1 6 ADC 192.168.109.0/24 192.168.109.1 0 ether1 7 ADC 192.168.111.1/32 192.168.111.32 0 pptp-out1 8 ADC 192.168.112.0/24 192.168.112.66 0 ether3 9 ADC 192.168.115.0/24 192.168.115.1 0 ether2 10 ADC 194.228.196.39/32 88.101.155.136 0 pppoe-o2 11 A S 212.18.63.73/32 reachable 194.228.196.39 1 pppoe-o2 [admin@pavlix-router] > ipv6 address print Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local, M - multicast # ADDRESS INTERFACE ADVERTISE 0 G 2001:15c0:65ff:14f::2/64 sixxs-o2 yes 1 XG 2002:5865:9b88::1/64 sixxs-o2 yes 2 DG ::88.101.155.136/128 sixxs-o2 no 3 DL fe80::20c:42ff:fe13:857d/64 ether4 no 4 DL fe80::20c:42ff:fe13:857b/64 ether2 no 5 DL fe80::20c:42ff:fe13:857a/64 ether1 no 6 DL fe80::20c:42ff:fe13:857c/64 ether3 no 7 DL fe80::20c:42ff:fe13:857e/64 ether5 no [admin@pavlix-router] > ipv6 route print Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, U - unreachable # DST-ADDRESS GATEWAY-STATE GATEWAY DISTANCE INTERFACE 0 ADC ::/96 0 sixxs-o2 1 A S 2000::/3 reachable ::212.18.63.73 1 sixxs-o2 2 X S 2000::/3 unreachable ::192.88.99.1 1 3 ADC 2001:15c0:65ff:14f::/64 0 sixxs-o2 4 A S 2002::/16 reachable sixxs-o2 1 sixxs-o2 (Please note that the "X" means disabled) [admin@pavlix-router] > /tool traceroute 212.18.63.73 ADDRESS STATUS 1 194.228.196.39 timeout 10ms 11ms 2 88.103.203.1 11ms 11ms 10ms 3 80.188.33.245 11ms timeout 11ms 4 194.228.21.32 11ms 10ms 10ms 5 194.228.21.82 10ms 10ms 11ms 6 prag-b1-link.telia.net 11ms 11ms 10ms 7 hbg-bb2-link.telia.net 24ms 25ms 25ms 8 win-b2-link.telia.net 48ms 48ms 44ms 9 amis-ic-124783-win-b2.c.telia.net 49ms 48ms 43ms 10 maribor3-ge-2-24.amis.net 53ms 53ms 48ms 11 simbx01.sixxs.net 57ms 58ms 53ms [admin@pavlix-router] > /tool traceroute ::212.18.63.73 ADDRESS STATUS 1 :: timeout timeout timeout 2 :: timeout timeout timeout 3 :: timeout timeout timeout 4 :: timeout timeout timeout 5 :: timeout timeout timeout 6 (unknown) timeout timeout timeout [admin@pavlix-router] > /tool traceroute 2001:838:1:1:210:dcff:fe20:7c7c ADDRESS STATUS 1 2001:15c0:65ff:14f::1 56ms 57ms 57ms 2 2001:15c0:ffff:7::1 56ms 56ms 56ms 3 2001:15c0:ffff:9::2 60ms 59ms 60ms 4 2001:890:600:8002::8447 62ms 61ms 61ms 5 2001:4b88::4:9:2:0:0 84ms 224ms 84ms 6 2001:4b88::4:2:1:11:10 98ms 98ms 98ms 7 2001:7f8:1::a501:2871:2 99ms 104ms 99ms 8 2001:838::13:0:0:0:1 101ms 91ms 91ms 9 2001:838::12:0:0:0:2 94ms 94ms 94ms 10 2001:838:1:1:210:dcff:fe20:7c7c 92ms 94ms 93ms (the last one is www.sixxs.net) Sniffing when pinging sixxs.net: [admin@pavlix-router] /tool sniffer> packet print # TIME INTERFACE SRC-ADDRESS DST-ADDRESS IP-PROTOCOL SIZE ... 3 0.471 pppoe-o2 88.101.155.136 212.18.63.73 41 84 4 0.562 pppoe-o2 212.18.63.73 88.101.155.136 41 84 ... 9 1.572 pppoe-o2 88.101.155.136 212.18.63.73 41 84 10 1.664 pppoe-o2 212.18.63.73 88.101.155.136 41 84 Sniffing when pinging the endpoint: # TIME INTERFACE SRC-ADDRESS DST-ADDRESS IP-PROTOCOL SIZE 0 0.1 pppoe-o2 83.209.129.80... 88.101.155.13... tcp 1492 1 0.51 pppoe-o2 88.140.126.27... 88.101.155.13... udp 93 2 0.157 pppoe-o2 88.101.155.13... 83.209.129.80... tcp 40 3 0.262 pppoe-o2 75.73.112.197... 88.101.155.13... tcp 41 4 0.305 pppoe-o2 83.209.129.80... 88.101.155.13... tcp 1492 5 0.307 pppoe-o2 88.101.155.13... 83.209.129.80... tcp 52 6 0.308 pppoe-o2 83.209.129.80... 88.101.155.13... tcp 1492 7 0.31 pppoe-o2 88.101.155.13... 83.209.129.80... tcp 52 8 0.452 pppoe-o2 83.209.129.80... 88.101.155.13... tcp 1492 9 0.454 pppoe-o2 88.101.155.13... 83.209.129.80... tcp 52 10 0.457 pppoe-o2 83.209.129.80... 88.101.155.13... tcp 1492 11 0.458 pppoe-o2 88.101.155.13... 83.209.129.80... tcp 40 12 0.459 pppoe-o2 88.101.155.13... 75.73.112.197... tcp 40 13 0.599 pppoe-o2 83.209.129.80... 88.101.155.13... tcp 1492 14 0.602 pppoe-o2 83.209.129.80... 88.101.155.13... tcp 1492 (nothing relevant to be seen, this looks like a problem - I haven't seen it before now) -- NEW INFO -- As no ping to the PoP got out of my network... I decided to change my IP prefix from 64 to 128. That solved the routing to PoP's ipv6. [admin@pavlix-router] /ipv6 address> /ping 2001:15c0:65ff:14f::1 2001:15c0:65ff:14f::1 64 byte ping: ttl=64 time=56 ms 2001:15c0:65ff:14f::1 64 byte ping: ttl=64 time=56 ms 2001:15c0:65ff:14f::1 64 byte ping: ttl=64 time=56 ms 2001:15c0:65ff:14f::1 64 byte ping: ttl=64 time=79 ms Hope it will be soon seen in the tunnel stats.
icmp6 echo request (ping)
[cz] Shadow Hawkins on Monday, 28 January 2008 20:04:37
My last post to the tunnel ticket... Everything is up and running, thank you very much. I'll soon write some RouterOS ipv6 tutorial.

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

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