Forum - Routing PLIX <-> OVH - plwaw01 - ICM :: SixXS

Routing PLIX <-> OVH - plwaw01 - ICM

Shadow Hawkins on Wednesday, 01 August 2012 17:11:30

Welcome I have a problem. I don't know why I can't ping a server in network OVH. I've tunnel on POP plwaw01 - ICM According to the OVH problem is on your side traceroute6 to server in OVH

traceroute to po-land.pl (2001:41d0:8:7c5::10) from 2001:6a0:200:292::2, 30 hops max, 16 byte packets 1 gw-659.waw-01.pl.sixxs.net (2001:6a0:200:292::1) 129.821 ms 160.581 ms 129.64 ms 2 2001:6a0:1:1::2 (2001:6a0:1:1::2) 130.01 ms 138.99 ms 89.687 ms 3 kp-mm-r3.rtr.net.icm.edu.pl (2001:6a0:1:1::1) 93.353 ms 88.765 ms 89.513 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * (...) 30 * * *

Routing PLIX <-> OVH - plwaw01 - ICM

Shadow Hawkins on Thursday, 02 August 2012 04:18:00

Works for me... (first 2 hops not shown for privacy) Please note that I usually use ICMP traceroute as there is less risk to get filtered. And a second note about traceroute: In my experience, not receiving an answer (the *) is often caused by the PING REPLY packet from the target host not making it back to you, NOT by the PING packet not reaching the target host (which is usually the first and only reason you are tempted to think about)...

# traceroute6 -I po-land.pl traceroute to po-land.pl (2001:41d0:8:7c5::10) from ... ... 3 ge0-1.gv1.ip-max.sixxs.net (2a02:2528:ff:1::2) 27.356 ms 20.426 ms 17.293 ms 4 ge3-14.ar01.gva253.ip-max.net (2a02:2528:103:1::1) 27.719 ms 25.514 ms 23.561 ms 5 ge3-8.cr01.gva253.ip-max.net (2a02:2528:102:2::1) 27.882 ms 24.845 ms 17.442 ms 6 ge3-2.br01.gva253.ip-max.net (2a02:2528:102:1::2) 31.582 ms 25.396 ms 23.569 ms 7 eqx.zur.ovh.net (2001:7f8:c:8235:194:42:48:30) 33.433 ms 28.624 ms 26.192 ms 8 fra-5-6k.fr.eu (2001:41d0::671) 55.998 ms 33.762 ms 30.991 ms 9 rbx-g2-a9.fr.eu (2001:41d0::b51) 49.481 ms 46.321 ms 39.638 ms 10 vss-5a-6k.fr.eu (2001:41d0::583) 4247.756 ms 7920.005 ms * 11 2001:41d0:8:7c5::10 (2001:41d0:8:7c5::10) 47.571 ms 39.377 ms 37.640 ms

Nicolas

Routing PLIX <-> OVH - plwaw01 - ICM

Shadow Hawkins on Thursday, 02 August 2012 12:39:14

Ok, I know, but me not works. Hot you explain this?

root@HTPC:~# wget -6 po-land.pl/index.php -T 60 --2012-08-02 12:35:55-- http://po-land.pl/index.php Resolving po-land.pl... 2001:41d0:8:7c5::10 Connecting to po-land.pl|2001:41d0:8:7c5::10|:80... failed: Connection timed out. Retrying. --2012-08-02 12:36:56-- (try: 2) http://po-land.pl/index.php

other network - onet.pl

root@HTPC:~# wget -6 ipv6.onet.pl/index.html --2012-08-02 12:38:49-- http://ipv6.onet.pl/index.html Resolving ipv6.onet.pl... 2a02:c10:2190:4::aaaa Connecting to ipv6.onet.pl|2a02:c10:2190:4::aaaa|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 181205 (177K) [text/html] Saving to: `index.html' 100%[===============================================================================================>] 181,205 29.8K/s in 5.8s 2012-08-02 12:38:55 (30.6 KB/s) - `index.html' saved [181205/181205]

Routing PLIX <-> OVH - plwaw01 - ICM

Jeroen Massar SixXS Staff

on Sunday, 05 August 2012 10:40:01

It would be quite useful to have a traceroute from OVH back to your IP, that way one can see if OVH has a proper route or not.

Routing PLIX <-> OVH - plwaw01 - ICM

Shadow Hawkins on Tuesday, 07 August 2012 14:49:26

I did test. When I add route:

ip -r route add 2001:41d0::/32 via ::192.88.99.1 dev tun6to4 metric 1

on 'main' router ( with both sixxs tunnel and tun6to4 ) then on my client station with IP ping to po-land.pl works. Client station IP is 2001:6a0:1e7::3:2:

bash-4.2# ping6 po-land.pl PING po-land.pl (2001:41d0:8:7c5::10): 48 data bytes 56 bytes from 2001:41d0:8:7c5::10: icmp_seq=0 ttl=54 time=44.480 ms 56 bytes from 2001:41d0:8:7c5::10: icmp_seq=1 ttl=54 time=44.429 ms 56 bytes from 2001:41d0:8:7c5::10: icmp_seq=2 ttl=54 time=44.182 ms ^C--- po-land.pl ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 44.182/44.364/44.480/0.130 ms

See on my 'main' router that ping works and goes with SIXXS IP number:

tcpdump -i tun6to4 -n host 2001:41d0:8:7c5::10 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on tun6to4, link-type RAW (Raw IP), capture size 65535 bytes 14:43:52.611878 IP6 2001:6a0:1e7::3:2 > 2001:41d0:8:7c5::10: ICMP6, echo request, seq 0, length 56 14:43:53.613034 IP6 2001:6a0:1e7::3:2 > 2001:41d0:8:7c5::10: ICMP6, echo request, seq 1, length 56 14:43:54.614194 IP6 2001:6a0:1e7::3:2 > 2001:41d0:8:7c5::10: ICMP6, echo request, seq 2, length 56 ^C 3 packets captured

Reply goes by sixxs tunnel:

tcpdump -i sixxs -n host 2001:41d0:8:7c5::10 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on sp2, link-type RAW (Raw IP), capture size 65535 bytes 14:45:17.315314 IP6 2001:41d0:8:7c5::10 > 2001:6a0:1e7::3:2: ICMP6, echo reply, seq 0, length 56 14:45:18.316538 IP6 2001:41d0:8:7c5::10 > 2001:6a0:1e7::3:2: ICMP6, echo reply, seq 1, length 56 14:45:19.317983 IP6 2001:41d0:8:7c5::10 > 2001:6a0:1e7::3:2: ICMP6, echo reply, seq 2, length 56 ^C 3 packets captured

In my opinion OVH has the right route. ukasz Nierycho

Routing PLIX <-> OVH - plwaw01 - ICM

Jeroen Massar SixXS Staff

on Tuesday, 07 August 2012 15:35:22

Client station IP is 2001:6a0:1e7::3:2:

If you are able to transmit from that source address through another host than the SixXS PoP that range is from something is forgetting to do proper source route filtering. And that should especially never happen on a 6to4 relay which should only accept 2002::/16 prefixes.

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