|
Problem with heartbeat tunnel take #3
![[be]](/s/countries/be.gif) Shadow Hawkins on Sunday, 07 December 2003 23:35:41
Ok, Jeroen, I tried those changes you suggested and still no go ;( .
if I uncomment or comment hb_behindnat, it's exactly the same, with the exception of "sender" or "213.118.132.46".
# Special case for people having their
# endpoint behind a NAT
hb_behindnat 1
#
then I get the following output from heartbeat-client:
debian:/etc/heartbeat# ./heartbeat-client heartbeat.conf
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 sender 1070835446 f28c68a32185e35b1dc1ddc7905bae9d
debian:~# cat /etc/heartbeat/heartbeat.conf
# Configuration for SixXS Heartbeat Client
# SixXS - http://www.sixxs.net
# Autogenerated by SixXS Website (http://www.sixxs.net)
# Created at 2003-12-05 22:31:10
#
# 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 "eth0"
# IPv4 address of the POP (nlams01/nlams02/nlams04/demun01/iedub01/dkcop01)
# This is also the address to where heartbeats are sent
ipv4_pop "nlams01.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
ipv4_local_resolve neimod.gotdns.org
# 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:838:300:66::1"
ipv6_local "2001:838:300:66::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 "******"
# The interval at which to send the heartbeat
hb_sendinterval 10
# 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
daemonize 0
debian:~# ip tun sho
sit0: ipv6/ip remote any local any ttl 64 nopmtudisc
sixxs: ipv6/ip remote 213.197.27.252 local 192.168.123.148 ttl inherit
debian:~# ip -6 addr sho
1: lo: <LOOPBACK,UP>
inet6 ::1/128 scope host
2: eth0: <BROADCAST,MULTICAST,UP> qlen 1000
inet6 fe80::210:a7ff:fe01:f57c/64 scope link
4: sixxs: <POINTOPOINT,NOARP,UP>
inet6 2001:838:300:66::2/64 scope global
inet6 fe80::c0a8:7b94/64 scope link
debian:~# ip -6 ro sho
2001:838:300:66::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
2000::/3 via 2001:838:300:66::1 dev sixxs metric 1024 mtu 1280 advmss 1220
fe80::/64 dev eth0 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 sixxs metric 256 mtu 1280 advmss 1220
default dev eth0 proto kernel metric 256 mtu 1500 advmss 1440
unreachable default dev lo proto none metric -1 error -101 advmss 1220
debian:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:10:A7:01:F5:7C
inet addr:192.168.123.148 Bcast:192.168.123.255 Mask:255.255.255.0
inet6 addr: fe80::210:a7ff:fe01:f57c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5664 errors:0 dropped:0 overruns:0 frame:0
TX packets:4020 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4180248 (3.9 MiB) TX bytes:873726 (853.2 KiB)
Interrupt:9 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:169 errors:0 dropped:0 overruns:0 frame:0
TX packets:169 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12550 (12.2 KiB) TX bytes:12550 (12.2 KiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:838:300:66::2/64 Scope:Global
inet6 addr: fe80::c0a8:7b94/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
debian:/etc/heartbeat# ./heartbeat-client heartbeat.conf
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 213.118.132.46 1070835740 f41178d916c4f797d46b2c43b9375f8d
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 213.118.132.46 1070835750 ed3fea0572b4ae9d22c4c774afb2dacc
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 213.118.132.46 1070835760 9390037d3f3686bcdf943bc04af951b9
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 213.118.132.46 1070835770 11ae7b41e542fb1111f190dc551d3591
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 213.118.132.46 1070835780 e9b9e8ed4e749b8a098a86af37158362
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 213.118.132.46 1070835790 3425f0e28788615f542dc166d6f05ccb
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 213.118.132.46 1070835800 c6f00951f09e4b53ada49f582d8763e7
[HB] HEARTBEAT TUNNEL 2001:838:300:66::2 213.118.132.46 1070835810 eff0f18f1276af41a5dbb4a9896c29ad
Here is a snippet of tethereal's output:
0.000000 2001:838:300:66::2 -> 2001:838:300:66::1 ICMPv6 Echo request
0.162984 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
0.196696 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
0.197980 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
0.209383 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
0.882374 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 148.123.168.192.in-addr.arpa
0.901861 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
0.902500 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 3.131.130.195.in-addr.arpa
0.912020 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR hass.momus.telenet-ops.be
1.018571 2001:838:300:66::2 -> 2001:838:300:66::1 ICMPv6 Echo request
1.019446 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
1.028260 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
1.031601 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
1.039167 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
1.409143 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query A nlams01.sixxs.net
1.641257 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response CNAME broker01.ams.nl.sixxs.net A 213.197.27.252
1.641962 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query A neimod.gotdns.org
1.648631 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response A 213.118.132.46
1.652142 192.168.123.148 -> broker01.ams.nl.sixxs.net UDP Source port: 1114 Destination port: 3740
2.018568 2001:838:300:66::2 -> 2001:838:300:66::1 ICMPv6 Echo request
2.019497 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
2.035046 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
2.035797 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
2.046129 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
3.018558 2001:838:300:66::2 -> 2001:838:300:66::1 ICMPv6 Echo request
3.019608 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
3.038703 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
3.039460 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
3.050951 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
4.018558 2001:838:300:66::2 -> 2001:838:300:66::1 ICMPv6 Echo request
4.019623 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
4.039289 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
4.040047 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
4.047934 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
5.018565 2001:838:300:66::2 -> 2001:838:300:66::1 ICMPv6 Echo request
5.019626 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.6.0.0.0.0.3.0.8.3.8.0.1.0.0.2.ip6.int
POP Description Concepts ICT BV
POP Location Amsterdam, Netherlands, The
POP IPv4 213.197.27.252
Your Location Genk, Belgium
Your IPv4 heartbeat
IPv6 Prefix 2001:838:300:66::1/64
POP IPv6 2001:838:300:66::1
Your IPv6 2001:838:300:66::2
Last Dead 2003-11-30 01:32:12
State Heartbeat
Heartbeat Password "******"
Heartbeat Configuration Client Configuration
Any ideas?
Thanks in advance
Problem with heartbeat tunnel take #3
The hb_behindnat flag, when enabled causes that not the local IP to be included but the special word 'sender' which then causes the POP to look at the IP the packet came from. As you have specified ipv4_local_resolve it will resolve that hostname and use that in the other case.
But your problem is quite simple: use NTP
This is mentioned with a nice big warning on the heartbeat page btw.
Problem with heartbeat tunnel take #3
Shadow Hawkins on Monday, 08 December 2003 18:13:06
Aha! I didn't know NTP synching was this important.
Maybe you should put it in big red letters ;).
Anyway, the heartbeat tunnel is working now!
Thank you so much Jeroen :*
|
![[ch]](/s/countries/ch.gif)
on Monday, 08 December 2003 00:20:23
Posting is only allowed when you are