Forum - traceroute problem :: SixXS - IPv6 Deployment & Tunnel Broker

traceroute problem

Shadow Hawkins on Thursday, 17 January 2008 21:27:44

Hi ppls! I habe a strage problem and cant find out, why it exist. i make a tracert and ping from my home router to my root server:

proxy:~# tracert6 s01.alientxc.de traceroute to cl-2572.ham-01.de.sixxs.net (2001:6f8:900:a0b::2) from 2001:6f8:109e:1::1, 30 hops max, 16 byte packets 1 2001:6f8:109e:1::1 (2001:6f8:109e:1::1) 3002.272 ms !H 3003.866 ms !H 3003.863 ms !H proxy:~# tracert6 s01.alientxc.de proxy:~# ping6 s01.alientxc.de PING s01.alientxc.de(cl-2572.ham-01.de.sixxs.net) 56 data bytes From 2001:6f8:109e:1::1 icmp_seq=2 Destination unreachable: Address unreachable From 2001:6f8:109e:1::1 icmp_seq=3 Destination unreachable: Address unreachable From 2001:6f8:109e:1::1 icmp_seq=4 Destination unreachable: Address unreachable --- s01.alientxc.de ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms proxy:~#

I see, that there is no package thats go to my root server. Ok.. i try it in the reversed direction (rootserver to home)

s01:~# tracert6 home6.alientxc.de traceroute to cl-2164.ham-01.de.sixxs.net (2001:6f8:900:873::2) from 2001:6f8:900:a0b::2, 30 hops max, 16 byte packets 1 gw-2572.ham-01.de.sixxs.net (2001:6f8:900:a0b::1) 20.420 ms 19.949 ms 20.922 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 s01:~# ping6 home6.alientxc.de PING home6.alientxc.de(cl-2164.ham-01.de.sixxs.net) 56 data bytes --- home6.alientxc.de ping statistics --- 13 packets transmitted, 0 received, 100% packet loss, time 12000ms s01:~#

And I also cant ping/connect :? Now I found this website: http://www.berkom.blazing.de/tools/ping.cgi?STR=s01.alientxc.de http://www.berkom.blazing.de/tools/ping.cgi?STR=home6.alientxc.de and this site can ping all my hosts! Also when i ping sixxs.net from my home or server i can correct ping the host. my firewall roules are simple and dont restict the ipv6 traffic. any ideas? Thomas

traceroute problem

Shadow Hawkins on Thursday, 17 January 2008 21:31:42

Ã¶hm.. thats my ipv6 fw rules:

proxy:~# ip6tables -L -vn Chain INPUT (policy DROP 4 packets, 966 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT 0 * * ::/0 ::/0 state RELATED,ESTABLISHED 0 0 DROP 0 * * ::/0 ::/0 rt type:0 27930 2123K ACCEPT 0 eth0 * ::/0 ::/0 31907 3449K ACCEPT icmpv6 * * ::/0 ::/0 4 966 LOG 0 * * ::/0 ::/0 LOG flags 0 level 7 prefix `INPUT:' Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT 0 * * ::/0 ::/0 state RELATED,ESTABLISHED 0 0 DROP 0 * * ::/0 ::/0 rt type:0 478K 136M ACCEPT 0 eth0 * ::/0 ::/0 435K 83M ACCEPT 0 sixxs * ::/0 ::/0 Chain OUTPUT (policy ACCEPT 76424 packets, 7838K bytes) pkts bytes target prot opt in out source destination 0 0 DROP 0 * * ::/0 ::/0 rt type:0

and this is from my server:

s01:/var/kunden/webs/rockih/www# ip6tables -L -vn Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 DROP 0 * * ::/0 ::/0 rt type:0 0 0 ACCEPT 0 * * ::/0 ::/0 state RELATED,ESTABLISHED 82 8528 ACCEPT icmpv6 * * ::/0 ::/0 0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:53 0 0 ACCEPT udp * * ::/0 ::/0 udp dpt:53 0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:22 0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:80 0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:443 0 0 ACCEPT tcp * * ::/0 ::/0 multiport dports 25,110,143,993,995 Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 DROP 0 * * ::/0 ::/0 rt type:0 Chain OUTPUT (policy ACCEPT 513 packets, 51000 bytes) pkts bytes target prot opt in out source destination 0 0 DROP 0 * * ::/0 ::/0 rt type:0

