|
My subnet not reachable from teredo
![[pt]](/s/countries/pt.gif) Shadow Hawkins on Tuesday, 29 March 2011 11:43:39
Hi,
I have a routing problem. I don't know if there's anything that can be done about it. My subnet has been working for a few weeks, I have some traffic with other unrelated entities, such as mail servers, etc.
However, I can't reach my subnet from the Windows teredo interface. When I try to ping my subnet from there I get a "No route to host" type error. When I try to traceroute from my subnet to the teredo interface, it stops halfway...
Here's my traceroute from teredo to www.kame.net:
C:\>tracert -6 www.kame.net
Tracing route to orange.kame.net [2001:200:dff:fff1:216:3eff:feb1:44d7]
over a maximum of 30 hops:
1 * 304 ms 303 ms 2001:200:0:b003::2
2 303 ms 309 ms 305 ms 2001:200:0:b003::1
3 307 ms 310 ms 307 ms 2001:200:0:fe00::9c4:11
4 305 ms 306 ms 307 ms 2001:200:0:1802:20c:dbff:fe1f:7200
5 305 ms 310 ms 305 ms ve42.foundry4.nezu.wide.ad.jp [2001:200:0:11::66
]
6 305 ms 305 ms 305 ms cloud-net1.wide.ad.jp [2001:200:0:1c0a:218:8bff:
fe43:d1d0]
7 315 ms 315 ms 313 ms 2001:200:dff:fff1:216:3eff:feb1:44d7
Trace complete.
Here's my traceroute from my subnet to www.kame.net:
~> traceroute6 -I www.kame.net traceroute6 to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001:b18:4071:0:960c:6dff:fe80:c03f, 64 hops max, 16 byte packets
1 airport 0.389 ms 0.246 ms 0.459 ms
2 gw-206.lis-01.pt.sixxs.net 19.252 ms 14.516 ms 15.714 ms
3 2001:b18:0:1000::1 16.845 ms 34.092 ms 24.882 ms
4 adm-ipv6-link.telia.net 27.085 ms 34.423 ms 27.804 ms
5 verio-ic-141746-mad-b2.c.telia.net 55.332 ms 152.232 ms 218.106 ms
6 xe-3-2.r02.mdrdsp01.es.bb.gin.ntt.net 180.259 ms 37.132 ms 210.713 ms
7 ae-3.r23.londen03.uk.bb.gin.ntt.net 54.193 ms 52.638 ms 51.283 ms
8 as-0.r22.osakjp01.jp.bb.gin.ntt.net 318.447 ms 367.172 ms 318.569 ms
9 ae-5.r24.tokyjp01.jp.bb.gin.ntt.net 329.296 ms 325.874 ms 331.829 ms
10 po-1.a15.tokyjp01.jp.ra.gin.ntt.net 290.583 ms 293.258 ms 302.565 ms
11 ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net 363.508 ms 361.310 ms 365.533 ms
12 ve44.foundry6.otemachi.wide.ad.jp 361.380 ms 379.922 ms 369.348 ms
13 ve42.foundry4.nezu.wide.ad.jp 359.660 ms 355.949 ms 359.052 ms
14 cloud-net1.wide.ad.jp 366.097 ms 370.660 ms 357.057 ms
15 2001:200:dff:fff1:216:3eff:feb1:44d7 365.097 ms 377.085 ms 366.382 ms
Now, here's the traceroute that fails from teredo to my subnet:
C:\>tracert -6 satan.miguel.ramos.name
Tracing route to satan.miguel.ramos.name [2001:b18:4071:0:960c:6dff:fe80:c03f]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * ^C
And here's the traceroute from my subnet to the teredo interface address.
~> traceroute6 -I 2001:0:5ef5:79fd:24ec:3984:a64b:513b traceroute6 to 2001:0:5ef5:79fd:24ec:3984:a64b:513b (2001:0:5ef5:79fd:24ec:3984:a64b:513b) from 2001:b18:4071:0:960c:6dff:fe80:c03f, 64 hops max, 16 byte packets
1 airport 0.412 ms 0.223 ms 0.449 ms
2 gw-206.lis-01.pt.sixxs.net 17.720 ms 27.710 ms 16.974 ms
3 2001:b18:0:1000::1 23.725 ms 16.011 ms 16.089 ms
4 FCCN.IPv6.GigaPix.pt 16.062 ms 17.816 ms
FCCN.IPv6.GigaPix.pt 16.420 ms
5 ROUTER23.IPv6.GE.Lisboa.fccn.pt 15.663 ms 16.355 ms 16.033 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 *^C
So, I get the feeling that it's not a problem at the routing tables of the leaf nodes.
Finally, here's the output of,
C:\>netsh int ipv6 show int
Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
1 50 4294967295 connected Loopback Pseudo-Interface 1
12 50 1280 disconnected isatap.albatroz
13 50 1280 connected Teredo Tunneling Pseudo-Interface
11 10 1500 connected Local Area Connection
16 50 1280 disconnected isatap.{48564D60-789B-4CE8-B788-9017E
7BD78AA}
18 20 1500 connected VirtualBox Host-Only Network
C:\>netsh int ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
No Manual 8 ::/0 13 Teredo Tunneling Pseudo-I
nterface
No Manual 256 ::1/128 1 Loopback Pseudo-Interface
1
No Manual 8 2001::/32 13 Teredo Tunneling Pseudo-I
nterface
No Manual 256 2001:0:5ef5:79fd:24ec:3984:a64b:513b/128 13 Teredo Tu
nneling Pseudo-Interface
No Manual 256 fe80::/64 18 VirtualBox Host-Only Netw
ork
No Manual 256 fe80::/64 11 Local Area Connection
No Manual 256 fe80::/64 13 Teredo Tunneling Pseudo-I
nterface
No Manual 256 fe80::5efe:192.168.1.103/128 12 isatap.albatroz
No Manual 256 fe80::5efe:192.168.56.1/128 16 isatap.{48564D60-789B-
4CE8-B788-9017E7BD78AA}
No Manual 256 fe80::20a5:806b:a803:1c9e/128 18 VirtualBox Host-Only
Network
No Manual 256 fe80::24ec:3984:a64b:513b/128 13 Teredo Tunneling Pse
udo-Interface
No Manual 256 fe80::587a:b613:3ef1:f47a/128 11 Local Area Connectio
n
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface
1
No Manual 256 ff00::/8 13 Teredo Tunneling Pseudo-I
nterface
No Manual 256 ff00::/8 18 VirtualBox Host-Only Netw
ork
No Manual 256 ff00::/8 11 Local Area Connection
Thanks for any help.
My subnet not reachable from teredo
Tracing route to orange.kame.net [2001:200:dff:fff1:216:3eff:feb1:44d7] over a maximum of 30 hops: 1 * 304 ms 303 ms 2001:200:0:b003::2 2 303 ms 309 ms 305 ms 2001:200:0:b003::1 [..]
So you are located in Portugal and using a Teredo first hop somewhere in the WIDE network in Japan.... *ouch*
I suggest that if you really need to use Teredo that you at least use a local, eg European-based, relay.
Better solution of course is to use an AYIYA tunnel.
My subnet not reachable from teredo
Shadow Hawkins on Wednesday, 30 March 2011 10:59:15
The only point about using Teredo is requiring no configuration... or so I thought. I only use this in networks where I don't want to have a big impact.
I guess I'll have to find out more about how this thing can be configured.
Thanks,
My subnet not reachable from teredo
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Friday, 01 April 2011 14:08:07
It looks like the teredo-relay closest to your network is broken.
You can find where it is tracing any teredo address (2001:0:....)
Unfortunately there is not much you can do with it unless you can setup teredo relay which will be closer to your network than that broken one (maybe your sixxs provider could set up one?).
There is a free teredo-relay software - google for miredo. It is available for linux and freebsd.
My subnet not reachable from teredo
Shadow Hawkins on Friday, 01 April 2011 13:55:52So you are located in Portugal and using a Teredo first hop somewhere in the WIDE network in Japan.... *ouch*
And this is just like it is supposed to work. Teredo client has found the teredo relay near to the server it is connecting to. orange.kame.net is in wide.ad.jp.
BTW, it works for me:
tracert orange.kame.net [2001:200:dff:fff1:216:3eff:feb1:44d7]
1 640 ms 320 ms 323 ms 2001:200:0:b003::2
2 319 ms 319 ms 320 ms 2001:200:0:b003::1
3 324 ms 321 ms 323 ms 2001:200:0:fe00::9c4:11
4 320 ms 319 ms 319 ms 2001:200:0:1802:20c:dbff:fe1f:7200
5 320 ms 320 ms 320 ms ve42.foundry4.nezu.wide.ad.jp [2001:200:0:11::66]
6 325 ms 319 ms 327 ms cloud-net1.wide.ad.jp [2001:200:0:1c0a:218:8bff:fe43:d1d0]
7 329 ms 329 ms 330 ms 2001:200:dff:fff1:216:3eff:feb1:44d7
Jacek
My subnet not reachable from teredo
Shadow Hawkins on Friday, 01 April 2011 14:10:51
I mean it works for me the same way - it finds the same teredo-relay (as it should) and I'm far from Portugal.
My subnet not reachable from teredo
That is not how it is "supposed" to work. One sends IPv6 inside IPv4 packets (teredo style) to their *CLOSEST* relay, and hopefully such a box is still in Europe not on the other side of the globe. As such the first hop will be that relays IPv6 address and then a full route of hops to Japan.
One can configure Teredo servers, and based on which server you select that server will tell you which relay to use, which hopefully is close to you IPv4 wise.
It seems to me that currently there are very few Teredo relays online when you end up in Japan for one.
My subnet not reachable from teredo
Shadow Hawkins on Saturday, 02 April 2011 21:27:02
I can't agree. Teredo-relay is selected based on destination address (ipv6 echo request is sent to the server, server responds with echo reply, that answer reaches teredo-relay which will be used for 2 way communication with the given server).
So when client connect to three different servers it can use three different teredo-relays.
This is just the opposite to 6to4 tunneling.
http://en.wikipedia.org/wiki/Teredo_tunneling#Relays
Any teredo-client in the world will use my reredo-relay to communicate with my ipv6 servers - try for example clamavmirror.ipartners.pl - traffic will go through teredo-relay.ipartners.pl.
Three traceroutes from the same teredo-client - please note that teredo-relay is close to destination, not source:
Tracing route to clamavmirror.ipartners.pl [2001:4190:8002:1::1:301]
over a maximum of 30 hops:
1 295 ms 8 ms 8 ms teredo-relay.ipartners.pl [2001:4190:8002:1::402]
2 8 ms 8 ms 9 ms 2001:4190:8002:1::401
3 10 ms 9 ms 9 ms clamavmirror.ipartners.pl [2001:4190:8002:1::1:301]
Tracing route to red.freebsd.org [2001:4f8:fff6::22]
over a maximum of 30 hops:
1 404 ms 185 ms 185 ms 6to4.fmt2.he.net [2001:470:0:108::2]
2 192 ms 185 ms 188 ms gige-g5-20.core1.fmt2.he.net [2001:470:0:108::1]
3 201 ms 189 ms 187 ms 10gigabitethernet1-2.core1.pao1.he.net [2001:470:0:30::2]
4 188 ms 193 ms 190 ms he.pao1.isc.org [2001:470:0:38::2]
5 187 ms 186 ms 186 ms gig-2-1-0.r7.pao1.isc.org [2001:4f8:0:1::50:2]
6 187 ms 187 ms 187 ms ipv6gw-isc.freebsd.org [2001:4f8:0:1::3e:2]
7 187 ms 187 ms 187 ms red.freebsd.org [2001:4f8:fff6::22]
Tracing route to www.ipv6.ie [2001:770:18:7::c101:1f72]
over a maximum of 30 hops:
1 56 ms 56 ms 58 ms 2a02:278:8::6:5501
2 58 ms 57 ms * qp1.mve.gal.core.airwire.ie [2a02:278:8::251]
3 57 ms 57 ms 57 ms qp2.mve.gal.core.airwire.ie [2a02:278:8::254]
4 66 ms 69 ms 67 ms te0-0-0-1-cr2-cwt.hea.net [2001:7f8:18::1:0:1]
5 67 ms 67 ms 66 ms te0-4-0-0-cr2-pw.hea.net [2001:770:400:34::2]
6 66 ms 66 ms 66 ms te5-1-blanch-sr2.services.hea.net [2001:770:90:60::2]
7 65 ms 66 ms 66 ms magellan.tssg.org [2001:770:18:7::c101:1f72]
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 29 March 2011 15:29:33
Posting is only allowed when you are