|
my tunnel suddenly stopped working
![[be]](/s/countries/be.gif) Carmen Sandiego on Monday, 01 December 2008 15:18:05
I've got an issue with my tunnel.
It suddenly stopped working and it won't work again, neither in Vista or Ubuntu, where it previously did work
It's isn't my internet connection either, I tested from three different locations ( and ISP's ) and it both didn't work ( where it did before )
my tunnelID = T17296
my pop = bebru01
I'm not sure if it's on my side, but it stopped working in both OSes the same day...
Tunnel Information for T17296:
PoP Id : bebru01
IPv6 Local : 2001:6f8:202:307::2/64
IPv6 Remote : 2001:6f8:202:307::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.0.70)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
Pingen naar 192.168.0.70 met 32 bytes aan gegevens:
Antwoord van 192.168.0.70: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.0.70: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.0.70: bytes=32 tijd<1 ms TTL=128
Ping-statistieken voor 192.168.0.70:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van âân bewerking in milliseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.100.184.146)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
Pingen naar 212.100.184.146 met 32 bytes aan gegevens:
Antwoord van 212.100.184.146: bytes=32 tijd=21 ms TTL=52
Antwoord van 212.100.184.146: bytes=32 tijd=19 ms TTL=52
Antwoord van 212.100.184.146: bytes=32 tijd=19 ms TTL=52
Ping-statistieken voor 212.100.184.146:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van âân bewerking in milliseconden:
Minimum = 19ms, Maximum = 21ms, Gemiddelde = 19ms
######
####### [3/8] Traceroute to the PoP (212.100.184.146) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
Traceren van de route naar bebru01.sixxs.net [212.100.184.146]
via maximaal 30 hops:
1 2 ms <1 ms <1 ms 192.168.0.254
2 7 ms 6 ms 5 ms 78-21-32-1.access.telenet.be [78.21.32.1]
3 11 ms 7 ms 7 ms dD5E0FBE1.access.telenet.be [213.224.251.225]
4 6 ms 8 ms 6 ms dD5E0FD51.access.telenet.be [213.224.253.81]
5 12 ms 10 ms 11 ms dD5E0FDA5.access.telenet.be [213.224.253.165]
6 10 ms 20 ms 9 ms dD5E0FD96.access.telenet.be [213.224.253.150]
7 13 ms 9 ms 11 ms 212.3.232.9
8 16 ms 17 ms 15 ms ae-6-6.ebr1.London1.Level3.net [4.69.136.246]
9 85 ms 216 ms 210 ms ae-15-51.car5.London1.Level3.net [4.68.116.19]
10 19 ms 19 ms 19 ms EASYNET-GRO.car5.London1.Level3.net [212.187.170.230]
11 19 ms 19 ms 20 ms te0-0-0.gr10.gdbru.be.easynet.net [87.86.77.47]
12 30 ms 22 ms 27 ms ge0-2-0-114.br3.gdbru.easynet.net [87.86.71.165]
13 18 ms 22 ms 18 ms ge4-0-0.cr4.gdbru.be.easynet.net [212.100.161.15]
14 20 ms 21 ms 20 ms bebru01.sixxs.net [212.100.184.146]
De trace is voltooid.
######
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
Pingen naar ::1 van ::1 met 32 bytes aan gegevens:
Antwoord van ::1: tijd<1 ms
Antwoord van ::1: tijd<1 ms
Antwoord van ::1: tijd<1 ms
Ping-statistieken voor ::1:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van âân bewerking in milliseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:202:307::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pingen naar 2001:6f8:202:307::2 van 2001:6f8:202:307::2 met 32 bytes aan gegevens:
Antwoord van 2001:6f8:202:307::2: tijd<1 ms
Antwoord van 2001:6f8:202:307::2: tijd<1 ms
Antwoord van 2001:6f8:202:307::2: tijd<1 ms
Ping-statistieken voor 2001:6f8:202:307::2:
Pakketten: verzonden = 3, ontvangen = 3, verloren = 0
(0% verlies).
De gemiddelde tijd voor het uitvoeren van âân bewerking in milliseconden:
Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:202:307::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall (both IPv4 and IPv6) of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
Pingen naar 2001:6f8:202:307::1 van 2001:6f8:202:307::2 met 32 bytes aan gegevens:
Time-out bij opdracht.
Time-out bij opdracht.
Time-out bij opdracht.
Ping-statistieken voor 2001:6f8:202:307::1:
Pakketten: verzonden = 3, ontvangen = 0, verloren = 3
(100% verlies).
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
The traceroute from test 7/8:
Traceren van de route naar noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c]
via maximaal 30 hops:
1 * * * Time-out bij opdracht.
2 * * * Time-out bij opdracht.
3 * * * Time-out bij opdracht.
4 * * * Time-out bij opdracht.
5 * * * Time-out bij opdracht.
6 * * * Time-out bij opdracht.
7 * * * Time-out bij opdracht.
8 * * * Time-out bij opdracht.
9 * * * Time-out bij opdracht.
10 * * * Time-out bij opdracht.
11 * * * Time-out bij opdracht.
12 * * * Time-out bij opdracht.
13 * * * Time-out bij opdracht.
14 * * * Time-out bij opdracht.
15 * * * Time-out bij opdracht.
16 * * * Time-out bij opdracht.
17 * * * Time-out bij opdracht.
18 * * * Time-out bij opdracht.
19 * * * Time-out bij opdracht.
20 * * * Time-out bij opdracht.
21 * * * Time-out bij opdracht.
22 * * * Time-out bij opdracht.
23 * * * Time-out bij opdracht.
24 * * * Time-out bij opdracht.
25 * * * Time-out bij opdracht.
26 * * * Time-out bij opdracht.
27 * * * Time-out bij opdracht.
28 * * * Time-out bij opdracht.
29 * * * Time-out bij opdracht.
30 * * * Time-out bij opdracht.
De trace is voltooid.
my tunnel suddenly stopped working
Of which the output tells that you can't reach the PoP side of the tunnel, which is just a first diagnostic, telling if it works or not.
What we really need is output from "netsh int ipv6 show routes", "netsh int ipv6 show addresses" while AICCU is running. Also check if your TUN/TAP is correctly setup, next to running AICCU in daemon mode.
And of course, if you really think it is the PoP giving issues, then file a proper ticket with all the requested details.
my tunnel suddenly stopped working
Carmen Sandiego on Monday, 01 December 2008 16:21:35
netsh interface ipv6 show route
Public. Type Met Voorvoegsel Idx Naam gateway/interface
------- -------- --- ------------------------ --- ------------------------
Ja Handmatig 256 ::/0 12 2001:6f8:202:307::1
Nee Handmatig 256 ::1/128 1 Loopback Pseudo-Interface 1
Nee Handmatig 256 2001:6f8:202:307::/64 12 sixxs
Nee Handmatig 256 2001:6f8:202:307::2/128 12 sixxs
Nee Handmatig 256 fe80::/64 10 LAN-verbinding* 6
Nee Handmatig 256 fe80::/64 12 sixxs
Nee Handmatig 256 fe80::/64 9 LAN-verbinding
Nee Handmatig 256 fe80::/64 11 Draadloze netwerkverbinding
Nee Handmatig 256 fe80::100:7f:fffe/128 10 LAN-verbinding* 6
Nee Handmatig 256 fe80::811:9972:33b2:45c9/128 11 Draadloze netwerkverbinding
Nee Handmatig 256 fe80::391d:a4a:8a24:7ecc/128 12 sixxs
Nee Handmatig 256 fe80::7cdb:b15f:35a9:2b7/128 9 LAN-verbinding
Nee Handmatig 256 ff00::/8 1 Loopback Pseudo-Interface 1
Nee Handmatig 256 ff00::/8 10 LAN-verbinding* 6
Nee Handmatig 256 ff00::/8 12 sixxs
Nee Handmatig 256 ff00::/8 9 LAN-verbinding
Nee Handmatig 256 ff00::/8 11 Draadloze netwerkverbinding
netsh interfaces ipv6 show addresses
Interface 1: Loopback Pseudo-Interface 1
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Voorkeur infinite infinite ::1
Interface 11: Draadloze netwerkverbinding
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Afgeschaft infinite infinite fe80::811:9972:33b2:45c9%11
Interface 12: sixxs
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Handmatig Voorkeur infinite infinite 2001:6f8:202:307::2
Overig Voorkeur infinite infinite fe80::391d:a4a:8a24:7ecc%12
Interface 10: LAN-verbinding* 6
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Afgeschaft infinite infinite fe80::100:7f:fffe%10
Interface 9: LAN-verbinding
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Voorkeur infinite infinite fe80::7cdb:b15f:35a9:2b7%9
I do think my TUN/TAP is configured correctly, I didn't change anything :s
here's the output from the ipconfig /all
Ethernet-adapter sixxs:
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : TAP-Win32 Adapter V9
Fysiek adres. . . . . . . . . . . : 00-FF-98-B1-0C-EB
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
IPv6-adres. . . . . . . . . . . . : 2001:6f8:202:307::2(voorkeur)
Link-local IPv6-adres . . . . . . : fe80::391d:a4a:8a24:7ecc%12(voorkeur)
Standaardgateway. . . . . . . . . : 2001:6f8:202:307::1
DHCPv6 IAID . . . . . . . . . . . : 201392024
DNS-servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS via TCPIP . . . . . . . . : uitgeschakeld
And I don't know if it's the POP because with some friends who also are on the same POP, this seems to work properly... :s
PS.
Lan-Verbinding = my primary network connection
LAN-verbinding* 6 = Teredo tunneling pseudo interface
Draadloze netwerkverbinding = wireless ( not used )
my tunnel suddenly stopped working
64 bytes from 2001:6f8:202:307::2: icmp_seq=1 ttl=116 time=123 ms
Pings for me, what is the issue?
my tunnel suddenly stopped working
Carmen Sandiego on Monday, 01 December 2008 16:40:13
that I can't connect to any ipv6 location :s ( I can't even ping the POP :/ )
so apparently the connection works only one way. :s
my tunnel suddenly stopped working
Carmen Sandiego on Monday, 01 December 2008 17:03:24
I think it might be DNS issues :(
my tunnel suddenly stopped working
![[us]](/s/countries/us.gif) Carmen Sandiego on Thursday, 04 December 2008 20:11:10
Any solution yet? I'm having a similar problem now.
my tunnel suddenly stopped working
"Similar problem", but what is the exact problem, provide the details etc ;)
my tunnel suddenly stopped working
Carmen Sandiego on Saturday, 06 December 2008 13:50:48
I can visit sites by using the IPv6-address itselve, but I can't seem to do any lookups,
I think my DNS is broken or something like that
Everything is working fine in Ubuntu \o/
( I have dnsmasq installed in Ubuntu, could that be it? )
nslookup works fine though :s
my tunnel suddenly stopped working
Which browser, which Operating System, what are the configuration settings, what firewall, what viruschecker, what what what.... MORE DETAILS.
You didn't even explain how the connectivity to the box is arranged; and as you mention that it does work in Ubuntu, I guess you have a subnet or something, but can't know for sure.
my tunnel suddenly stopped working
Carmen Sandiego on Saturday, 06 December 2008 19:36:47
Well:
Virusscanner: NONE
Firewall: Default windows firewall, everything's on default
OS: Vista SP1
Browser: Latest Firefox
network.dns.disableIPv6;false
network.dns.ipv4OnlyDomains;
I'm connected behind a router and I've got ADSL
NAT is enabled
I'd just say that it's Vista that's acting strange :p
my tunnel suddenly stopped working
Firefox should simply work(tm) with IPv6. Did you configure a proxy?
Did you try connecting to http://www.ipv6.sixxs.net?
As for Vista and letting other apps use IPv6, it seems the trick is to add a global address to a LAN interface. See the Wiki for more details on how to do that.
I'm connected behind a router and I've got ADSL NAT is enabled
You probably meant to say "I'm connected behind a NAT box and I've got ADSL". If you had a 'router', you would not have a need for a NAT as then you could route your packets.
You wrote that you can ping6 hosts, though you didn't mention over which route (tracert6 helps here), maybe it is just 6to4 or Teredo that you are using.
my tunnel suddenly stopped working
Shadow Hawkins on Wednesday, 10 December 2008 03:15:54
i'm having the exact same problem (except that i run gentoo linux).
i've tried running aiccu on another pc which is connected to a NAT (my main pc has a straight PPPoE passtrough session to the net), and it gave me the same result.
i've tried various routes that i've found on this forum/FAQ, while still applying my own POP endpoint,
and it still didn't seem to work.
I get an IP, the route is setup properly, but i can't even ping the POP itself over IPv6 (IPv4 is fine)
guntherdw@lisa ~ % ping6 ipv6.google.com
PING ipv6.google.com(2001:4860:0:1001::68) 56 data bytes
^C
--- ipv6.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2011ms
guntherdw@lisa ~ % sudo ip -6 ro show
2001:6f8:202:2fd::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
default via 2001:6f8:202:2fd::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
If i run tcpdump i can see the ICMP packets going over the sixxs dev, but no reply coming back at me.
It's been like this for a day or 2 now, i don't want to lose my tunnel :(.
my tunnel suddenly stopped working
Shadow Hawkins on Wednesday, 10 December 2008 03:19:00
additional notes i forgot to include that might help
(i'm on bebru01 as well)
guntherdw@lisa ~ % sudo ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 00:1d:92:64:89:31 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.5/24 brd 192.168.0.255 scope global eth0
inet6 fe80::21d:92ff:fe64:8931/64 scope link
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
link/sit 0.0.0.0 brd 0.0.0.0
4: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN qlen 3
link/ppp
inet 83.101.8.159 peer 83.101.8.1/32 scope global ppp0
6: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500
link/[65534]
inet6 2001:6f8:202:2fd::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4f8:202:2fd:2/64 scope link
valid_lft forever preferred_lft forever
my tunnel suddenly stopped working
Please try to read the "Reporting Problems Checklist" section of the contact page as clearly stated in the big orange boxes on the forum submission page (twice even) and in various other places...
The provided information is useless.
my tunnel suddenly stopped working
Carmen Sandiego on Wednesday, 10 December 2008 15:08:33
My problem suddenly went away on it's own for awhile, now came back this morning. Can't even ping the other end of my tunnel anymore.
C:\Users\bknoblauch>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : bknoblauch
Primary Dns Suffix . . . . . . . : sscorp.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sscorp.com
Ethernet adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-86-7E-64-13
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:4978:f:21d::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::f113:9f2e:69a8:f5c7%16(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.245.199(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:4978:f:21d::1
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
it Ethernet NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1A-4D-5F-03-47
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fdfe:182a:bdca:470f::a00(Preferred)
Link-local IPv6 Address . . . . . : fe80::6164:9e73:407c:e6bd%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.100.65(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 192.168.100.1
DNS Servers . . . . . . . . . . . : 192.168.102.10
192.168.102.14
NetBIOS over Tcpip. . . . . . . . : Enabled
C:\Users\bknoblauch>netsh int ipv6 sh route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
Yes Manual 256 ::/0 16 2001:4978:f:21d::1
No Manual 256 ::1/128 1 Loopback Pseudo-Interface
1
No Manual 256 2001:4978:f:21d::/64 16 aiccu
No Manual 256 2001:4978:f:21d::2/128 16 aiccu
No Manual 256 fdfe:182a:bdca:470f::/64 11 Local Area Connection 2
No Manual 256 fdfe:182a:bdca:470f::a00/128 11 Local Area Connection
2
No Manual 256 fe80::/64 16 aiccu
No Manual 256 fe80::/64 11 Local Area Connection 2
No Manual 256 fe80::6164:9e73:407c:e6bd/128 11 Local Area Connectio
n 2
No Manual 256 fe80::f113:9f2e:69a8:f5c7/128 16 aiccu
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface
1
No Manual 256 ff00::/8 16 aiccu
No Manual 256 ff00::/8 11 Local Area Connection 2
Thanks!
my tunnel suddenly stopped working
Please actually follow the "Reporting Problems Checklist", can't do anything to help without those items, we are not on your computer.
my tunnel suddenly stopped working
Shadow Hawkins on Wednesday, 10 December 2008 15:26:54
Yep, same problem here. Tunnel worked yesterday and doesn't this morning.
netsh int ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
Yes Manual 256 ::/0 14 2001:4978:f:22e::1
No Manual 256 ::1/128 1 Loopback Pseudo-Interface
1
No Manual 256 2001:4978:f:22e::/64 14 aiccu
No Manual 256 2001:4978:f:22e::2/128 14 aiccu
No Manual 256 fdfe:182a:bdca:470f::/64 10 Local Area Connection
No Manual 256 fdfe:182a:bdca:470f::a01/128 10 Local Area Connection
No Manual 256 fe80::/64 14 aiccu
No Manual 256 fe80::/64 10 Local Area Connection
No Manual 256 fe80::194:508e:52df:5fed/128 14 aiccu
No Manual 256 fe80::2501:5c0b:3927:f082/128 10 Local Area Connectio
n
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface
1
No Manual 256 ff00::/8 14 aiccu
No Manual 256 ff00::/8 10 Local Area Connection
C:\Users\cholzhauer\Desktop>aiccu-2008-03-15-windows-console.exe autotest
sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs
.net)"
sock_printf() : "client TIC/draft-00 AICCU/2008.03.15-console-win32 WinNT/6.0.6
002-SP2"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1228919079"
sock_printf() : "username CHK2-SIXXS"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 b8afb078ca2ebdb0bcad53ecb0db294c"
sock_printf() : "authenticate md5 056bc0a1be4ee3e00059b596818183ea"
sock_getline() : "200 Succesfully logged in using md5 as CHK2-SIXXS (Carl Holzha
uer) from 2001:7b8:3:4f:202:b3ff:fe46:bec"
sock_printf() : "tunnel show T18502"
sock_getline() : "201 Showing tunnel information for T18502"
sock_getline() : "TunnelId: T18502"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2001:4978:f:22e::2"
sock_getline() : "IPv6 POP: 2001:4978:f:22e::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: My First Tunnel"
sock_getline() : "POP Id: uschi02"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 216.14.98.22"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: f011a3ed8e114659a3221798aa52a617"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T18502
sock_printf() : "QUIT Tschau!"
Tunnel Information for T18502:
PoP Id : uschi02
IPv6 Local : 2001:4978:f:22e::2/64
IPv6 Remote : 2001:4978:f:22e::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D
36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1)
Found interface named 'aiccu', with guid {F4C09817-598F-488C-9EE3-C8EB2A83419F},
using it
[tun-start] Trying \\.\Global\{F4C09817-598F-488C-9EE3-C8EB2A83419F}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
heartbeat_socket() - IPv4 : 192.168.100.192
#######
[AYIYA-tun->tundev] : (Socket to TUN) started
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.100.192)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
Pinging 192.168.100.192 with 32 bytes of data:
Reply from 192.168.100.192: bytes=32 time<1ms TTL=128
Reply from 192.168.100.192: bytes=32 time<1ms TTL=128
Reply from 192.168.100.192: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.100.192:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.14.98.22)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
Pinging 216.14.98.22 with 32 bytes of data:
Reply from 216.14.98.22: bytes=32 time=16ms TTL=53
Reply from 216.14.98.22: bytes=32 time=18ms TTL=53
Reply from 216.14.98.22: bytes=32 time=18ms TTL=53
Ping statistics for 216.14.98.22:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 18ms, Average = 17ms
######
####### [3/8] Traceroute to the PoP (216.14.98.22) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
Tracing route to sixxs.cx01.chi.bb.your.org [216.14.98.22]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 12.199.185.1
2 11 ms 13 ms 9 ms 12.88.183.17
3 19 ms 21 ms 20 ms cr81.dtrmi.ip.att.net [12.122.102.14]
4 17 ms 31 ms 19 ms cr1.cgcil.ip.att.net [12.123.139.157]
5 17 ms 19 ms 20 ms tbr1.cgcil.ip.att.net [12.122.17.154]
6 18 ms 16 ms 17 ms ggr6.cgcil.ip.att.net [12.122.87.241]
7 18 ms 38 ms 18 ms 192.205.35.138
8 19 ms 16 ms 18 ms your.org.ge2-5.br02.chc01.pccwbtn.net [63.218.5.
38]
9 26 ms 23 ms 18 ms sixxs.cx01.chi.bb.your.org [216.14.98.22]
Trace complete.
######
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
Pinging ::1 from ::1 with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Ping statistics for ::1:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4978:f:22e::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pinging 2001:4978:f:22e::2 from 2001:4978:f:22e::2 with 32 bytes of data:
Reply from 2001:4978:f:22e::2: time<1ms
Reply from 2001:4978:f:22e::2: time<1ms
Reply from 2001:4978:f:22e::2: time<1ms
Ping statistics for 2001:4978:f:22e::2:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4978:f:22e::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall (both IPv4 and IPv6) of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
Pinging 2001:4978:f:22e::1 from 2001:4978:f:22e::2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:4978:f:22e::1:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connecti
on
### If your browser supports IPv6 and uses it of course.
'tracert6' is not recognized as an internal or external command,
operable program or batch file.
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses
IPv6
'tracert6' is not recognized as an internal or external command,
operable program or batch file.
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : cholzhauer
Primary Dns Suffix . . . . . . . : sscorp.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sscorp.com
Ethernet adapter aiccu:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-F4-C0-98-17
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:4978:f:22e::2(Preferred)
Link-local IPv6 Address . . . . . : fe80::194:508e:52df:5fed%14(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.95.237(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 2001:4978:f:22e::1
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Networking
Controller
Physical Address. . . . . . . . . : 00-1F-D0-22-95-B3
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fdfe:182a:bdca:470f::a01(Preferred)
Link-local IPv6 Address . . . . . : fe80::2501:5c0b:3927:f082%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.100.192(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 192.168.100.1
DNS Servers . . . . . . . . . . . : 192.168.102.14
192.168.102.10
NetBIOS over Tcpip. . . . . . . . : Enabled
my tunnel suddenly stopped working
You also seem to be at the same company and seem to be getting fdfe:182a:bdca:470f::a01 address, which looks to be manually configured as that is not an EUI-64 postfix appended to it.
One mentioned an Active Directory, how sure are you that your firewall admin didn't suddenly start blocking things?
my tunnel suddenly stopped working
Carmen Sandiego on Wednesday, 10 December 2008 15:36:09
The fdfe is statically assigned so that I can hit other local boxes with statically assigned IPv6 (internal use only, there's no outside IPv6 connectivity on our network).
The firewall admin hasn't changed anything. He also has a tunnel and noted the same exact problems. Really nothing has changed here. And now all of a sudden both our tunnels came back up. Odd, but oh well... :)
my tunnel suddenly stopped working
Carmen Sandiego on Thursday, 11 December 2008 15:56:45
Is there a page we can check to see the real-time status of the POPs? My tunnel is down again, once again no changes here. Would be nice to be able to quickly rule out problems on the far end. I typically assume the problem is on my end, but having it drop and come up again later with no changes makes me want to check all the possibilities!
Thanks!
my tunnel suddenly stopped working
Shadow Hawkins on Wednesday, 10 December 2008 15:33:42
My tunnel now all of a sudden works just fine. I was going through some RSS feeds when ipv6.google.com all of a sudden just popped up; I didn't do anything to change it.
my tunnel suddenly stopped working
Carmen Sandiego on Wednesday, 24 December 2008 15:07:05
Very strange stuff. I've switched to Teredo for awhile to compare and I have the same random dropping problems there too. Maybe I'll try setting up my SIXXS tunnel in a VM and see what happens. Might just be my particular installation of Vista is unreliable.
my tunnel suddenly stopped working
If you can provide details on what you mean with "dropping" that would help a lot.
Wireshark is also always a great friend in times of weird issues.
my tunnel suddenly stopped working
Carmen Sandiego on Friday, 26 December 2008 13:37:00
Well, with Teredo it'll just suddenly refuse to route through that interface. Nothing happens anymore. Configuration looks the same as it always does. Wireshark doesn't capture any traffic. The system doesn't even seem to try.
With the SIXXS tunnel, I can still ping the local side, but the far end goes away. Once again, wireshark doesn't capture anything. Been through the troubleshooting procedure and there really isn't much help for this problem there.
All I can guess is that either it's a Vista thing, or it's a "I need to reformat my computer" thing. :-)
my tunnel suddenly stopped working
Sounds like a firewalling issue to me if everything else is correct.
Do also check your routing of course, for the rest, go through the "Reporting Problems Checklist" (which we really should rename "Diagnosing Problems Checklist") and check what might be wrong or not.
my tunnel suddenly stopped working
Carmen Sandiego on Friday, 26 December 2008 21:33:02
Up and running using Carl's FreeBSD router now. That seems to work fine, so I deleted my tunnel. Seeing as I can't keep one running, I'll just route through his now that it's going! :-)
|
![[ch]](/s/countries/ch.gif)
on Monday, 01 December 2008 15:31:06
Posting is only allowed when you are