SixXS::Sunset 2017-06-06

Problems after tunnel update
[be] Shadow Hawkins SixXS PoP Administrator on Tuesday, 20 May 2003 20:56:09
Hey guru's :) I recently updated my tunnel due to the prefix change of my endpoint. I deleted the old tunnel with a /sbin/ip tunnel del, and recreated the new one using the normal script with updated prefix. However, I can't manage to get my tunnel up. I get stuck on following [root@lweb02 root]# ping6 2001:838:300:4a::1 PING 2001:838:300:4a::1(2001:838:300:4a::1) from 2001:838:300:4a::2 : 56 data bytes where the ::1 is my endpoint. I have read some posts about this topic, but they talked about firewall settings. My firewall has not changed, I even shut it down for testing purposes. I can ping v4 to my endpoint. Some info: ifconfig sixxs Link encap:IPv6-in-IPv4 inet6 addr: fe80::d447:4c/128 Scope:Link inet6 addr: 2001:838:300:4a::2/128 Scope:Global route 2000::/3 dev sixxs metric 1 mtu 1480 advmss 1420 fe80::/10 via :: dev sixxs proto kernel metric 256 mtu 1480 advmss 1420 ff00::/8 dev sixxs proto kernel metric 256 mtu 1480 advmss 1420 unreachable default dev lo metric -1 error -101 advmss 1220 tunnel sit0: ipv6/ip remote any local any ttl 64 nopmtudisc sixxs: ipv6/ip remote 212.19.192.219 local "local ip" ttl 64 add 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue inet6 ::1/128 scope host 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 inet6 fe80::260:b0ff:fe1a:71b5/10 scope link 26: sixxs@NONE: <POINTOPOINT,NOARP,UP> mtu 1480 qdisc noqueue inet6 fe80::d447:4c/128 scope link inet6 2001:838:300:4a::2/128 scope global Looks all fine to me, .... Any help is greatly appreciated. Thanks ! Daan
Problems after tunnel update
[ch] Jeroen Massar SixXS Staff on Wednesday, 21 May 2003 02:46:26
tunnel
sit0: ipv6/ip remote any local any ttl 64 nopmtudisc
sixxs: ipv6/ip remote 212.19.192.219 local "local ip" ttl 64
Last time I checked that was the IP of the IPng POP: 219.192.19.212.IN-ADDR.ARPA domain name pointer tunnelserver.ipng.nl Goody, it is still the same. Concepts is nlams01.sixxs.net and not nlams02.sixxs.net. Also it's a /64 that goes over the link, though configuring a /128 should work too.
Problems after tunnel update
[be] Shadow Hawkins SixXS PoP Administrator on Wednesday, 21 May 2003 19:02:10
I totally overlooked. Thanks a lot for pointing it out. Daan

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

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