Ticket ID: SIXXS #9106094 Ticket Status: User PoP: deolo01 - EWE TEL GmbH (Oldenburg)
tunnel is not responding
Shadow Hawkins on Monday, 01 April 2013 04:07:55
I am using aiccu on osx but I can't get it running. The tun interface is there and everything seems right but I can't ping through it or anything else. I used the newest source and also tried the homebrew package.
The host is behind a nat.
toby@Tobys-Mac-mini:~$ sudo aiccu test
sock_getline() : "200 SixXS TIC Service on nlhaa01.sixxs.net ready (http://www.sixxs.net)"
sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-darwin Darwin/12.3.0"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1364788367"
sock_printf() : "username TPP6-SIXXS"
sock_getline() : "200 TPP6-SIXXS choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 173136f8fef712eef3bf937d4f26467c"
sock_printf() : "authenticate md5 d707afee23c012fe31abc7189fc834d0"
sock_getline() : "200 Successfully logged in using md5 as TPP6-SIXXS (Tobias Pollmann)"
sock_printf() : "tunnel list"
sock_getline() : "201 Listing tunnels"
sock_getline() : "T120202 2a02:8204:d600:66::2 ayiya deolo01"
sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>"
sock_printf() : "tunnel show T120202"
sock_getline() : "201 Showing tunnel information for T120202"
sock_getline() : "TunnelId: T120202"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2a02:8204:d600:66::2"
sock_getline() : "IPv6 POP: 2a02:8204:d600:66::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: My First Tunnel"
sock_getline() : "POP Id: deolo01"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 80.228.241.140"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: ...."
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T120202
sock_printf() : "QUIT Illuminaughty"
Tunnel Information for T120202:
POP Id : deolo01
IPv6 Local : 2a02:8204:d600:66::2/64
IPv6 Remote : 2a02:8204:d600:66::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
[tun-start] Trying Configured TUN/TAP interface tun0...
[tun-start] Using TUN/TAP interface tun0
[tun-start] Setting TUNSIFHEAD for tun0
add net default: gateway 2a02:8204:d600:66::1
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
heartbeat_socket() - IPv4 : 192.168.1.2
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.2)
### 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
PING 192.168.1.2 (192.168.1.2): 56 data bytes
64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=0.099 ms
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.064 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.108 ms
--- 192.168.1.2 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.064/0.090/0.108/0.019 ms
######
Did this work? [Y/n] Y
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (80.228.241.140)
### 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
PING 80.228.241.140 (80.228.241.140): 56 data bytes
64 bytes from 80.228.241.140: icmp_seq=0 ttl=56 time=27.866 ms
64 bytes from 80.228.241.140: icmp_seq=1 ttl=56 time=26.589 ms
64 bytes from 80.228.241.140: icmp_seq=2 ttl=56 time=26.405 ms
--- 80.228.241.140 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 26.405/26.953/27.866/0.650 ms
######
Did this work? [Y/n] Y
####### [3/8] Traceroute to the PoP (80.228.241.140) 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
traceroute to 80.228.241.140 (80.228.241.140), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.875 ms 1.146 ms 1.056 ms
2 192.168.2.1 (192.168.2.1) 1.879 ms 2.552 ms 2.955 ms
3 217.0.117.99 (217.0.117.99) 18.054 ms 19.697 ms 17.283 ms
4 87.186.192.114 (87.186.192.114) 17.137 ms
87.186.192.122 (87.186.192.122) 17.718 ms 16.510 ms
5 hh-ea4-i.hh.de.net.dtag.de (62.154.33.37) 20.427 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.34) 20.673 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.37) 20.535 ms
6 80.156.163.126 (80.156.163.126) 21.523 ms
80.150.168.162 (80.150.168.162) 20.794 ms
80.156.160.242 (80.156.160.242) 20.983 ms
7 ewetel-ic-155862-hbg-b1.c.telia.net (62.115.8.174) 26.445 ms 25.683 ms 25.087 ms
8 bbrt.ol-0-1-xe-0-3-0.ewe-ip-backbone.de (80.228.90.98) 26.093 ms 26.322 ms 26.212 ms
9 rzrt.rzhl-1-xe-0-0-0.ewe-ip-backbone.de (80.228.98.10) 26.825 ms 26.186 ms 37.023 ms
10 deolo01.sixxs.net (80.228.241.140) 26.458 ms 26.536 ms 26.264 ms
######
Did this work? [Y/n] Y
###### [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
PING6(56=40+8+8 bytes) ::1 --> ::1
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=0 hlim=64 dst=::1 time=0.541 ms
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1 time=0.261 ms
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1 time=0.379 ms
--- ::1 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.261/0.394/0.541/0.115 ms
######
Did this work? [Y/n] Y
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a02:8204:d600:66::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING6(56=40+8+8 bytes) 2a02:8204:d600:66::2 --> 2a02:8204:d600:66::2
--- 2a02:8204:d600:66::2 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
######
Did this work? [Y/n] n
toby@Tobys-Mac-mini:~$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_HWTAGGING>
ether a8:20:66:11:2f:8a
inet6 fe80::aa20:66ff:fe11:2f8a%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
media: autoselect (100baseTX <full-duplex,flow-control>)
status: active
en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 20:c9:d0:8f:ee:65
media: autoselect (<unknown type>)
status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
ether 02:c9:d0:8f:ee:65
media: autoselect
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:3e:e1:ff:fe:94:b4:02
media: autoselect <full-duplex>
status: inactive
tun0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1280
inet6 fe80::aa20:66ff:fe11:2f8a%tun0 prefixlen 64 scopeid 0x8
inet6 2a02:8204:d600:66::2 --> 2a02:8204:d600:66::1 prefixlen 128
open (pid 20605)
toby@Tobys-Mac-mini:~$ uname -a
Darwin Tobys-Mac-mini.local 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64
toby@Tobys-Mac-mini:~$ netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 17 0 en0
127 127.0.0.1 UCS 0 2 lo0
127.0.0.1 127.0.0.1 UH 441 15677263 lo0
169.254 link#4 UCS 0 0 en0
192.168.1 link#4 UCS 2 0 en0
192.168.1.1 0:22:b0:93:b6:c7 UHLWIir 19 1007 en0 1200
192.168.1.2 127.0.0.1 UHS 1 31 lo0
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 7 en0
Internet6:
Destination Gateway Flags Netif Expire
default 2a02:8204:d600:66::1 UGSc tun0
::1 link#1 UHL lo0
2a02:8204:d600:66::1 2a02:8204:d600:66::2 UHr tun0
2a02:8204:d600:66::2 link#8 UHL lo0
fe80::%lo0/64 fe80::1%lo0 UcI lo0
fe80::1%lo0 link#1 UHLI lo0
fe80::%en0/64 link#4 UCI en0
fe80::1%en0 74:31:70:fa:5e:dc UHLWIi en0
fe80::aa20:66ff:fe11:2f8a%en0 a8:20:66:11:2f:8a UHLI lo0
fe80::%en1/64 link#5 UCI en1
fe80::%tun0/64 fe80::aa20:66ff:fe11:2f8a%tun0 UcI tun0
fe80::aa20:66ff:fe11:2f8a%tun0 link#8 UHLI lo0
ff01::%lo0/32 fe80::1%lo0 UmCI lo0
ff01::%en0/32 link#4 UmCI en0
ff01::%en1/32 link#5 UmCI en1
ff01::%tun0/32 fe80::aa20:66ff:fe11:2f8a%tun0 UmCI tun0
ff02::%lo0/32 fe80::1%lo0 UmCI lo0
ff02::%en0/32 link#4 UmCI en0
ff02::%en1/32 link#5 UmCI en1
ff02::%tun0/32 fe80::aa20:66ff:fe11:2f8a%tun0 UmCI tun0
tunnel is not responding
Jeroen Massar on Monday, 01 April 2013 06:52:42
Did you check your firewall settings on both the apparently two NAT boxes that you have and the local host?
The live status indicates that the tunnel is working btw.
tunnel is not responding
Shadow Hawkins on Monday, 01 April 2013 07:12:33
I missed that point that the tunnel host has to be the DMZ host.
I can't do that because i have no access to the first nat box.
tunnel is not responding
Shadow Hawkins on Monday, 01 April 2013 07:37:08
nevermind, it's working now somehow
tunnel is not responding
Jeroen Massar on Monday, 01 April 2013 07:38:06
AYIYA tunnels do not care about being the first host, this as it is UDP, thus as long as the NAT supports UDP (which is a default) and the AYIYA port is not blocked somewhere it should just work.
Posting is only allowed when you are logged in. |