Discussion:
IPv6 traceroute weirdness
(too old to reply)
ElChino
2018-08-14 12:22:37 UTC
Permalink
Hello group.

I now have IPv6 connection to the net. But I'm only able
to get a proper stable WAN/IPv6 connection via '6to4'.
I tried 'SLAAC/DHCPv6' and got a connect, but it got
a "disconnect" after approx. 20 min. And my router (a
Trendnet TEW-824DRU) seems to have an auto-fallback to
'6to4'.

From the router-status, I see it uses '2001:4600:4:1fff::'
as the DNSv6-server. Located in Oslo/Norway.

Here is the strange part in this '6to4' tunneling scheme.
A 'c:\Windows\system32\tracert.exe -6 2001:4600:4:1fff::' shows
these long hops:

Tracing route to 2001:4600:4:1fff:: over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 2002:6dbd:2078:1::1
2 41 ms 42 ms 43 ms 2002:c058:6301::1
3 70 ms 43 ms 67 ms ve210.core1.ams1.he.net [2001:470:0:24f::1]
4 43 ms 43 ms 43 ms ti9000b400.ti.telenor.net [2001:7f8:1::a500:2119:1]
5 65 ms 64 ms 65 ms ti3004c400-lo0-0.ti.telenor.net [2001:4600:0:100::5]
6 67 ms 75 ms 64 ms ti0001c360-lo0-0.ti.telenor.net [2001:4600:0:100::23]
7 66 ms 65 ms 63 ms ti0300b400-lo0-0.ti.telenor.net [2001:4600::e]
8 65 ms 65 ms 66 ms sf-o-d-6.ti.telenor.net [2001:4600:10::ae]
9 64 ms 64 ms 73 ms tix96c01-ec6-v100.tix.telenor.net [2001:4600:4:f000::c1]
10 65 ms 69 ms 65 ms tix95d02-ec4-v100.tix.telenor.net [2001:4600:4:f000::a2]
11 65 ms 65 ms 65 ms tix95d01-ec1-v100.tix.telenor.net [2001:4600:4:f000::91]
12 66 ms 65 ms 65 ms tix95a01-ec7-v100.tix.telenor.net [2001:4600:4:f000::112]
13 66 ms 66 ms 85 ms 2001:4600:4:f000::95:a2
14 64 ms 65 ms 64 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94]
15 66 ms 74 ms 65 ms tnxe95c01-v11.tnx.telenor.net [2001:4600:4:f000::95:92]
16 65 ms 65 ms 65 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94] == hop 14
17 66 ms 66 ms 72 ms tnxe95c01-v11.tnx.telenor.net [2001:4600:4:f000::95:92]
18 66 ms 123 ms 68 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94] == hop 14
19 66 ms 71 ms 66 ms tnxe95c01-v11.tnx.telenor.net [2001:4600:4:f000::95:92]
20 68 ms 102 ms 66 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94] == hop 14
21 69 ms 66 ms 69 ms tnxe95c01-v11.tnx.telenor.net [2001:4600:4:f000::95:92]
22 66 ms 78 ms 65 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94] == hop 14
23 66 ms 67 ms 70 ms tnxe95c01-v11.tnx.telenor.net [2001:4600:4:f000::95:92]
24 67 ms 66 ms 66 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94] == hop 14
25 69 ms 67 ms 67 ms tnxe95c01-v11.tnx.telenor.net [2001:4600:4:f000::95:92]
26 67 ms 82 ms 68 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94] == hop 14
27 77 ms 69 ms 68 ms tnxe95c01-v11.tnx.telenor.net [2001:4600:4:f000::95:92]
28 69 ms 68 ms 68 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94] == hop 14
29 113 ms 69 ms 70 ms tnxe95c01-v11.tnx.telenor.net [2001:4600:4:f000::95:92]
30 68 ms 69 ms 69 ms fw-z1-95-exp1-v11.tnx.telenor.net [2001:4600:4:f000::95:94] == hop 14

---------

Using data from GeoIP and IP2Location data-bases, I figured the
location of hop 3 is in "United States (Fremont/California)" !!

Hop 4 is 'Holland, Amsterdam'.
Hop 5 and higher are all 'Norway, Oslo'.

And what's up with all the nodes at hop 16, 18,..30?
My Windows tracert program gave up after 30 hops.

Who can I blame this strangeness on? Windows-10, my ISP or
my router/PC settings?

