Can't get tunnel to work on Slackware 10
![]()
Hi, i'm using Slackware 10 and can't get my tunnel working, first i type aiccu start and it doesn't give any errors, then i did aiccu autotest > aiccu.log
and heres my aiccu log:
----cut---
######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (80.220.195.90)
### 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 80.220.195.90 (80.220.195.90) 56(84) bytes of data.
64 bytes from 80.220.195.90: icmp_seq=1 ttl=64 time=0.144 ms
64 bytes from 80.220.195.90: icmp_seq=2 ttl=64 time=0.100 ms
64 bytes from 80.220.195.90: icmp_seq=3 ttl=64 time=0.067 ms
--- 80.220.195.90 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.067/0.103/0.144/0.033 ms
######
####### [2/8] Ping the IPv4 Remote/POP Outer Endpoint (62.78.96.38)
### 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 62.78.96.38 (62.78.96.38) 56(84) bytes of data.
64 bytes from 62.78.96.38: icmp_seq=1 ttl=59 time=31.4 ms
64 bytes from 62.78.96.38: icmp_seq=2 ttl=59 time=29.0 ms
64 bytes from 62.78.96.38: icmp_seq=3 ttl=59 time=31.0 ms
--- 62.78.96.38 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2014ms
rtt min/avg/max/mdev = 29.087/30.502/31.412/1.014 ms
######
####### [3/8] Traceroute to the POP (62.78.96.38) 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 62.78.96.38 (62.78.96.38), 30 hops max, 38 byte packets
1 hkimmlgw7.dsl.inet.fi (80.222.96.1) 26.258 ms 25.867 ms 26.566 ms
2 141.208.207.145 (141.208.207.145) 26.297 ms 26.289 ms 26.418 ms
3 141.208.205.214 (141.208.205.214) 26.493 ms 26.035 ms 26.299 ms
4 finnet.ficix2-ge.ficix.fi (193.110.224.20) 26.435 ms 34.499 ms 26.428 ms
5 van5r1.kv9.net (217.78.198.90) 26.463 ms 27.880 ms 28.084 ms
6 sixxs-gw.kv9.net (62.78.96.38) 29.766 ms 29.579 ms 29.743 ms
######
###### [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
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.088 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.041 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.040 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.040/0.056/0.088/0.023 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:14b8:100:111::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:14b8:100:111::2(2001:14b8:100:111::2) 56 data bytes
64 bytes from 2001:14b8:100:111::2: icmp_seq=1 ttl=64 time=0.084 ms
64 bytes from 2001:14b8:100:111::2: icmp_seq=2 ttl=64 time=0.074 ms
64 bytes from 2001:14b8:100:111::2: icmp_seq=3 ttl=64 time=0.040 ms
--- 2001:14b8:100:111::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.040/0.066/0.084/0.018 ms
######
###### [6/8] Ping the IPv6 Remote/POP Inner Tunnel Endpoint (2001:14b8:100:111::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 of course
### If the previous test was succesful then this could be both
### a firealling and a routing/interface problem
PING 2001:14b8:100:111::1(2001:14b8:100:111::1) 56 data bytes
From ::1 icmp_seq=2 Destination unreachable: Address unreachable
From ::1 icmp_seq=3 Destination unreachable: Address unreachable
--- 2001:14b8:100:111::1 ping statistics ---
3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2010ms
######
###### [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.
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:14b8:100:111::2, 30 hops max, 16 byte packets
1 localhost (::1) 0.197 ms !H 0.175 ms !H *
######
###### [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
traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:14b8:100:111::2, 30 hops max, 16 byte packets
1 ::1 (::1) 0.223 ms !H 0.131 ms !H 0.118 ms !H
######
###### 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.
---cut---
i don't have firewall or nat, here my ifconfig output for sixxs interface:
-----cut-----
sixxs Link encap:UNSPEC HWaddr 50-DC-C3-5A-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::50dc:c35a/64 Scope:Link
inet6 addr: 2001:14b8:100:111::2/64 Scope:Global
inet6 addr: fe80::c0a8:42/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:1248 (1.2 Kb)
---cut-----
i will gladly answer to any further questions
Can't get tunnel to work on Slackware 10
![]()
What is the output of aiccu with the following settings:
verbose true
daemonize false
Can't get tunnel to work on Slackware 10
![]()
---cut----
sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)"
sock_printf() : "client TIC/draft-00 AICCU/2004.08.29-BETA2-gui Linux/2.4.26"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1104401117"
sock_printf() : "username OK5-6BONE"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 0af32dfec145d8b8440d662129205265"
sock_printf() : "authenticate md5 c2c0d1a52e8b9d9a308b6d6fd7c0f886"
sock_getline() : "200 Succesfully logged in using md5 as OK5-6BONE (Oskari Kantoniemi) from 80.220.195.90"
sock_printf() : "tunnel list"
sock_getline() : "201 Listing tunnels"
sock_getline() : "T5595 2001:14b8:100:111::2 heartbeat fihel01"
sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>"
sock_printf() : "tunnel show T5595"
sock_getline() : "201 Showing tunnel information for T5595"
sock_getline() : "TunnelId: T5595"
sock_getline() : "Type: 6in4-heartbeat"
sock_getline() : "IPv6 Endpoint: 2001:14b8:100:111::2"
sock_getline() : "IPv6 POP: 2001:14b8:100:111::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "POP Id: fihel01"
sock_getline() : "IPv4 Endpoint: heartbeat"
sock_getline() : "IPv4 POP: 62.78.96.38"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: 53d547cc528afea27a82c75b506435ee"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T5595
sock_printf() : "QUIT It was lovely talking to you again"
Tunnel Information for T5595:
POP Id : fihel01
IPv6 Local : 2001:14b8:100:111::2/64
IPv6 Remote : 2001:14b8:100:111::1/64
Tunnel Type : 6in4-heartbeat
Adminstate : enabled
Userstate : enabled
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Beat()
heartbeat_socket() - IPv4 : 62.78.96.38
[HB] HEARTBEAT TUNNEL 2001:14b8:100:111::2 sender 1104401119 91dffc7808359e9b03908a0f97cda7f4
Beat()
[HB] HEARTBEAT TUNNEL 2001:14b8:100:111::2 sender 1104401179 4d3d38dd56cd1326dcb8d83af42ce0e5
---cut---
Can't get tunnel to work on Slackware 10
![]()
i got the same prob also on slackware 10. aiccu output is alike. It just stopped working after reboot.
Can't get tunnel to work on Slackware 10
![]()
I have similar problems with fihel01 and I'm using Gentoo.
I just posted a long report to sixxs, let's see what they figure out of it.
Can't get tunnel to work on Slackware 10
![]()
Now my tunnel just simply started working again.
Don't why, how or what was wrong.
I haven't heard from sixxs yet.
Can't get tunnel to work on Slackware 10
![]()
I changed to debian just a week ago and i didn't work on it then, but today i tested the tunnel and it started to work! problem solved, but i hope it doesn't do this again.
Can't get tunnel to work on Slackware 10
![]()
ifconfig sixxs
sixxs Link encap:UNSPEC HWaddr 52-80-DA-D1-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::5280:dad1/128 Scope:Link
inet6 addr: 2001:14b8:100:70::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6181 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:3028564 (2.8 Mb)
Link encap:UNSPEC ? i think there's my problem. Just can't figure out how to fix it. Any ideas? ipv6 is now as a module in kernel but i get the same output when it's not. It has worked just fine almost an year or so. Now when rebooted it i get this: From ::1 icmp_seq=2 Destination unreachable: Address unreachable when pingin ipv6 pop endpoint or any other ipv6 address. Localhost is working.
Can't get tunnel to work on Slackware 10
![]()
First of all, "Link encap:UNSPEC" isn't the reason why your tunnel isn't working.
It simply means that you haven't specified any encapsulation for your tunnel.
If I were you I would start looking for the error in my routingtables.
With iproute2 installed, just run "ip -6 route add 2001::/3 dev sixxs" to route your ipv6 packages thru your tunneldevice sixxs.
And be sure to check with sysctl if "net.ipv6.all.forwarding = 1".
I hope this helps.
/Marcus
Can't get tunnel to work on Slackware 10
![]()
Count me in. I, too, have this problem. (gentoo, fihel01)
2005-01-04 EDIT:
My tunnel started working.
|