Linux - Kernel 2.6.5 Tunnel Problem
Shadow Hawkins on Wednesday, 28 April 2004 01:22:59
Hi,
i'm running the following setup script to start the inital
ipv6-over-ipv4 tunnel, after I've launched my internet connection.
#!/bin/sh
ip tunnel add sixxs mode sit local $LOCAL_IP remote 212.224.0.188
ip link set sixxs up
ip link set mtu 1280 dev sixxs
ip tunnel change sixxs ttl 64
ip -6 add add 2001:6f8:900:1fc::2/64 dev sixxs
ip -6 route add default via 2001:6f8:900:1fc::1 dev sixxs
heartbeat-client /etc/heartbeat/heartbeat.conf
I can't ping the gateway.
penguin1:/home/jens# ping6 2001:6f8:900:1fc::1
PING 2001:6f8:900:1fc::1(2001:6f8:900:1fc::1) from 2001:6f8:900:1fc::2 : 56 data bytes
--- 2001:6f8:900:1fc::1 ping statistics ---
13 packets transmitted, 0 received, 100% loss, time 11998ms
Simulatanously I ran tethereal - here the output.
penguin1:/etc/heartbeat# tethereal -i ppp0 proto 41
Capturing on ppp0
0.000000 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
0.999852 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
1.999652 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
2.999774 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
3.999392 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
4.999227 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
5.999124 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
6.998959 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
7.998738 cl-509.muc-01.de.sixxs.net -> gw-509.muc-01.de.sixxs.net ICMPv6 Echo request
I don't get any ipv6 replies from gw-509.muc-01.de.sixxs.net!
The heartbeat client is running, the lastest syslog entry:
heartbeat-client: [HB] HEARTBEAT TUNNEL 2001:6f8:900:1fc::2 217.236.160.106 1083122276 5 ***password***
Here's my heartbeat.conf
# Configuration for SixXS Heartbeat Client
# SixXS - http://www.sixxs.net
#
# Commentlines start with semicolon (;), hash (#),
# double slash (//) or a space ( ).
# Empty lines are ignored.
# Argument values may be quoted using single (') and double (") quotes.
#
# examples:
# os linux
# os "linux"
# os 'linux'
# Operating System (linux/freebsd/openbsd/netbsd/winxp)
os "linux"
# Interface the tunnel should go over
# used for detecting the local IPv4 endpoint
ipv4_interface "ppp0"
# IPv4 address of the POP (nlams01/nlams02/nlams04/demun01/iedub01/dkcop01)
# This is also the address to where heartbeats are sent
ipv4_pop "demuc01.sixxs.net"
# ipv4_local is figured out automatically
# from the ipv4_interface
# Special case for people having their
# endpoint behind a NAT
# hb_behindnat 1
#
# Don't change the local tunnel endpoint
#hb_statictunnel 1
#
# The hostname or IP of the 'external' IP
# from which the heartbeat should originate
# Note that mismatching IP's will be dropped
#ipv4_local_resolve public-ip.example.net
# Interface to be used for the tunnel
# will be created on the OS's that need that
ipv6_interface "sixxs"
# The local and remote sides of the tunnel
ipv6_pop "2001:6f8:900:1fc::1"
ipv6_local "2001:6f8:900:1fc::2"
# The prefix length of the tunnel
# Tunnel space is thus ipv6_pop/ipv6_prefixlen
ipv6_prefixlen 64
# The Heartbeat password for this tunnel
hb_password "***password***"
# The interval at which to send the heartbeat
hb_sendinterval 60
# Informational: after this timeout the tunnel
# is taken down at the POP side
hb_timeout 300
# Put the client in the background? (default)
# Set to 0 to keep in foreground, eg for daemontools
# Non-daemonized will also cause logs to be send to stdout
daemonize 1
and ip -6 route shows:
2001:6f8:900:1fc::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth2 metric 256 mtu 1500 advmss 1220
fe80::/64 dev dummy0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth2 metric 256 mtu 1500 advmss 1220
ff00::/8 dev dummy0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220
default via 2001:6f8:900:1fc::1 dev sixxs metric 1024 mtu 1280 advmss 1220
I don't have any ideas! I've tried an other tunnel broker, and it worked without
any problems! So it cannot be an firewall issue!
Greetings
Jens
Linux - Kernel 2.6.5 Tunnel Problem
Shadow Hawkins on Wednesday, 28 April 2004 01:25:49
Additionally I tried http://www.ipv6-net.org a German IPv6 information site
and I was not able to ping my gateway from there 2001:6f8:900:1fc::1
My problem occured after updateing from kernel 2.4.22 to 2.6.5.
Linux - Kernel 2.6.5 Tunnel Problem
Shadow Hawkins on Wednesday, 28 April 2004 01:31:19
Have you checked, that your clock is not off by more than 120 seconds?
Kind regards
Lars Ehrhardt
Linux - Kernel 2.6.5 Tunnel Problem
Shadow Hawkins on Wednesday, 28 April 2004 02:01:50
I found my problem:
I was using an NTP server with an incorrect time! The NTP server reported me the
current time plus something about 4 hous! *grrrr* I wrote an email to the
admin and switched over to an other NTP server, and now it's working again.
Thanks
Jens
Posting is only allowed when you are logged in. |