I briefly read something about 'IPv6 tunnel brokering'. Would
that be a fix for this case?
Ivan Shmakov
2018-08-16 14:07:45 UTC
Permalink
I now have IPv6 connection to the net. But I'm only able to get a
proper stable WAN/IPv6 connection via '6to4'. I tried 'SLAAC/DHCPv6'
and got a connect, but it got a "disconnect" after approx. 20 min.
What do you mean by "disconnect" here? Can you run something
like "ip addr" command on the router before and after
"disconnect" and show the results (with your IPv6 address
removed for privacy if necessary) here?
And my router (a Trendnet TEW-824DRU) seems to have an auto-fallback
to '6to4'.
Can you try SLAAC /without/ DHCPv6? May also make sense to
disable the 6to4 fallback.

The problem with 6to4 is that successful datagram delivery tends
to depend on the parties that you'd be surprised to find involved.

[...]
Using data from GeoIP and IP2Location data-bases, I figured the
location of hop 3 is in "United States (Fremont/California)" !!
Yep, just like that.

[...]
Who can I blame this strangeness on? Windows-10, my ISP or my
router/PC settings?
I don't think I can readily comment on the "traceroute" issue, alas.
I briefly read something about 'IPv6 tunnel brokering'. Would that be
a fix for this case?
It's possible to request IPv6 network allocation and forwarding
(tunneling) from a third party via http://tunnelbroker.net/
(if you have a static and publicly-routable IPv4 address) or
http://sixxs.net/. Indeed, you can use that instead of your
ISP-provided IPv6 at the cost of higher latency.
--
FSF associate member #7257 np. Undivided Horizons -- HMage
Jorgen Grahn
2018-08-16 14:36:17 UTC
Permalink
...
Post by Ivan Shmakov
I briefly read something about 'IPv6 tunnel brokering'. Would that be
a fix for this case?
It's possible to request IPv6 network allocation and forwarding
(tunneling) from a third party via http://tunnelbroker.net/
(if you have a static and publicly-routable IPv4 address) or
http://sixxs.net/. Indeed, you can use that instead of your
ISP-provided IPv6 at the cost of higher latency.
YMMV (depending on where the tunnel ends and so on) but I use such a
tunnel and the latency cost is not noticeable.

OTOH, if the OP pays for decent IPv6, he should get it. (I'm not quite
sure /what/ he got, since I'm only familiar with the local aspect of
IPv6.)

/Jorgen
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
Ivan Shmakov
2018-08-16 15:05:53 UTC
Permalink
Post by Jorgen Grahn
Post by Ivan Shmakov
I briefly read something about 'IPv6 tunnel brokering'. Would
that be a fix for this case?
It's possible to request IPv6 network allocation and forwarding
(tunneling) from a third party via http://tunnelbroker.net/
(if you have a static and publicly-routable IPv4 address) or
http://sixxs.net/. Indeed, you can use that instead of your
ISP-provided IPv6 at the cost of higher latency.
YMMV (depending on where the tunnel ends and so on) but I use such
a tunnel and the latency cost is not noticeable.
I certainly don't care about the one I'm getting, either.

But then again, I mainly use Tor for HTTP(S) anyway.
Post by Jorgen Grahn
OTOH, if the OP pays for decent IPv6, he should get it.
Seconded.
Post by Jorgen Grahn
(I'm not quite sure /what/ he got,
Neither am I.
Post by Jorgen Grahn
since I'm only familiar with the local aspect of IPv6.)
--
FSF associate member #7257 np. The Book of Souls -- Iron Maiden
ElChino
2018-08-18 14:33:13 UTC
Permalink
Post by Ivan Shmakov
Post by Jorgen Grahn
OTOH, if the OP pays for decent IPv6, he should get it.
Seconded.
Post by Jorgen Grahn
(I'm not quite sure /what/ he got,
Neither am I.
And neither am I really. I've tried 2 times to contact my
ISP support w/o success. Clueless as to what they're selling.
They only refer me to Telenor's hotline call-centre which cost
approx US$ 4 per. minute!

Testing against 'http://test-ipv6.com', it reports:
You appear to be using a public 6to4 gateway; your router may be
providing this to you automatically. Such public gateways have
no service level agreements; you may see performance problems
using such. Better would be to get a native IPv6 address from
your ISP.

My router (under "Advanced | Setup | IPv6 Settings"), these options
are listed::
Static
Autoconfiguration (SLAAC/DHCPv6)
Link-local only
PPPoE
6to4

No way AFAICS to specify SLAAC without DHCPv6 (stateful).

A "Connect" on "6to4" works fine, except the latency I mentioned
is 4 times higher that IPv4 to the same site. From the traceroute
output:
1 <1 ms <1 ms <1 ms 2002:6dbd:2078:1::1
2 41 ms 42 ms 43 ms 2002:c058:6301::1

these '6dbd:2078' + 'c058:6301' 32-bits are the '6to4' IPv-4
addresses for hop 1 and 2, as far I understand.

BTW, I've been using dd-Wrt for several years on my old
router. So I'm inclined to install dd-Wrt on this new
router pretty soon.

Thanks guys for answering.

Loading...