|
IPv6 Heartbeat tunnel problems!
![[be]](/s/countries/be.gif) Shadow Hawkins on Thursday, 15 April 2004 21:38:35
<snip>
IPv6 Heartbeat tunnel problems!
Shadow Hawkins on Saturday, 06 December 2003 00:58:37
Here is also a snippet of tethereal:
0.000000 192.168.123.191 -> 0-1pool37-82.nas4.saint-louis1.mo.us.da.qwest.net TCP 2925 > 6699 [ACK] Seq=2768498084 Ack=2992546962 Win=17520 Len=0
0.008410 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 191.123.168.192.in-addr.arpa
0.017065 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
0.017955 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 82.37.157.63.in-addr.arpa
0.030338 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR 0-1pool37-82.nas4.saint-louis1.mo.us.da.qwest.net
0.033370 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 148.123.168.192.in-addr.arpa
0.043059 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
0.043541 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 3.131.130.195.in-addr.arpa
0.050459 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR hass.momus.telenet-ops.be
4.592672 192.168.123.176 -> orders14.taltrade.com TCP 1354 > 1724 [PSH, ACK] Seq=3376427085 Ack=3734233890 Win=64166 Len=16
4.596932 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 176.123.168.192.in-addr.arpa
4.621312 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
4.621819 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 29.61.75.63.in-addr.arpa
4.629857 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR orders14.taltrade.com
5.007888 UNEX_01:f5:7c -> US_a8:2e:19 ARP Who has 192.168.123.254? Tell 192.168.123.148
5.008335 US_a8:2e:19 -> UNEX_01:f5:7c ARP 192.168.123.254 is at 00:c0:49:a8:2e:19
5.008623 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 254.123.168.192.in-addr.arpa
5.038205 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
6.148010 192.168.123.176 -> nchass01.telenet-ops.be TCP 3436 > webcache [SYN] Seq=414291014 Ack=0 Win=60352 Len=0
6.151480 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 102.83.224.213.in-addr.arpa
6.215790 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR nchass01.telenet-ops.be
6.661873 192.168.123.176 -> nchass01.telenet-ops.be TCP 3436 > webcache [FIN, ACK] Seq=414291593 Ack=2461055062 Win=63875 Len=0
7.074649 192.168.123.176 -> nchass01.telenet-ops.be TCP 3440 > webcache [SYN] Seq=414699075 Ack=0 Win=60352 Len=0
7.077785 192.168.123.176 -> nchass01.telenet-ops.be TCP 3441 > webcache [SYN] Seq=414737952 Ack=0 Win=60352 Len=0
7.322878 192.168.123.176 -> nchass01.telenet-ops.be TCP 3440 > webcache [FIN, ACK] Seq=414699626 Ack=2478284221 Win=64216 Len=0
8.545667 192.168.123.176 -> sbnews25.taltrade.com TCP 2915 > 1724 [ACK] Seq=3837518342 Ack=1585980923 Win=64053 Len=0
8.547909 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 217.60.75.63.in-addr.arpa
8.562979 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR sbnews25.taltrade.com
10.552319 192.168.123.176 -> sbquote229.taltrade.com TCP 3107 > 1724 [ACK] Seq=4202123604 Ack=1093385587 Win=64170 Len=0
10.554548 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 248.62.75.63.in-addr.arpa
10.574818 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR sbquote229.taltrade.com
15.390457 192.168.123.176 -> sboptreco05.taltrade.com TCP 3106 > 1724 [PSH, ACK] Seq=4202002160 Ack=17846063 Win=63878 Len=16
15.393236 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 25.62.75.63.in-addr.arpa
15.402535 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR sboptreco05.taltrade.com
17.976928 192.168.123.176 -> sbperms14.taltrade.com TCP 1336 > 1724 [ACK] Seq=3364289392 Ack=127869257 Win=65311 Len=0
17.979220 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 222.60.75.63.in-addr.arpa
18.036179 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR sbperms14.taltrade.com
21.258472 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query A nlams01.sixxs.net
21.273243 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response CNAME broker01.ams.nl.sixxs.net A 213.197.27.252
21.274510 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query A neimod.gotdns.org
21.443169 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response A 213.118.132.46
21.443478 192.168.123.148 -> broker01.ams.nl.sixxs.net UDP Source port: 1073 Destination port: 3740
25.156992 192.168.123.191 -> cae168-195-152.sc.rr.com TCP 2918 > 6699 [PSH, ACK] Seq=2073623131 Ack=3326966300 Win=16176 Len=105
25.160163 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 152.195.168.24.in-addr.arpa
25.174536 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR cae168-195-152.sc.rr.com
27.809547 192.168.123.176 -> sboptreco11.taltrade.com TCP 1359 > 1724 [ACK] Seq=3381448181 Ack=1393371022 Win=64139 Len=0
27.812295 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 207.62.75.63.in-addr.arpa
27.826559 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR sboptreco11.taltrade.com
28.212788 192.168.123.176 -> orders14.taltrade.com TCP 1354 > 1724 [ACK] Seq=3376427117 Ack=3734233918 Win=64159 Len=0
29.518804 192.168.123.176 -> sbnews25.taltrade.com TCP 2915 > 1724 [ACK] Seq=3837518358 Ack=1585980936 Win=64050 Len=0
29.669790 192.168.123.176 -> sbreco34.taltrade.com TCP 3113 > 1724 [PSH, ACK] Seq=4202509862 Ack=195337868 Win=64078 Len=16
29.669847 192.168.123.176 -> sbquote229.taltrade.com TCP 3107 > 1724 [PSH, ACK] Seq=4202123604 Ack=1093385678 Win=64148 Len=16
29.672970 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 159.62.75.63.in-addr.arpa
29.695467 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response PTR sbreco34.taltrade.com
30.719974 192.168.123.176 -> sbquote229.taltrade.com TCP 3107 > 1724 [ACK] Seq=4202123620 Ack=1093385763 Win=64126 Len=0
32.167236 192.168.123.191 -> cae168-195-152.sc.rr.com TCP 2918 > 6699 [PSH, ACK] Seq=2073623366 Ack=3326966542 Win=17400 Len=104
34.173977 192.168.123.191 -> cae168-195-152.sc.rr.com TCP 2918 > 6699 [PSH, ACK] Seq=2073623470 Ack=3326966542 Win=17400 Len=160
35.852383 192.168.123.191 -> cae168-195-152.sc.rr.com TCP 2918 > 6699 [ACK] Seq=2073623769 Ack=3326966612 Win=17330 Len=0
36.405112 192.168.123.176 -> sboptreco05.taltrade.com TCP 3106 > 1724 [PSH, ACK] Seq=4202002176 Ack=17846075 Win=63875 Len=16
36.854871 192.168.123.191 -> 0-1pool37-82.nas4.saint-louis1.mo.us.da.qwest.net TCP 2925 > 6699 [PSH, ACK] Seq=2768498148 Ack=2992564222 Win=17520 Len=8
38.639957 192.168.123.124 -> 192.168.123.255 NBNS Name query NB PC1 <20>
38.640162 MOTOTECH_5e:46:eb -> ff:ff:ff:ff:ff:ff ARP Who has 192.168.123.124? Tell 192.168.123.191
38.721122 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 124.123.168.192.in-addr.arpa
38.765549 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
38.766189 192.168.123.148 -> hass.momus.telenet-ops.be DNS Standard query PTR 255.123.168.192.in-addr.arpa
38.790418 hass.momus.telenet-ops.be -> 192.168.123.148 DNS Standard query response, No such name
39.046758 192.168.123.176 -> sbperms14.taltrade.com TCP 1336 > 1724 [ACK] Seq=3364289408 Ack=127869273 Win=65295 Len=0
39.257376 192.168.123.191 -> cae168-195-152.sc.rr.com TCP 2918 > 6699 [ACK] Seq=2073623873 Ack=3326966733 Win=17209 Len=0
40.778147 192.168.123.124 -> 192.168.123.255 NBNS Name query NB PC4 <20>
40.824355 UNEX_01:f5:7c -> ff:ff:ff:ff:ff:ff ARP Who has 192.168.123.124? Tell 192.168.123.148
40.824474 UNEX_01:f6:3e -> UNEX_01:f5:7c ARP 192.168.123.124 is at 00:10:a7:01:f6:3e
40.824531 192.168.123.148 -> 192.168.123.124 NBNS Name query response NB 192.168.123.148
40.824721 192.168.123.124 -> 192.168.123.148 TCP 1414 > netbios-ssn [SYN] Seq=6095390 Ack=0 Win=8192 Len=0
40.824854 192.168.123.148 -> 192.168.123.124 TCP netbios-ssn > 1414 [SYN, ACK] Seq=2374574240 Ack=6095391 Win=5840 Len=0
40.825853 192.168.123.124 -> 192.168.123.148 TCP 1414 > netbios-ssn [ACK] Seq=6095391 Ack=2374574241 Win=8760 Len=0
40.825860 192.168.123.124 -> 192.168.123.148 NBSS Session request
40.825995 192.168.123.148 -> 192.168.123.124 TCP netbios-ssn > 1414 [ACK] Seq=2374574241 Ack=6095463 Win=5840 Len=0
IPv6 Heartbeat tunnel problems!
You might really want to apply filters to your tcpdump query and use -n to only use IP addresses, the above really has too much garbage in it that is completely irrelevant.
IPv6 Heartbeat tunnel problems!
<SNIP>
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 <SNIP>
debian:~# ip tun sho sit0: ipv6/ip remote any local any ttl 64 nopmtudisc sixxs: ipv6/ip remote 213.197.27.252 local 213.118.132.46 ttl inherit
Your local endpoint is set to an address that is not configured on your machine. Thus any packet can't be sent out of your machine and even if it did that it wouldn't be matched when it came back.
You might want to set the following two flags:
# Special case for people having their
# endpoint behind a NAT
hb_behindnat 1
#
# Don't change the local tunnel endpoint
hb_statictunnel 1
And you can comment "ipv4_local_resolve" parameter then.
You will also still have to set your NATbox to forward proto-41 packets to this internal host.
IPv6 Heartbeat tunnel problems!
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 03 January 2004 01:53:59
Hi,
not sure if you already solved the problem. If yes, just ignore this post...
I set my tunnel up today and had some problems with first setup, too. My iptables firewall was already okay (allowing UDP 3740 outgoing - restricted to dest POP IP).
But the default route wasn't setup correctly when using the command shown on the webpage. I already had two "::/0"-routes to eth0 and eth1 with metric 256 - the sixxs "default" route was added with metric 1024 (is this the default when o parameter is given?). So no ping6 etc. worked at first.
Changing the route didn't work well because a second one was created. So I had to delete the ::/0-routes for dev sixxs and set up a new one with metric 128... and it worked:-)
HTH... at least for somebody who will suffer the same things when trying to setup a tunnel.
Greetz,
Wolfgang
IPv6 Heartbeat tunnel problems!
If you have default routes on your eth0 and eth1, don't you have native connectivity in place already? Next to that it is all to blame on yourself.. check your routes ;) The heartbeat program doesn't touch those.
IPv6 Heartbeat tunnel problems!
Shadow Hawkins on Sunday, 04 January 2004 02:22:59
Hi Jeroen,
seems as if these two routes were some relicts of the very _slow_ freenet6 tunnel I tried before;)
After changing my (dynamic) IPv4 this evening (without any heartbeart problems :-) some ipv6 routes (including those waste ::/0 routes for eth0 and eth1) disappeared from my routing tables without any emerging problems.
Since my routing table looks quite fine now, I think this problem was kind of typical 'startup' or 'migrating' problem some others also had (or will have)...
Nevertheless thx for your help,
Wolfgang
|
![[ch]](/s/countries/ch.gif)
on Saturday, 06 December 2003 12:35:35
Posting is only allowed when you are