|
Heartbeat Tunnel on Gentoo
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Saturday, 18 December 2004 12:15:30
Hello there all.
I have configured my gentoo-laptop with an ipv6-heartbeat tunnel using aiccu.
I used the ebuild from the tar.gz and started aiccu after editing the config file.
My logs tell me that aiccu started correctly and the verbose output shows that it has retrieved the right tunnel including the right information. But my tunnel doesnt work...
Aiccu itself created the sixxs-device and thus it should be able to go on the net. But I can't even reach my ipv6-endpoint.
When I ping the endpoint from my server (which has a static-ipv6-tunnel) I get a Destination Unreachable notice from another ipv6-address.
The tunnel is a scarlet-internet POP (but I had the same problem before with a Concepts-ICT POP) at the address 2001:610:600:1f::1 and the Destionation Unreachable notification comes from the address 2001:610:1:80bb:192:87:1202:107.
I am sure it is me that is doing something wrong (cuz I had the same problem with 2 different pops) But I cant seem to find out what it is im doing wrong.
-IPV6-kernel support is available (the laptop works on ipv6 in my network behind my static-tunnel-server)
-Aiccu is installed.
This is the aiccu output:
Tunnel Information for T4689:
POP Id : nlams05
IPv6 Local : 2001:610:600:1f::2/64
IPv6 Remote : 2001:610:600:1f::1/64
Tunnel Type : 6in4-heartbeat
Adminstate : enabled
Userstate : enabled [ ok ]
and this is the config file (though not much can be wrecked here...)
# AICCU Configuration
# Login information
username user-id
password passwd
# Interface names to use
ipv4_interface eth0
ipv6_interface sixxs
# The tunnel_id to use
# (only required when there are multiple tunnels in the list)
tunnel_id T4689
# Be verbose?
verbose true
# Daemonize?
daemonize true
# Automatic?
automatic true
What can be wrong...? As I said, ipv6 works when it gets an address from my router, but when I start a heartbeat tunnel it doesnt. (I would like it to cuz its a laptop u know :))
Heartbeat Tunnel on Gentoo
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 18 December 2004 13:06:06
You should look a two things:
1. Is your clock in sync?
2. Are you behind a NAT-router that doesn't forward Proto-41-packets?
Also look at the syslog for more infos...
Greets
Thorsten
Heartbeat Tunnel on Gentoo
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Tuesday, 04 January 2005 10:51:27
<edit>
It seems there already was a thread about this same problem I have with the same pop I have, so you probably may ignore me here =)
</edit>
I have (I think) the same poblem wih my gentoo (2.6 kernel) / aiccu heartbeat setup. Aiccu starts ok but when i run 'aiccu autotest' it works only until step 6:
###### [6/8] Ping the IPv6 Remote/POP Inner Tunnel Endpoint (2001:14b8:100:113::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:113::1(2001:14b8:100:113::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:113::1 ping statistics ---
3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1998ms
and of course the rest of the test doesn't work.
This is what aiccu tells as tunnel's properties (and they're correct):
Tunnel Information for T5631:
POP Id : fihel01
IPv6 Local : 2001:14b8:100:113::2/64
IPv6 Remote : 2001:14b8:100:113::1/64
Tunnel Type : 6in4-heartbeat
Adminstate : enabled
Userstate : enabled
This is what 'ip -6 route show' says when aiccu is started:
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220 metric10 64
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 metric10 64
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 64
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220 metric10 1
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 metric10 1
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 1
default via 2001:14b8:100:113::1 dev sixxs metric 1024 mtu 1280 advmss 1220 metric10 64
I do have iptables set up but this same thing happens if I disable the firewall.
I've done all sorts of things to get this working but haven't succeeded..
|
Posting is only allowed when you are