|
IPv6/IPv4 preference issue with WinXP SP3
![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 11 October 2010 16:48:12
Hi,
I'm having a (probably simple) configuration error that makes WinXP SP3 prefer "native IPv4" over "tunneled IPv6" which should not be the case as far as I understood.
When connecting to https://www.sixxs.net, IPv4 will be used always.
When connecting to https://www.ipv6.sixxs.net explicitly, the connection works fine (no delays), but the website states I'm connecting from the IPv6 address of my tunnel endpoint (and not one of the global IPv6 addresses assigned to the "LAN connection").
Obviously the "tunnel adapter" is preferred over the "LAN connection" when IPv6 is "forced"... but IPv4 is preferred if both protocols are available.
Any hints where to search for the configuration error? Which config details would be helpful to track down the issue?
Regards,
Wolfgang
IPv6/IPv4 preference issue with WinXP SP3
See that big orange box when posting, it points to a 'reporting problems checklist' on the contact page, please provide those details.
In this case you will also want to tell the browser you are using and check if that browser has IPv6 support and if that support is not disabled.
IPv6/IPv4 preference issue with WinXP SP3
Shadow Hawkins on Tuesday, 12 October 2010 19:43:32
Hi Jeroen,
- Tunnel/Subnet ID are T8076/R5732
- AICCU is run to setup the heartbeat tunnel on WinXP SP3 (clock is sync)
- WinXP SP3 laptop is behind a NAT router (AVM FritzBox 7170)
- local BIND DNS server (recursive, supporting IPv6 and working without problems)
- no radvd or something, computer has two global IPv6 addresses (EUI-64 and an additional "static" one, that does not depend on the MAC address)
- interfaces:
Idx Met MTU Status Name
--- ---- ----- ------------ -----
10 0 1500 Verbunden LAN-Verbindung
8 1 1280 Verbunden aiccu
6 2 1280 Getrennt Teredo Tunneling Pseudo-Interface
5 0 1500 Getrennt Drahtlose Netzwerkverbindung
3 1 1280 Verbunden 6to4 Pseudo-Interface
2 1 1280 Verbunden Automatic Tunneling Pseudo-Interface
1 0 1500 Verbunden Loopback Pseudo-Interface
- ipconfig:
Ethernetadapter LAN-Verbindung:
Verbindungsspezifisches DNS-Suffix: fritz.box
Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physikalische Adresse . . . . . . : 00-D0-59-83-4A-D5
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IP-Adresse. . . . . . . . . . . . : 192.168.0.151
Subnetzmaske. . . . . . . . . . . : 255.255.0.0
IP-Adresse. . . . . . . . . . . . : 2001:6f8:114f:0:2d0:59ff:fe83:ead5
IP-Adresse. . . . . . . . . . . . : 2001:6f8:114f::1
IP-Adresse. . . . . . . . . . . . : fe80::2d0:59ff:fe83:4ad5%10
Standardgateway . . . . . . . . . : 192.168.0.254
DHCP-Server . . . . . . . . . . . : 192.168.0.254
DNS-Server. . . . . . . . . . . . : 192.168.0.151
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
Tunneladapter aiccu:
Verbindungsspezifisches DNS-Suffix: fritz.box
Beschreibung. . . . . . . . . . . : Configured Tunnel Interface
Physikalische Adresse . . . . . . : C0-A8-00-97
DHCP aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 2001:6f8:900:5cf::2
IP-Adresse. . . . . . . . . . . . : fe80::8:c0a8:97%8
Standardgateway . . . . . . . . . : 2001:6f8:900:5cf::1
DNS-Server. . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
NetBIOS ber TCP/IP . . . . . . . : Deaktiviert
- IPv6 Routes
Verff. Typ Met Prfix Idx Gateway/Schnittstelle
------- -------- ---- ------------------------ --- ---------------------
yes Manuell 1 ::/0 8 2001:6f8:900:5cf::1
no Manuell 1 ::/0 8 aiccu
no Manuell 11 2001:6f8:900:5cf::/64 8 2001:6f8:900:5cf::1
yes Manuell 1 2001:6f8:114f::/64 10 LAN-Verbindung
- IPv6 firewalling is currently disabled
- Route trace to PoP with IPv4
Routenverfolgung zu deham01.sixxs.net [212.224.0.188] ber maximal 30 Abschnitt
e:
1 <1 ms <1 ms <1 ms 192.168.0.254
2 13 ms 7 ms 7 ms dslb-084-057-064-001.pools.arcor-ip.net [84.57.6
4.1]
3 8 ms 8 ms 8 ms nbg-145-254-7-101.arcor-ip.net [145.254.7.101]
4 17 ms 18 ms 26 ms 92.79.213.122
5 19 ms 18 ms 19 ms te0-0-0-5.er10.ixfra.de.easynet.net [80.81.192.1
4]
6 22 ms 21 ms 23 ms te0-1-0.gr11.isham.de.easynet.net [87.86.77.80]
7 22 ms 50 ms 23 ms ge3-8.br3.isham.de.easynet.net [87.86.71.253]
8 22 ms 21 ms 21 ms ge9-15.cr20.isham.de.easynet.net [212.224.4.93]
9 34 ms 32 ms 21 ms deham01.sixxs.net [212.224.0.188]
- Route trace to PoP with IPv6
Routenverfolgung zu deham01.sixxs.net [2001:6f8:800:1003::2] ber maximal 30 Ab
schnitte:
1 23 ms 23 ms 23 ms deham01.sixxs.net [2001:6f8:800:1003::2]
Ablaufverfolgung beendet.
- Used browsers are MS IE8 and Mozilla FireFox 3.6.10, both have IPv6 enabled
As I already stated, IPv6 works in both browsers for IPv6 only pages (e.g. http://v6.testmyipv6.com/) ... but for pages supporting both protocols IPv4 is used, e.g. http://testmyipv6.com/.
Any ideas what might be wrong?
Regards,
Wolfgang
IPv6/IPv4 preference issue with WinXP SP3
Shadow Hawkins on Wednesday, 13 October 2010 11:30:31
Hi,
got the IPv4/IPv6 prefererence problem fixed... just misunderstood the "precedence" value of the prefixpolicy: greater numbers mean *higher* (not lower) priority (found nothing about that high-to-low-ordering on the Microsoft pages)
I'm still curious about the source address selection, i.e. on the machine where the tunnel is configured, I can't get the EUI-64 address of the subnet to be used.
Is there no way to make Windows use the subnet address configured for the "LAN connection"... then forward the packet to the aiccu interface and then route it over the tunnel with source address still being my EUI-64 address which also resolves correctly via reverse DNS?
I played around with several route configurations with 3 possible results:
1. tunnel endpoint address off aiccu interface is selected always (as stated in the original post)
2. EUI-64 address is used... but "no route to host" when pinging externel IPv6 addresses
3. EUI-64 address is used *once* when pinging which also results in "no route to host", then kind of fallback to the tunnel endpoint address on the aiccu interface
Regards,
Wolfgang
IPv6/IPv4 preference issue with WinXP SP3
If you would have mentioned that you had been changing the prefixpolicy, then my questions would have been completely different.... now it is: why change them?
I'm still curious about the source address selection, i.e. on the machine where the tunnel is configured, I can't get the EUI-64 address of the subnet to be used.
Windows does not support source address selection through policy mechanisms.
IPv6/IPv4 preference issue with WinXP SP3
Shadow Hawkins on Thursday, 14 October 2010 17:37:02
The change in the prefixpolicy was a "try" to get the IPv6 address of the "LAN connection" used as source address instead of the tunnel endpoint address of the aiccu interface... and this indeed broke the IPv6 over IPv4 precedence.
Windows does not support source address selection through policy mechanisms.
So does this mean source address selection is generally not supported in Windows... or are there any other mechanisms apart from the policy?
I think I shall get this finally fixed when upgrading my AVM FritzBox 7170 to a 7390 which provides support for the SixXS tunnel integrated on the NAT router.
Then the Windows client will no longer be the tunnel endpoint and only have one global IPv6 address.
Nevertheless I'd like to know if there's any solution for this address selection problem with Windows.
Regards,
Wolfgang
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 12 October 2010 17:32:46
Posting is only allowed when you are