forum.mikrotik.com unreachable

[fwindt]

Hi,

I am in Las Vegas on an HE IPv6 tunnel. I am timing out reaching forum.mikrotik.com on its AAAA record.

The odd thing is that from my home I am timing out in Frankfurt, and so is a traceroute sent from the LA HE router. However, a traceroute from Frankfurt works just fine.

Code Select Expand

$ traceroute6 forum.mikrotik.com
traceroute6 to forum.mikrotik.com (2a02:610:7501:1000::201) from 2001:470:f037:1:64a5:688c:fd18:1c02, 64 hops max, 12 byte packets
1  2001:470:f037:1::1  2.038 ms  0.653 ms  0.519 ms
2  fwindt-1.tunnel.tserv15.lax1.ipv6.he.net  34.758 ms  24.669 ms  20.860 ms
3  gige-g4-6.core1.lax1.he.net  23.012 ms  16.327 ms  23.436 ms
4  10gigabitethernet4-3.core1.nyc4.he.net  85.279 ms  77.992 ms  80.870 ms
5  10gigabitethernet3-3.core1.lon1.he.net  145.930 ms  145.156 ms  146.613 ms
6  10gigabitethernet4-2.core1.fra1.he.net  155.722 ms  154.766 ms  165.712 ms
7  * * *
8  * * *
9  * * *
10  * * *
11  * * *
12  * * *
^C

Code Select Expand

core1.lax2.he.net> traceroute ipv6 2a02:610:7501:1000::201 numeric
Target 2a02:610:7501:1000::201
Hop Start 1
Hop End 30
Hop Packet 1 Packet 2 Packet 3 Hostname
1 <1 ms <1 ms <1 ms 10gigabitethernet2-1.core1.lax1.he.net (2001:470:0:72::1)
2 66 ms 61 ms 63 ms 10gigabitethernet4-3.core1.nyc4.he.net (2001:470:0:10e::2)
3 143 ms 183 ms 144 ms 10gigabitethernet3-3.core1.lon1.he.net (2001:470:0:128::2)
4 155 ms 148 ms 152 ms 10gigabitethernet4-2.core1.fra1.he.net (2001:470:0:1d2::2)
5 * * * ?
6 * * * ?
7 * * * ?
8 * * * ?
IP: Errno(8) Trace Route Failed, no response from target node.

Code Select Expand

core1.fra1.he.net> traceroute ipv6 2a02:610:7501:1000::201 numeric
Target 2a02:610:7501:1000::201
Hop Start 1
Hop End 30
Hop Packet 1 Packet 2 Packet 3 Hostname
1 35 ms 43 ms 35 ms decix-te5-5.38.vln.globalcom.lv (2001:7f8::a7e3:0:1)
2 53 ms 49 ms 50 ms 2a02:610:ffff:1800::2
3 49 ms 50 ms 50 ms latnet.tv.riga.globalcom.lv (2a02:610:ffff:1003::2)
4 42 ms 48 ms 53 ms titan-gw.v53.ls.lv (2a02:610:7500::1)
5 55 ms 51 ms 52 ms 2a02:610:7500:8::2
6 45 ms 49 ms 50 ms 2a02:610:7500:9::2
7 46 ms 64 ms 50 ms 2a02:610:7501:1000::1
8 49 ms 50 ms 49 ms 2a02:610:7501:1000::201

Any idea what's going on?

Thanks,
Felix

[cholzhauer]

I have the same problem from a Chicago tunnel.

Email ipv6@he.net and alert them to it.

[fwindt]

Email sent, appreciate the answer.

[broquea]

Contacted and opened a ticket with the peer that advertises that downstream network. Seems to be some sort of return path issue when sourcing from our /32 but not from the DECIX IP (which is what it does when tracing on the router). Waiting on a reply from them.