Forum - [linux] Please help, this is getting frustrating :: SixXS

[linux] Please help, this is getting frustrating

Shadow Hawkins on Sunday, 02 May 2004 19:40:18

Please.......... I just hope this isn't a POP problem or I'll just give up entirely. My tunnel isn't working for more than 3 weeks, and I don't know why. This is my tunnel setup script:

ip tunnel add sixxs mode sit local 192.168.0.3 remote 81.92.202.9 ip link set sixxs up ip link set mtu 1280 dev sixxs ip tunnel change sixxs ttl 64 ip -6 addr add 2001:b18:2000:b::2/64 dev sixxs ip -6 route add default via 2001:b18:2000:b::1 dev sixxs

This is my heartbeat.conf:

os "linux" ipv4_interface "eth1" ipv4_pop "ptlis01.sixxs.net" hb_behindnat 1 ipv6_interface "sixxs" ipv6_pop "2001:b18:2000:b::1" ipv6_local "2001:b18:2000:b::2" ipv6_prefixlen 64 hb_password "<password>" hb_sendinterval 60 hb_timeout 300 daemonize 1 Routing: wizepc conf.d # ip -6 route 2001:b18:2000:b::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 metric10 64 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 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220 metric10 1 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 metric10 1 default via 2001:b18:2000:b::1 dev sixxs metric 1024 mtu 1280 advmss 1220 metric10 64

NAT box is forwarding protocol 41 to my ip (192.168.0.3). POP doesn't even respond to ping:

wizepc wizeman # tethereal -i eth1 proto 41 Capturing on eth1 0.000000 2001:b18:2000:b::2 -> 2001:b18:2000:b::1 ICMPv6 Echo request 0.999776 2001:b18:2000:b::2 -> 2001:b18:2000:b::1 ICMPv6 Echo request 1.999562 2001:b18:2000:b::2 -> 2001:b18:2000:b::1 ICMPv6 Echo request

And before you tell me... YES, I have the clock synchronized!!

wizepc conf.d # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== -veracity.mcc.ac 128.86.8.123 2 u 563 1024 377 227.419 23.585 47.701 -utserv.mcc.ac.u 193.63.106.104 2 u 228 1024 377 100.537 7.109 16.682 -swisstime.ee.et .PPS. 1 u 161 1024 377 216.803 -29.044 0.789 -ntp0.cis.strath 129.132.2.21 2 u 627 1024 377 115.971 1.844 17.052 +hora.cs.tu-berl .PPS. 1 u 568 1024 377 137.736 15.526 67.475 ntp2-rz.rrze.un .STEP. 16 u - 1024 0 0.000 0.000 4000.00 lanczos.maths.t .STEP. 16 u - 1024 0 0.000 0.000 4000.00 -krishna.via.ecp 157.99.64.66 2 u 565 1024 377 135.137 -3.266 27.060 -fartein.ifi.uio 129.132.2.21 2 u 183 1024 377 152.098 -1.977 70.375 +nic.lth.se 130.149.17.8 2 u 573 1024 377 189.192 9.626 16.759 -prestreljenik.a 131.188.3.221 2 u 574 1024 377 194.846 25.938 26.522 -troy.ijs.si 193.2.4.2 2 u 161 1024 377 217.189 -17.938 5.137 +ns.keso.fi 128.252.19.1 2 u 626 1024 377 208.706 12.708 3.418 *vega.cbk.poznan .PPS. 1 u 561 1024 377 172.300 19.649 8.573 -10.10.10.10 194.77.8.1 3 u 596 1024 377 150.404 31.493 64.959

Oh, and I'm using kernel 2.6.5 It was working fine, but since 3 weeks ago it just isn't. I just hope you don't tell me it's a POP problem. Cause I'll give up right now :(

[linux] Please help, this is getting frustrating

Jeroen Massar SixXS Staff

on Sunday, 02 May 2004 22:47:42

poznan as a Stratum 1 server.... hmmm and you are in Spain? I don't think that will work, notice the "delay" column ;) Btw, use 'ntpdc' and then 'peers' to see what your local ntp server tells you what it is. But it sure isn't synced: 80.172.0.81: Time is 269 seconds off for 2001:b18:2000:b::2

[linux] Please help, this is getting frustrating

Shadow Hawkins on Monday, 03 May 2004 01:25:49

I'm sorry, how can that be?? The delay is in milliseconds.. It's not even 0.3 seconds, how can it be 269 seconds off? I know the NTP server doesn't do big clock jumps, but the offset is < 100 milliseconds, so it should be correct.. right? Now I'm confused. Are you sure the POP server's clock isn't wrong?? I'm in Portugal, btw.

[linux] Please help, this is getting frustrating

Shadow Hawkins on Monday, 03 May 2004 01:28:06

Oh and:

ntpdc> peers remote local st poll reach delay offset disp ======================================================================= =troy.ijs.si 192.168.0.3 2 128 377 0.18381 -0.043641 0.00951 =krishna.via.ecp 192.168.0.3 2 128 377 0.12537 -0.013522 0.00516 =ns.keso.fi 192.168.0.3 2 128 377 0.15044 -0.030536 0.00877 =lanczos.maths.t :: 16 1024 0 0.00000 0.000000 0.00000 =fartein.ifi.uio 192.168.0.3 2 128 377 0.13794 -0.032680 0.01062 =hora.cs.tu-berl 192.168.0.3 1 128 377 0.11514 -0.018666 0.00989 =10.10.10.10 192.168.0.3 3 128 377 0.07047 0.000375 0.00490 =veracity.mcc.ac 192.168.0.3 2 128 377 0.12024 -0.040167 0.00810 =swisstime.ee.et 192.168.0.3 1 128 377 0.14058 -0.011896 0.00836 =prestreljenik.a 192.168.0.3 2 128 377 0.14651 -0.030877 0.00827 =ntp2-rz.rrze.un 192.168.0.3 16 1024 0 0.00000 0.000000 0.00000 =utserv.mcc.ac.u 192.168.0.3 2 128 377 0.09372 -0.018335 0.00972 =ntp0.cis.strath 192.168.0.3 2 128 377 0.14388 -0.017793 0.00359 *vega.cbk.poznan 192.168.0.3 1 128 377 0.11952 -0.020210 0.01083 =nic.lth.se 192.168.0.3 2 128 377 0.14958 -0.039335 0.00885

I didn't know about this 'ntpdc'. But it looks ok. What do you think?

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