SixXS::Sunset 2017-06-06

Connectivity problem
[fi] Carmen Sandiego on Thursday, 20 May 2004 12:26:38
My tunnel worked very fine about 40 days. Now it's working sometime and then stop working. I will paste some ping and tcpdump here: only4fun ipv6 # tcpdump -i sixxs tcpdump: WARNING: sixxs: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on sixxs, link-type RAW (Raw IP), capture size 96 bytes 13:19:38.871231 linz.irc.at.ircd > only4fun.org.33257: P 3052147533:3052147606(73) ack 2037153399 win 4880 13:19:38.871275 only4fun.org.33257 > linz.irc.at.ircd: . ack 73 win 32940 13:19:38.989252 linz.irc.at.ircd > only4fun.org.33257: P 73:253(180) ack 1 win 4880 13:19:38.989299 only4fun.org.33257 > linz.irc.at.ircd: . ack 253 win 32940 13:19:46.468130 only4fun.org.33257 > linz.irc.at.ircd: P 1:37(36) ack 253 win 32940 13:19:46.587719 linz.irc.at.ircd > only4fun.org.33257: . ack 37 win 4880 13:19:46.587760 only4fun.org.33257 > linz.irc.at.ircd: P 37:55(18) ack 253 win 32940 13:19:46.704615 linz.irc.at.ircd > only4fun.org.33257: . ack 55 win 4880 13:19:46.704657 only4fun.org.33257 > linz.irc.at.ircd: P 55:91(36) ack 253 win 32940 13:19:46.820909 linz.irc.at.ircd > only4fun.org.33257: . ack 91 win 4880 13:19:46.857250 linz.irc.at.ircd > only4fun.org.33257: P 253:293(40) ack 91 win 4880 13:19:46.857286 only4fun.org.33257 > linz.irc.at.ircd: . ack 293 win 32940 13:19:49.343480 only4fun.org.33257 > linz.irc.at.ircd: P 91:131(40) ack 293 win 32940 13:19:49.459677 linz.irc.at.ircd > only4fun.org.33257: . ack 131 win 4880 13:20:28.361236 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:20:28.361271 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 13:20:32.201774 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:20:32.201808 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 13:20:36.056175 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:20:36.056214 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 13:20:37.798083 linz.irc.at.ircd > only4fun.org.33257: P 293:358(65) ack 131 win 4880 13:20:37.798124 only4fun.org.33257 > linz.irc.at.ircd: . ack 358 win 32940 13:20:37.918031 linz.irc.at.ircd > only4fun.org.33257: P 358:580(222) ack 131 win 4880 13:20:37.918070 only4fun.org.33257 > linz.irc.at.ircd: . ack 580 win 32940 13:20:39.857974 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:20:39.858008 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 13:20:39.991356 only4fun.org.33257 > linz.irc.at.ircd: P 131:149(18) ack 580 win 32940 13:20:40.105897 linz.irc.at.ircd > only4fun.org.33257: . ack 149 win 4880 13:20:40.207752 linz.irc.at.ircd > only4fun.org.33257: P 580:620(40) ack 149 win 4880 13:20:40.207792 only4fun.org.33257 > linz.irc.at.ircd: . ack 620 win 32940 13:20:43.694441 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:20:43.694480 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 13:20:46.187580 linz.irc.at.ircd > only4fun.org.33257: P 620:749(129) ack 149 win 4880 13:20:46.187624 only4fun.org.33257 > linz.irc.at.ircd: . ack 749 win 32940 13:20:47.516227 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:20:47.516262 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 13:20:51.350226 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:20:51.350262 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 13:21:29.501147 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:21:29.501186 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 13:21:33.311105 gw-76.hel-01.fi.sixxs.net > cl-76.hel-01.fi.sixxs.net: icmp6: echo request seq 23552 13:21:33.311142 cl-76.hel-01.fi.sixxs.net > gw-76.hel-01.fi.sixxs.net: icmp6: echo reply seq 23552 42 packets captured 42 packets received by filter 0 packets dropped by kernel And ping6 to my pop: From ::1 icmp_seq=15 Destination unreachable: Address unreachable From ::1 icmp_seq=16 Destination unreachable: Address unreachable From ::1 icmp_seq=17 Destination unreachable: Address unreachable From ::1 icmp_seq=18 Destination unreachable: Address unreachable From ::1 icmp_seq=19 Destination unreachable: Address unreachable From ::1 icmp_seq=20 Destination unreachable: Address unreachable From ::1 icmp_seq=21 Destination unreachable: Address unreachable From ::1 icmp_seq=22 Destination unreachable: Address unreachable From ::1 icmp_seq=23 Destination unreachable: Address unreachable From ::1 icmp_seq=24 Destination unreachable: Address unreachable From ::1 icmp_seq=25 Destination unreachable: Address unreachable From ::1 icmp_seq=26 Destination unreachable: Address unreachable From ::1 icmp_seq=27 Destination unreachable: Address unreachable From ::1 icmp_seq=28 Destination unreachable: Address unreachable From ::1 icmp_seq=29 Destination unreachable: Address unreachable From ::1 icmp_seq=30 Destination unreachable: Address unreachable From ::1 icmp_seq=31 Destination unreachable: Address unreachable 64 bytes from 2001:14b8:100:4b::1: icmp_seq=31 ttl=64 time=34.5 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=32 ttl=64 time=33.3 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=33 ttl=64 time=34.4 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=34 ttl=64 time=34.6 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=35 ttl=64 time=34.0 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=36 ttl=64 time=33.8 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=37 ttl=64 time=34.3 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=38 ttl=64 time=34.1 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=39 ttl=64 time=34.0 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=40 ttl=64 time=33.8 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=41 ttl=64 time=33.1 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=42 ttl=64 time=38.1 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=43 ttl=64 time=33.9 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=44 ttl=64 time=33.7 ms 64 bytes from 2001:14b8:100:4b::1: icmp_seq=45 ttl=64 time=35.1 ms From ::1 icmp_seq=47 Destination unreachable: Address unreachable From ::1 icmp_seq=48 Destination unreachable: Address unreachable From ::1 icmp_seq=49 Destination unreachable: Address unreachable From ::1 icmp_seq=50 Destination unreachable: Address unreachable time: 0 May 13:24:58 ntpdate[25061]: adjust time server 130.233.224.2 offset -0.042518 sec i haven't modified any config and have tryed this tunnel in 3 different computer's always same problem. I don't know anymore what to do. If someone knows please help me ;)
Connectivity problem
[fi] Carmen Sandiego on Thursday, 20 May 2004 14:23:36
Problem seems to be in heartbeat. Before it worked fine if hb_sendinterval is 60 Now even i put it 15 I get's couple of "address unreachable" Really don't what to do besides lower the hb_sendinterval value.
Connectivity problem
[ch] Jeroen Massar SixXS Staff on Thursday, 20 May 2004 14:35:39
a) From the main forum page: Operational issues, abuse and other questions should be directed to the contact address. b) Fix your clock and your connectivity. Apparently you have a lot of packetloss in IPv4 Lowering the hb_sendinterval doesn't make sense unless you expect the connection to change every n seconds. The server will actually ignore anything that is less than 60 seconds. Thus it will cause a lot of useless traffic.
Connectivity problem
[fi] Carmen Sandiego on Thursday, 20 May 2004 16:50:19
Don't know about packet loss. like i say 3 diffenrent computers and 3 different internet connection, every machine got synced time etc.. so how the problem can be a) my ipv4 packet loss? b) my clock? And yes it really helped when changed the timeinterval to 15 sec. I know that because i change it back to 60sec and packet loss is then much higher. And can't mail to info@sixxs.net because i have pete@only4fun.org in my 6bone handle and that computer has broken motherboard.
Connectivity problem
[ch] Jeroen Massar SixXS Staff on Thursday, 20 May 2004 17:11:27
Do you have any NAT or connection tracking activated as this more looks like that packets going to your system get dropped: 18:08:38.447279 213.216.248.235 > 62.78.96.38: icmp: 213.216.248.235 protocol 41 unreachable I suggest you fix your firewall and/or tunnel system and not do something foolish like the above. Heartbeats are only useful for notification of changing IP's and extending the lifetime of the tunnel configuration, they don't help with anything else. In your case though your NAT connection tracking might not loose the relation because it is updated every once in a while. Read the FAQ there is an entry there about that case. You can't read your mail because there is only one computer handling it? :) Never heared of a real mail setup (2x MX etc)... you also hopefully realize that you can't read your email and thus in the event that a notification has been sent to you about matters that you can't read it...
Connectivity problem
[ch] Jeroen Massar SixXS Staff on Thursday, 20 May 2004 17:26:27
haha, I've found your problem. You might want to run the heartbeat client from *1* PC and not two! ;) Now that is REALLY stupid.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker