|
Win7 Teredo to AICCU tunnel does not work
![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 21 December 2009 21:27:02
Hi,
I configured an AICCU tunnel on a Fritzbox 7170 to get a IPv6 subnet in my home LAN. Everything seems to be working.
I am using some Windows 7 clients and opened the firewalls for testing purposes - just to make sure nothing is blocked here.
I installed IIS on one of the machines, the default web page is accessible from all clients in the network, also by using the IPv6 address of the "server".
I tried www.subnetonline.com to do a IPv6 ping and a port scan on port 80 to the destination server - this was successful, too.
I even installed Network Monitor and can see subnetonline accessing my host.
Thats everything so far for the setup.
Now I used a different Windows 7 laptop with a UMTS adapter and try to access my server. I want to use the builtin Teredo, so that I do not have to install any additional software.
I can ping -6 different hosts like www.six.heise.de, www.kame.net etc ... everything seems to be successful. Browsing using IP addresses work, too.
Unfortunately I cant access my hosts behind the AICCU tunnel. In the Network Monitor I can see pings coming in and replies going out, but nothing else happens. The pings seem to be the Teredo pings which are used to determine the nearest relay, but nothing else happens here.
Any ideas? Is Teredo <-> AICCU not supported? Any problems here?
TIA
M.
Win7 Teredo to AICCU tunnel does not work
Any ideas? Is Teredo <-> AICCU not supported? Any problems here?
First a little note: "AICCU" is a program which sets up either a proto-41 (+ optionally heartbeat) or an AYIYA tunnel.
Teredo uses 2001::/32 address space, the tunnels provided by AICCU the address space provided by the PoP. As it is all IPv6 one should be able to get from either to either, as long as there is a route and the MTU and other such things are okay.
Thus first thing you do when you have a problem: traceroute.
As you are on windows: tracert -6 <other host>
When that works, then try: telnet <other host> 80
(though, that you can also try first, you'll notice that it won't work and then can try the traceroute to check if you at least have a route :)
That you can "ping" something doesn't mean much, especially if the source address is broken, and even more so if you are not using the route that you intended to use, thus check your source address...
Win7 Teredo to AICCU tunnel does not work
Shadow Hawkins on Tuesday, 22 December 2009 07:27:36
Sorry, you are of course right. AICCU should be replaced with AYIYA. The traceroute return nothing, i.e. only *, nothing more. When I traceroute to other IPs, it return, what it should return. The routing table seems to be ok as well, theres nothing unusual in there.
Win7 Teredo to AICCU tunnel does not work
The traceroute return nothing, i.e. only *, nothing more.
Traceroute from where to where? Please be way more specific.
When I traceroute to other IPs, it return, what it should return.
Show it :) Can't help you without data.
The routing table seems to be ok as well, theres nothing unusual in there.
You think there is nothing unusual, but show them, and lets find out.
The output of:
netsh int ipv6 show int
netsh int ipv6 show route
ipconfig /all
is a good start
Win7 Teredo to AICCU tunnel does not work
Shadow Hawkins on Tuesday, 22 December 2009 21:06:29
Hi,
ok - first the output from the Teredo client
C:\Windows\system32>netsh int ipv6 show int
Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
1 50 4294967295 connected Loopback Pseudo-Interface 1
12 20 1500 disconnected Wireless Network Connection
20 20 1500 disconnected Wireless Network Connection 2
22 50 1280 disconnected isatap.{D3DD92E6-FB16-4308-A921-C3D87
821A3B2}
13 50 1280 disconnected isatap.{07DA211B-FA1A-42C9-A621-F5D3B
EA59952}
11 10 1500 disconnected Local Area Connection
23 50 1280 disconnected isatap.{E1B70C2B-BED7-4FF3-9908-19392
1E9F32E}
19 50 1280 disconnected isatap.{CD28AAE0-CED9-4D4D-9B8F-1F2DD
CED6C16}
24 50 1280 disconnected isatap.{2FF30786-BF4D-40F0-9173-141A8
2037AA7}
44 50 1280 connected Teredo Tunneling Pseudo-Interface
15 50 1500 disconnected Bluetooth Network Connection
45 50 1280 disconnected isatap.{4BE8D97C-3967-4100-9018-6D712
4908E09}
18 20 1500 connected VirtualBox Host-Only Network
C:\Windows\system32>netsh int ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
No Manual 8 ::/0 44 Teredo Tunneling Pseudo-I
nterface
No Manual 256 ::1/128 1 Loopback Pseudo-Interface
1
No Manual 8 2001::/32 44 Teredo Tunneling Pseudo-I
nterface
No Manual 256 2001:0:53aa:64c:3cf2:4b46:af44:9c54/128 44 Teredo Tun
neling Pseudo-Interface
No Manual 256 fe80::/64 18 VirtualBox Host-Only Netw
ork
No Manual 256 fe80::/64 12 Wireless Network Connecti
on
No Manual 256 fe80::/64 11 Local Area Connection
No Manual 256 fe80::/64 20 Wireless Network Connecti
on 2
No Manual 256 fe80::/64 15 Bluetooth Network Connect
ion
No Manual 256 fe80::/64 44 Teredo Tunneling Pseudo-I
nterface
No Manual 256 fe80::5efe:10.166.14.188/128 45 isatap.{4BE8D97C-3967
-4100-9018-6D7124908E09}
No Manual 256 fe80::3cf2:4b46:af44:9c54/128 44 Teredo Tunneling Pse
udo-Interface
No Manual 256 fe80::d05a:e840:39c9:dfd4/128 18 VirtualBox Host-Only
Network
No Manual 256 fe80::d56b:d7f3:d5dc:1dd8/128 15 Bluetooth Network Co
nnection
No Manual 256 fe80::d847:e24a:77df:469b/128 12 Wireless Network Con
nection
No Manual 256 fe80::e4a4:37b6:124b:32a/128 20 Wireless Network Conn
ection 2
No Manual 256 fe80::f502:8618:a997:af97/128 11 Local Area Connectio
n
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface
1
No Manual 256 ff00::/8 18 VirtualBox Host-Only Netw
ork
No Manual 256 ff00::/8 44 Teredo Tunneling Pseudo-I
nterface
No Manual 256 ff00::/8 12 Wireless Network Connecti
on
No Manual 256 ff00::/8 11 Local Area Connection
No Manual 256 ff00::/8 20 Wireless Network Connecti
on 2
No Manual 256 ff00::/8 15 Bluetooth Network Connect
ion
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : PC04965
Primary Dns Suffix . . . . . . . : ads-storck.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ads-storck.com
PPP adapter T-Mobile D:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : T-Mobile D
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.166.14.188(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 193.254.160.1
10.74.83.22
Primary WINS Server . . . . . . . : 10.11.12.13
Secondary WINS Server . . . . . . : 10.11.12.14
NetBIOS over Tcpip. . . . . . . . : Disabled
Wireless LAN adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 0C-EE-E6-B5-89-92
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 00-26-5E-E5-D2-34
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1510 Wireless-N WLAN Mini-C
ard
Physical Address. . . . . . . . . : 0C-EE-E6-B5-89-92
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 00-24-E8-D7-5F-37
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-4C-60
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d05a:e840:39c9:dfd4%18(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 520618023
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-A6-F2-33-00-24-E8-D7-5F-37
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{D3DD92E6-FB16-4308-A921-C3D87821A3B2}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{07DA211B-FA1A-42C9-A621-F5D3BEA59952}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{E1B70C2B-BED7-4FF3-9908-193921E9F32E}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{CD28AAE0-CED9-4D4D-9B8F-1F2DDCED6C16}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{2FF30786-BF4D-40F0-9173-141A82037AA7}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:53aa:64c:3cf2:4b46:af44:9c54(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::3cf2:4b46:af44:9c54%44(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{4BE8D97C-3967-4100-9018-6D7124908E09}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #6
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Windows\system32>ping -6 www.six.heise.de
Pinging www.six.heise.de [2a02:2e0:3fe:100::6] with 32 bytes of data:
Request timed out.
Reply from 2a02:2e0:3fe:100::6: time=255ms
Reply from 2a02:2e0:3fe:100::6: time=233ms
Reply from 2a02:2e0:3fe:100::6: time=216ms
Ping statistics for 2a02:2e0:3fe:100::6:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 216ms, Maximum = 255ms, Average = 234ms
C:\Windows\system32>tracert -6 www.six.heise.de
Tracing route to www.six.heise.de [2a02:2e0:3fe:100::6]
over a maximum of 30 hops:
1 432 ms * 734 ms 1g-bge0.tserv6.fra1.ipv6.he.net [2001:470:0:69::
2]
2 254 ms 298 ms 299 ms gige-g2-4.core1.fra1.he.net [2001:470:0:69::1]
3 271 ms 239 ms 358 ms te3-1.c101.f.de.plusline.net [2001:7f8::3012:0:1
]
4 273 ms 280 ms 275 ms te6-1.c13.f.de.plusline.net [2a02:2e0:1::1e]
5 311 ms 341 ms 258 ms www.six.heise.de [2a02:2e0:3fe:100::6]
Trace complete.
C:\Windows\system32>tracert -6 marvin.toad.de
Tracing route to marvin.toad.de [2a01:198:51b:0:1168:41ce:c363:5488]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 ^C [this goes on and on ...]
C:\Windows\system32>
I will continue in a second posting because I have to switch PCs now ...
Win7 Teredo to AICCU tunnel does not work
Shadow Hawkins on Tuesday, 22 December 2009 21:09:50
Now the output of the client sitting behind the AYIYA tunnel in my private LAN:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\toad>netsh int ipv6 show int
Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
1 50 4294967295 connected Loopback Pseudo-Interface 1
11 10 1500 connected LAN-Verbindung
C:\Users\toad>netsh int ipv6 show route
Verff. Typ Met Prfix Idx Gateway/Schnittstelle
------- -------- ---- ------------------------ --- ---------------------
Nein Manuell 256 ::/0 11 fe80::21a:4fff:fe36:57df
Nein Manuell 256 ::1/128 1 Loopback Pseudo-Interface
1
Nein Manuell 8 2a01:198:51b::/64 11 LAN-Verbindung
Nein Manuell 256 2a01:198:51b:0:1168:41ce:c363:5488/128 11 LAN-Verbind
ung
Nein Manuell 256 2a01:198:51b:0:d47c:8c5f:dbfb:6958/128 11 LAN-Verbind
ung
Nein Manuell 256 fe80::/64 11 LAN-Verbindung
Nein Manuell 256 fe80::1168:41ce:c363:5488/128 11 LAN-Verbindung
Nein Manuell 256 ff00::/8 1 Loopback Pseudo-Interface
1
Nein Manuell 256 ff00::/8 11 LAN-Verbindung
C:\Users\toad>ipconfig /all
Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : MARVIN
Primres DNS-Suffix . . . . . . . : toad.de
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : toad.de
Ethernet-Adapter LAN-Verbindung:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physikalische Adresse . . . . . . : 00-24-1D-16-3C-7D
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : 2a01:198:51b:0:1168:41ce:c363:5488(Bevorz
ugt)
Temporre IPv6-Adresse. . . . . . : 2a01:198:51b:0:d47c:8c5f:dbfb:6958(Bevorz
ugt)
Verbindungslokale IPv6-Adresse . : fe80::1168:41ce:c363:5488%11(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.42.10(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : fe80::21a:4fff:fe36:57df%11
192.168.42.1
DNS-Server . . . . . . . . . . . : 192.168.42.1
NetBIOS ber TCP/IP . . . . . . . : Aktiviert
C:\Users\toad>ping -6 www.six.heise.de
Ping wird ausgefhrt fr www.six.heise.de [2a02:2e0:3fe:100::6] mit 32 Bytes Dat
en:
Antwort von 2a02:2e0:3fe:100::6: Zeit=42ms
Antwort von 2a02:2e0:3fe:100::6: Zeit=43ms
Antwort von 2a02:2e0:3fe:100::6: Zeit=43ms
Antwort von 2a02:2e0:3fe:100::6: Zeit=41ms
Ping-Statistik fr 2a02:2e0:3fe:100::6:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 41ms, Maximum = 43ms, Mittelwert = 42ms
C:\Users\toad>tracert -6 www.six.heise.de
Routenverfolgung zu www.six.heise.de [2a02:2e0:3fe:100::6] ber maximal 30 Absch
nitte:
1 <1 ms <1 ms <1 ms 2a01:198:51b::1
2 39 ms 39 ms 40 ms gw-1825.dus-01.de.sixxs.net [2a01:198:200:720::1
]
3 40 ms 40 ms 39 ms sixxs-dus.dus.speedpartner.de [2a01:198:200::1]
4 38 ms 40 ms 39 ms speedpartner.r1.dus1.de.opencarrier.eu [2001:7f8
:3a:e101::1]
5 121 ms 194 ms 245 ms gi1-15.c1.d.de.plusline.net [2001:7f8:8::3012:0:
1]
6 44 ms 43 ms 43 ms ge1-16.c302.f.de.plusline.net [2a02:2e0:1::45]
7 43 ms 45 ms 43 ms te2-4.c102.f.de.plusline.net [2a02:2e0:1::5]
8 42 ms 44 ms 44 ms te6-2.c13.f.de.plusline.net [2a02:2e0:1::22]
9 42 ms 46 ms 43 ms www.six.heise.de [2a02:2e0:3fe:100::6]
Ablaufverfolgung beendet.
C:\Users\toad>
Thanks a lot for your help - its appreciated!
Win7 Teredo to AICCU tunnel does not work
Shadow Hawkins on Tuesday, 22 December 2009 21:18:39
OK, now thats wiered. You just approved my second tunnel and just in that minute the ping worked. Now the traceroute shows the following:
C:\Users\rudolf-adm>tracert -6 marvin.toad.de
Tracing route to marvin.toad.de [2a01:198:51b:0:1168:41ce:c363:5488]
over a maximum of 30 hops:
1 658 ms 298 ms 456 ms 1g-bge0.tserv6.fra1.ipv6.he.net [2001:470:0:69::
2]
2 290 ms 261 ms 239 ms gige-g2-4.core1.fra1.he.net [2001:470:0:69::1]
3 252 ms 299 ms 276 ms 2001:7f8::a2dc:0:1
4 * 331 ms 317 ms oc-fra.dus.speedpartner.de [2001:7f8:3a:e102::2]
5 271 ms 299 ms 317 ms dedus01.sixxs.net [2a01:198:200::2]
6 420 ms 377 ms 376 ms cl-1825.dus-01.de.sixxs.net [2a01:198:200:720::2
]
7 348 ms 358 ms 358 ms 2a01:198:51b:0:1168:41ce:c363:5488
Trace complete.
C:\Users\rudolf-adm>
Has anything changed? Has the been a problem on any of the hosts above? Any ideas? You can trust me - I did not change anything, I have been trying for a couple of days now and left my config as it was before ....
Win7 Teredo to AICCU tunnel does not work
![[us]](/s/countries/us.gif) Shadow Hawkins on Saturday, 26 December 2009 17:55:01
I found Teredo rather unreliable when I toyed with it.
You could try using IPv4Gate ( http://ipv6gate.sixxs.net/ ) to make sure a public IPv6 website with a domain name can be accessed via IPv6, then try again with Teredo to see if you're getting IPv6 web connectivity at all. Then try connecting to the server on your subnet.
A common gotcha with IPv6 tunnels is the NAT connection tracking issue ( http://www.sixxs.net/faq/connectivity/?faq=conntracking ), but I'm not sure if that applies to AYIYA tunnels. To test for this, use IPv6 from your server's subnet (perhaps ping -6 www.sixxs.net ) and then try to access the server from a remote Teredo or IPv6 client. If that works but then quits working after a few minutes then it's your NAT connection tracking.
Win7 Teredo to AICCU tunnel does not work
Shadow Hawkins on Monday, 28 December 2009 14:23:22
Hi,
the problem does not seem to be related to connection tracking, because the servers were rechable using IPv6-Ping and port scanning using subnetonline.com. It only did not work using teredo. I will try to figure out what happend. In the meantime I am trying to connect two Win7 clients, one using Teredo, the other behind a Sixxs tunnel in my local LAN using IPv6 and IPSEC using the Windows firewall ....
M.
Win7 Teredo to AICCU tunnel does not work
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 10 February 2010 12:44:31
Did you get this resolved? I'm having the same kind of problem, I can't access my own subnet when using a Teredo tunnel. I think the problem is teredo itself, because when I visit www.kame.net, the turtle isn't moving which means I'm not accessing the site through IPv6, but IPv6 does work as http://ipv6.google.com works. When I visit http://ipv6.wcclan.net, I can let it ping and portscan the system behind my Sixxs tunnel and on the teredo tunnel.
When I ping to my subnet, either the endpoint or one of it's IP addresses, I keep getting "destination host unreachable", coming from my own teredo address. A traceroute6 and tracepath6 both stop at the first hop, my own system. Here is some output:
ifconfig teredo:
teredo Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::ffff:ffff:ffff/64 Scope:Link
inet6 addr: 2001:0:53aa:64c:2057:fb54:a66d:eae3/32 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:113 errors:0 dropped:0 overruns:0 frame:0
TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:86042 (86.0 KB) TX bytes:17398 (17.3 KB)
Route -6:
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
2001::/32 :: U 256 0 0 teredo
fe80::/64 :: U 256 0 0 wlan
fe80::/64 :: U 256 0 0 teredo
::/0 :: U 1029 0 0 teredo
::/0 :: !n -1 1 515 lo
::1/128 :: Un 0 1 30 lo
2001:0:53aa:64c:2057:fb54:a66d:eae3/128 :: Un 0 1 115 lo
fe80::ffff:ffff:ffff/128 :: Un 0 1 0 lo
fe80::21e:65ff:fe8a:d570/128 :: Un 0 1 0 lo
ff00::/8 :: U 256 0 0 wlan
ff00::/8 :: U 256 0 0 teredo
::/0 :: !n -1 1 515 lo
So far, nothing unusual. This is the unusual part:
tracepath6 2001:610:693:172:25::2
1?: [LOCALHOST] pmtu 1280
1: no reply
2: no reply
3: no reply
4: 2001:0:53aa:64c:2057:fb54:a66d:eae3 0.105ms !H
Resume: pmtu 1280
ping6 2001:610:693:172:25::2
From 2001:0:53aa:64c:2057:fb54:a66d:eae3 icmp_seq=11 Destination unreachable: Address unreachable
traceroute6 2001:610:693:172:25::2
traceroute to 2001:610:693:172:25::2 (2001:610:693:172:25::2) from 2001:0:53aa:64c:2057:fb54:a66d:eae3, 30 hops max, 24 byte packets
1 2001:0:53aa:64c:2057:fb54:a66d:eae3 (2001:0:53aa:64c:2057:fb54:a66d:eae3) 0.097 ms !H 0.078 ms !H 0.058 ms !H
So, how compatible is sixxs with Teredo (or the other way around)?
Win7 Teredo to AICCU tunnel does not work
Shadow Hawkins on Wednesday, 10 February 2010 12:46:57
I forgot to mention, I'm mainly using Ubuntu, the output above is from Ubuntu. The turtle _does_ move on Linux, but on Windows with Teredo, it doesn't. The systems that use my sixxs subnet have no problems with dual-stack sites, IPv6 is preferred there.
|
![[ch]](/s/countries/ch.gif)
on Monday, 21 December 2009 21:38:59
Posting is only allowed when you are