|
XP and weird routing
![[fi]](/s/countries/fi.gif) Carmen Sandiego on Tuesday, 28 October 2003 09:53:00
Seems like my traffic is just taking whatever route it wants in IPv6 environment. I'm using my Linux box as ISATAP router, and it seems to be working fine, but XP is for reasons having two routes. I have IPv4-gateway defined, which is different from IPv6-gateway. I've tried to delete the ::/0 route, but it always comes up again automatically (apparently it's not meant to be deleted).
But this is all I came up with:
netsh interface ipv6>show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
no Autoconf 256 ::/0 4 fe80::210:a7ff:fe02:fe32
no Autoconf 8 2001:960:645::/48 4 Local Area Connection 3
netsh interface ipv6>isatap show router
Relay Name : 130.233.21.101
Use Relay : default
Resolution Interval : default
netsh interface ipv6>6to4 show state
6to4 Service State : disabled
Undo on Service Stop: default
And what happens?
E:\Documents and Settings\michael>ping6 www.6bone.net
Pinging 6bone.net [3ffe:b00:c18:1::10]
from fe80::201:2ff:fedd:908f%4 with 32 bytes of data:
Reply from fe80::210:a7ff:fe02:fe32%4: No route to destination.
Reply from fe80::210:a7ff:fe02:fe32%4: No route to destination.
E:\Documents and Settings\michael>tracert6 www.6bone.net
Tracing route to 6bone.net [3ffe:b00:c18:1::10]
from fe80::201:2ff:fedd:908f%4 over a maximum of 30 hops:
1 fe80::210:a7ff:fe02:fe32%4 reports: No route to destination.
So whoop, why is it trying fe80 address? It seems ISATAP is working, it's getting information and all, but routing isn't using ISATAP. I've tried enabling / disabling network interface, rebooting machine, nothing helps.
What am I missing?-) Microsoft's documents didn't help much, I googled to some other IPv6-sites with instructions, they didn't fix it either.
- Yak
XP and weird routing
Check if there is an RA on the network to which Interface 4 (see "netsh interface ipv6 show address") causes the default gateway to be created. It specifies AutoConf thus it was done with RA's on that interface.
Why use ISATAP btw? Apparently interface 8 has the correct configuration directly.
XP and weird routing
Carmen Sandiego on Tuesday, 28 October 2003 21:23:35
Interface 8 gets it's IP address from ISATAP, that's mostly the reason it gets it right. However I don't know where the interface 4 gets it. Maybe there is one in the network, is there any way to prevent XP from using it, since it's not working?
- Yak
XP and weird routing
Depends on what type of Interface it is.
Type "netsh interface ipv6" and then: "show interface" and "show teredo" and "show state" and other values that show up there. XP has a number of transition mechanisms in place so it can be any one of those.
XP and weird routing
Carmen Sandiego on Thursday, 30 October 2003 13:01:59
Do not show anything new. Interface is normal local are connection, teredo isn't in use, and use state shows this time "default". I've set this to state disabled also, without any help to actual connection.
The following sub-contexts are available:
6to4 isatap
So, no help there either. Under isatap, show router shows only the real one. Show destinationcache tells following:
Interface 4: Local Area Connection 3
PMTU Destination Address Next Hop Address
---- ---------------------------------- ----------------------------------
1500 fe80::201:2ff:fedd:908f fe80::201:2ff:fedd:908f
1500 2001:6e8::1 ::130.233.21.101
1500 3ffe:b00:c18:1::10 fe80::210:a7ff:fe02:fe32
1500 ::130.233.21.101 fe80::210:a7ff:fe02:fe32
Interface 3: 6to4 Tunneling Pseudo-Interface
PMTU Destination Address Next Hop Address
---- ---------------------------------- ----------------------------------
1280 2002:c058:6301::c058:6301 2002:c058:6301::c058:6301
1280 2002:836b:213c::836b:213c 2002:836b:213c::836b:213c
Then again, show neighbors tells something interesting:
Interface 5: Teredo Tunneling Pseudo-Interface
Internet Address Physical Address Type
-------------------------------------------- ----------------- -----------
fe80::54ff:fe55:4e01 02-00-54-55-4e-01 Permanent
Interface 4: Local Area Connection 3
Internet Address Physical Address Type
-------------------------------------------- ----------------- -----------
fe80::201:2ff:fedd:908f 00-01-02-dd-90-8f Permanent
fe80::210:a7ff:fe02:fe32 00-10-a7-02-fe-32 Stale (router)
::130.233.21.101 Incomplete
Interface 3: 6to4 Tunneling Pseudo-Interface
Internet Address Physical Address Type
-------------------------------------------- ----------------- -----------
2002:c058:6301::c058:6301 192.88.99.1 Permanent
2002:836b:213c::836b:213c 131.107.33.60 Permanent
2002:82e9:15ac::82e9:15ac 130.233.21.172 Permanent
Interface 1: Loopback Pseudo-Interface
Internet Address Physical Address Type
-------------------------------------------- ----------------- -----------
fe80::1 Permanent
::1 Permanent
What is this: 2002:82e9:15ac::82e9:15ac ? It points to my IPv4, however it's some XS4ALL TB-service (according to traceroute) ? mm, however.
- Yak
XP and weird routing
1500 fe80::201:2ff:fedd:908f fe80::201:2ff:fedd:908f
Is apparently your local machine and your own machine
is acting as a 6to4 relay. Turn off 6to4 stuff :)
Btw "netsh interface ipv6 show address" and "netsh interface ipv6 show route"
is more interesting
2002:c058:6301::c058:6301 192.88.99.1 Permanent
6to4 anycast relay address
2002:836b:213c::836b:213c 131.107.33.60 Permanent
Default Microsoft 6to4/teredo relay
2002:82e9:15ac::82e9:15ac 130.233.21.172 Permanent
Your own box doing 6to4
What is this: 2002:82e9:15ac::82e9:15ac ? It points to my IPv4, however it's some XS4ALL TB-service (according to traceroute) ? mm, however.
You have 6to4 enabled and all traffic goes over your own box
over 6to4 to the rest of the internet. Where you get XS4all from though...
2002::/16 does go over XS4ALL as they are announcing that prefix.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 28 October 2003 12:26:59
Posting is only allowed when you are