AYIYA tunnel is up, AICCU running, IPv6 is pingable but no connectivity - driving me bananas :-(
Carmen Sandiego on Friday, 24 July 2009 11:24:49
This is really strange -
installed the tuntap 9.01 and the aiccu commandline util.
the AYIYA tunnel is up and i can PING the ip address from outside, so it must be running.
But the virtual tuntap adapter always saiy no connectivity - packets are sent bun 0 packets received.
the outpunt of aiccu
C:\AICCU>aiccu start
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.1.7
100"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1248426586"
sock_printf() : "username IKN2-SIXXS"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 e8b80be21b3600e448e6b87bb9e84d87"
sock_printf() : "authenticate md5 dfedd5fffc40669a459be8f649caed9c"
sock_getline() : "200 Succesfully logged in using md5 as IKN2-SIXXS (Ingeborg Kr
eller) from 2001:7b8:3:4f:202:b3ff:fe46:bec"
sock_printf() : "tunnel list"
sock_getline() : "201 Listing tunnels"
sock_getline() : "T22393 2001:6f8:1c00:6e::2 ayiya deham02"
sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>"
sock_printf() : "tunnel show T22393"
sock_getline() : "201 Showing tunnel information for T22393"
sock_getline() : "TunnelId: T22393"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2001:6f8:1c00:6e::2"
sock_getline() : "IPv6 POP: 2001:6f8:1c00:6e::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: kreller"
sock_getline() : "POP Id: deham02"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 212.224.0.189"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: a5ff5a33cadb93498447cf0265f247e9"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T22393
sock_printf() : "QUIT Running Down That Hill"
Tunnel Information for T22393:
PoP Id : deham02
IPv6 Local : 2001:6f8:1c00:6e::2/64
IPv6 Remote : 2001:6f8:1c00:6e::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : kreller
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
Renaming adapter 'LAN-Verbindung 2' to 'sixxs' and using it
[tun-start] Trying \\.\Global\{8EC99117-5149-4EAC-B0F7-22D036EFB825}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
so - all fine.
and now
C:\Users\Roland>ipconfig /all
Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : HP-Mini
Primres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : fritz.box
Ethernet-Adapter sixxs:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : TAP-Win32 Adapter V9
Physikalische Adresse . . . . . . : 00-FF-8E-C9-91-17
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : 2001:6f8:1c00:6e::2(Bevorzugt)
Verbindungslokale IPv6-Adresse . : fe80::8907:af1b:f5a5:1a62%22(Bevorzugt)
IPv4-Adresse (Auto. Konfiguration): 169.254.26.98(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.0.0
Standardgateway . . . . . . . . . : 2001:6f8:1c00:6e::1
DHCPv6-IAID . . . . . . . . . . . : 369164174
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-11-D3-97-3B-00-24-81-5F-18-4F
DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS ber TCP/IP . . . . . . . : Aktiviert
Ethernet-Adapter Bluetooth-Netzwerkverbindung:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Bluetooth-Gert (PAN)
Physikalische Adresse . . . . . . : 00-24-7E-4D-F1-D3
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
Verbindungsspezifisches DNS-Suffix: fritz.box
Beschreibung. . . . . . . . . . . : Broadcom 4321AG 802.11a/b/g/draft-n Wi-Fi
Adapter
Physikalische Adresse . . . . . . : 00-21-00-C9-74-0E
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : 2002:81a8:102::(Bevorzugt)
IPv6-Adresse. . . . . . . . . . . : 2a01:198:423:0:5c0b:eecc:c211:469d(Bevorz
ugt)
Temporre IPv6-Adresse. . . . . . : 2a01:198:423:0:c896:37b7:1f3d:da6f(Bevorz
ugt)
Verbindungslokale IPv6-Adresse . : fe80::5c0b:eecc:c211:469d%12(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.178.22(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Freitag, 24. Juli 2009 11:05:17
Lease luft ab. . . . . . . . . . : Montag, 3. August 2009 11:05:17
Standardgateway . . . . . . . . . : fe80::21f:3fff:fef2:613e%12
192.168.178.1
DHCP-Server . . . . . . . . . . . : 192.168.178.1
DHCPv6-IAID . . . . . . . . . . . : 218112256
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-11-D3-97-3B-00-24-81-5F-18-4F
DNS-Server . . . . . . . . . . . : fd00::21f:3fff:fef2:613e
192.168.178.1
NetBIOS ber TCP/IP . . . . . . . : Aktiviert
Tunneladapter isatap.fritz.box:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix: fritz.box
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter isatap.{8EC99117-5149-4EAC-B0F7-22D036EFB825}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
for the time being, only the SIXXS adapter should be important
as it is my virtual tuntap - it looks ok and as i said its ip address is pongable
but it simply is not working at all... :-(
is there something i completely misunderstood?
any idears.
greetings
Roland Schweiger
AYIYA tunnel is up, AICCU running, IPv6 is pingable but no connectivity - driving me bananas :-(
Jeroen Massar on Friday, 24 July 2009 11:31:56 the AYIYA tunnel is up and i can PING the ip address from outside, so it must be running. But the virtual tuntap adapter always saiy no connectivity - packets are sent bun 0 packets received.
Your ifconfig list shows:
IPv6-Adresse. . . . . . . . . . . : 2001:6f8:1c00:6e::2(Bevorzugt) IPv6-Adresse. . . . . . . . . . . : 2002:81a8:102::(Bevorzugt) IPv6-Adresse. . . . . . . . . . . : 2a01:198:423:0:5c0b:eecc:c211:469d(Bevorz ugt)
Temporre IPv6-Adresse. . . . . . : 2a01:198:423:0:c896:37b7:1f3d:da6f(Bevorz ugt)
Those are 3 possible (4 if you include the temporary address) different exits: AYIYA (local tunnel), 6to4 over your fritzbox, and another prefix over your fritzbox.
How do you know for sure that packets are taking the appropriate exit?
I suggest you first start trimming down your configuration so that you have only 1 global address (temporary is acceptable if it is in the same prefix, though I personally disable privacy addresses).
Then, when that is done, try again.
Of course you should always check firewalls if they fully support IPv6. Easiest method for checking those things though is running a Wireshark.
Fritz!Box can do tcpdumps btw: http://fritz.box/html/capture.html
You can then see what your Fritz!Box sees, very very handy.
AYIYA tunnel is up, AICCU running, IPv6 is pingable but no connectivity - driving me bananas :-(
Carmen Sandiego on Friday, 24 July 2009 13:00:08
what i have done now is to completely De-ACTIVATE IPv6 support in FritzBox,
it does not help me anyway because i want to test / use AICCU / AYIYA running on the local machine.
not it looks like
Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : HP-Mini
Primres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : fritz.box
Ethernet-Adapter sixxs:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : TAP-Win32 Adapter V9
Physikalische Adresse . . . . . . : 00-FF-8E-C9-91-17
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : 2001:6f8:1c00:6e::2(Bevorzugt)
Verbindungslokale IPv6-Adresse . : fe80::8907:af1b:f5a5:1a62%15(Bevorzugt)
IPv4-Adresse (Auto. Konfiguration): 169.254.26.98(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.0.0
Standardgateway . . . . . . . . . : 2001:6f8:1c00:6e::1
DHCPv6-IAID . . . . . . . . . . . : 369164174
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-11-D3-97-3B-00-24-81-5F-18-4F
DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS ber TCP/IP . . . . . . . : Aktiviert
Ethernet-Adapter LAN-Verbindung:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Marvell Yukon 88E8072-PCI-E-Gigabit-Ether
net-Controller
Physikalische Adresse . . . . . . : 00-24-81-5F-18-4F
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Ethernet-Adapter Bluetooth-Netzwerkverbindung:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Bluetooth-Gert (PAN)
Physikalische Adresse . . . . . . : 00-24-7E-4D-F1-D3
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
Verbindungsspezifisches DNS-Suffix: fritz.box
Beschreibung. . . . . . . . . . . : Broadcom 4321AG 802.11a/b/g/draft-n Wi-Fi
Adapter
Physikalische Adresse . . . . . . : 00-21-00-C9-74-0E
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : fd00::5c0b:eecc:c211:469d(Bevorzugt)
Temporre IPv6-Adresse. . . . . . : fd00::b942:dda3:1cc9:351b(Bevorzugt)
Verbindungslokale IPv6-Adresse . : fe80::5c0b:eecc:c211:469d%12(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.178.22(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Freitag, 24. Juli 2009 12:36:27
Lease luft ab. . . . . . . . . . : Montag, 3. August 2009 12:36:27
Standardgateway . . . . . . . . . : fe80::21f:3fff:fef2:613e%12
192.168.178.1
DHCP-Server . . . . . . . . . . . : 192.168.178.1
DHCPv6-IAID . . . . . . . . . . . : 218112256
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-11-D3-97-3B-00-24-81-5F-18-4F
DNS-Server . . . . . . . . . . . : fd00::21f:3fff:fef2:613e
192.168.178.1
NetBIOS ber TCP/IP . . . . . . . : Aktiviert
Tunneladapter isatap.fritz.box:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix: fritz.box
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter isatap.{8EC99117-5149-4EAC-B0F7-22D036EFB825}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter isatap.{BDCD28D4-24E0-493A-B11E-245C70CF0087}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #3
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
at least the physical wLAN adapter now only fas fd00 and fe00 addresses, which i suppose are linklocal.
currently same problem: the tunnel seems to be up, i can ping the ipv6 address from outside but i have no ipv6 connectivity and the virtual sixxs tuntap adapter says "0 packets" on the receive side :-(
AYIYA tunnel is up, AICCU running, IPv6 is pingable but no connectivity - driving me bananas :-(
Jeroen Massar on Friday, 24 July 2009 14:02:54 at least the physical wLAN adapter now only fas fd00 and fe00 addresses, which i suppose are linklocal.
fe80::/10 == link-local
fd00::/8 == ULA (Unique Local Address), funny that they generate those, might be handy for local communications though.
currently same problem: the tunnel seems to be up, i can ping the ipv6 address from outside but i have no ipv6 connectivity and the virtual sixxs tuntap adapter says "0 packets" on the receive side :-(
Please try reading the Contact pages "Problems Checklist", it asks for things as routing tables, traceroutes etc. These are invaluable when you want people to help you out.
Posting is only allowed when you are logged in. |