traceroute problem

Shadow Hawkins on Saturday, 19 January 2008 09:51:51

Hi, not IPv6 guru, but I will try... regarding the firewall the best way how to check it is not the cause of your troubles is to switch it off for a moment, it the behavior did not change, it's probably not FW related. It may be helpful to check your routing tables (and paste them here for others). As you are not able to reach even one more hop then the one next to you, I would not expect it to be problem somewhere on the way. As you are using the same pop for both sites, the traffic should go just to the PoP and then to the destination. Bye

traceroute problem

Shadow Hawkins on Saturday, 19 January 2008 18:37:24

I assume you know that this (2001:6f8:109e:1::1) is not the source address you are tracing the other way? Anyway, I believe !H indicates that there is no route to this address. Check your routing table using "ip -6 route" or similar FWIW, I can reach your machines with ICMP, but not using UDP traceroute probes. I assume that's because you either filter incoming UDP or disallow the generated ICMP port unreacheable packets.

bjorn@dewey:~$ traceroute6 s01.alientxc.de traceroute to s01.alientxc.de (2001:6f8:900:a0b::2) from 2001:470:1f04:19d::2, 30 hops max, 16 byte packets 1 bmork.tunnel.tserv3.fmt2.ipv6.he.net (2001:470:1f04:19d::1) 11.478 ms 1.392 ms 1.319 ms 2 1g-3-20.core1.fmt2.ipv6.he.net (2001:470:0:45::1) 1.133 ms 1.284 ms 1.103 ms 3 10g-1-1.core1.sjc2.ipv6.he.net (2001:470:0:31::2) 1.552 ms 1.536 ms 1.36 ms 4 10g-1-3.core1.nyc4.ipv6.he.net (2001:470:0:33::2) 80.844 ms 80.777 ms 80.84 ms 5 10g-1-2.core1.nyc1.ipv6.he.net (2001:470:0:37::2) 83.275 ms 80.846 ms 86.889 ms 6 2001:458:26:2::580 (2001:458:26:2::580) 81.232 ms 81.365 ms 81.433 ms 7 2001:6f8::21:10:1 (2001:6f8::21:10:1) 81.775 ms 82.198 ms 81.567 ms 8 2001:6f8::4:40:1 (2001:6f8::4:40:1) 153.724 ms 153.849 ms 153.505 ms 9 2001:6f8:1:0:87:86:71:132 (2001:6f8:1:0:87:86:71:132) 153.816 ms 154.157 ms 153.9 ms 10 2001:6f8:1:0:87:86:77:47 (2001:6f8:1:0:87:86:77:47) 158.269 ms 158.354 ms 158.549 ms 11 2001:6f8:1:0:87:86:77:49 (2001:6f8:1:0:87:86:77:49) 282.727 ms 249.838 ms 199.742 ms 12 2001:6f8:1:0:87:86:77:51 (2001:6f8:1:0:87:86:77:51) 159.079 ms 158.801 ms 158.824 ms 13 2001:6f8:1:0:87:86:77:53 (2001:6f8:1:0:87:86:77:53) 158.739 ms 158.753 ms 158.73 ms 14 2001:6f8:1:2:87:86:77:55 (2001:6f8:1:2:87:86:77:55) 294.566 ms 258.765 ms 203.33 ms 15 2001:6f8:1:0:87:86:77:62 (2001:6f8:1:0:87:86:77:62) 170.06 ms 169.193 ms 169.004 ms 16 2001:6f8:1:0:87:86:71:233 (2001:6f8:1:0:87:86:71:233) 169.04 ms 169.321 ms 169.254 ms 17 ge1-14-120.br2.isham.de.easynet.net (2001:6f8:800:0:1:0:c240:454) 175.63 ms 175.063 ms 174.755 ms 18 ge7-1.cr20.isham.de.easynet.net (2001:6f8:800:0:1:0:d4e0:459) 175.153 ms 175.066 ms 174.868 ms 19 deham01.sixxs.net (2001:6f8:800:1003::2) 175.888 ms 176.22 ms 176.829 ms 20 * * * 21 * * * bjorn@dewey:~$ tracert6 s01.alientxc.de traceroute to cl-2572.ham-01.de.sixxs.net (2001:6f8:900:a0b::2) from 2001:470:1f04:19d::2, 30 hops max, 16 byte packets 1 bmork.tunnel.tserv3.fmt2.ipv6.he.net (2001:470:1f04:19d::1) 1.428 ms 1.691 ms 1.328 ms 2 1g-3-20.core1.fmt2.ipv6.he.net (2001:470:0:45::1) 5.731 ms 1.209 ms 1.296 ms 3 10g-1-1.core1.sjc2.ipv6.he.net (2001:470:0:31::2) 1.738 ms 1.709 ms 1.325 ms 4 10g-1-3.core1.nyc4.ipv6.he.net (2001:470:0:33::2) 81.122 ms 80.714 ms 87.335 ms 5 10g-1-2.core1.nyc1.ipv6.he.net (2001:470:0:37::2) 90.132 ms 81.249 ms 90.804 ms 6 2001:458:26:2::580 (2001:458:26:2::580) 81.657 ms 81.352 ms 81.671 ms 7 2001:6f8::21:10:1 (2001:6f8::21:10:1) 81.548 ms 81.733 ms 81.606 ms 8 2001:6f8::4:40:1 (2001:6f8::4:40:1) 153.471 ms 153.531 ms 153.600 ms 9 2001:6f8:1:0:87:86:71:132 (2001:6f8:1:0:87:86:71:132) 153.582 ms 153.458 ms 153.569 ms 10 2001:6f8:1:0:87:86:77:47 (2001:6f8:1:0:87:86:77:47) 158.575 ms 158.731 ms 158.811 ms 11 2001:6f8:1:0:87:86:77:49 (2001:6f8:1:0:87:86:77:49) 158.636 ms 158.268 ms 158.312 ms 12 2001:6f8:1:0:87:86:77:51 (2001:6f8:1:0:87:86:77:51) 159.135 ms 158.794 ms 158.776 ms 13 2001:6f8:1:0:87:86:77:53 (2001:6f8:1:0:87:86:77:53) 158.654 ms 158.763 ms 158.818 ms 14 2001:6f8:1:2:87:86:77:55 (2001:6f8:1:2:87:86:77:55) 162.128 ms 162.195 ms 162.270 ms 15 2001:6f8:1:0:87:86:77:62 (2001:6f8:1:0:87:86:77:62) 169.654 ms 169.271 ms 169.291 ms 16 2001:6f8:1:0:87:86:71:233 (2001:6f8:1:0:87:86:71:233) 169.680 ms 169.178 ms 169.305 ms 17 ge1-14-120.br2.isham.de.easynet.net (2001:6f8:800:0:1:0:c240:454) 175.130 ms 175.920 ms 175.047 ms 18 ge7-1.cr20.isham.de.easynet.net (2001:6f8:800:0:1:0:d4e0:459) 175.169 ms 180.527 ms 175.019 ms 19 deham01.sixxs.net (2001:6f8:800:1003::2) 177.174 ms 176.585 ms 175.797 ms 20 cl-2572.ham-01.de.sixxs.net (2001:6f8:900:a0b::2) 194.590 ms 195.215 ms 194.789 ms bjorn@dewey:~$ ping6 s01.alientxc.de -c1 PING s01.alientxc.de(cl-2572.ham-01.de.sixxs.net) 56 data bytes 64 bytes from cl-2572.ham-01.de.sixxs.net: icmp_seq=1 ttl=43 time=195 ms --- s01.alientxc.de ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 195.752/195.752/195.752/0.000 ms bjorn@dewey:~$ ping6 home6.alientxc.de -c1 PING home6.alientxc.de(cl-2164.ham-01.de.sixxs.net) 56 data bytes 64 bytes from cl-2164.ham-01.de.sixxs.net: icmp_seq=1 ttl=43 time=220 ms --- home6.alientxc.de ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 220.629/220.629/220.629/0.000 ms bjorn@dewey:~$ ping6 2001:6f8:109e:1::1 -c1 PING 2001:6f8:109e:1::1(2001:6f8:109e:1::1) 56 data bytes 64 bytes from 2001:6f8:109e:1::1: icmp_seq=1 ttl=43 time=218 ms --- 2001:6f8:109e:1::1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 218.404/218.404/218.404/0.000 ms

Don't know if this helps. But your servers are certainly reacheable.

traceroute problem

Shadow Hawkins on Monday, 21 January 2008 21:46:58

Thanks for you answers.. I found the problem in my firewall and netwerk configuration :D

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