Forum - Linux setup with iproute2 issue :: SixXS - IPv6 Deployment & Tunnel Broker

Linux setup with iproute2 issue

Shadow Hawkins on Tuesday, 30 December 2008 15:10:41

Hello guys :) My tunnel was disabled for a while and today I've re-enabled it, but it does not work. Here is my setup: ip tunnel add ipv6_dx mode sit remote 212.18.63.x local 212.73.x.x ttl 255 dev eth0 ip link set ipv6_dx mtu 1280 ip link set ipv6_dx up ip addr add 2001:15c0:65ff:xxx::2/64 dev ipv6_dx ip route add ::/0 via 2001:15c0:65ff:xxx::1 There is no error message returned so far, but ping and traceroute fails. dx-pc ~ # ping6 www.sixxs.net PING www.sixxs.net(noc.sixxs.net) 56 data bytes From cl-329.mbx-01.si.sixxs.net icmp_seq=1 Destination unreachable: Address unreachable From cl-329.mbx-01.si.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable ^C --- www.sixxs.net ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1000ms Here is my routing table: dx-pc ~ # route -6 Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If 2001:15c0:65ff:xxx::/64 :: Un 256 0 4 ipv6_dx fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: Un 256 0 0 ipv6_dx ::/0 2001:15c0:65ff:148::1 UG 1024 0 8 ipv6_dx ::/0 :: !n -1 1 13 lo ::1/128 :: Un 0 1 8 lo 2001:15c0:65ff:xxx::2/128 :: Un 0 1 24 lo fe80::d449:8f8d/128 :: Un 0 1 0 lo fe80::219:dbff:fecb:3760/128 :: Un 0 1 0 lo ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 ipv6_dx ::/0 :: !n -1 1 13 lo Could anyone give me some advice? I've also tried to setup the aiccu, but it does not work either.. here is my /var/log/messages: Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)" Dec 30 15:17:08 dx-pc aiccu: sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.27-gentoo-r2" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "200 Client Identity accepted" Dec 30 15:17:08 dx-pc aiccu: sock_printf() : "get unixtime" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "200 1230643028" Dec 30 15:17:08 dx-pc aiccu: sock_printf() : "starttls" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "400 This service is not SSL enabled (yet)" Dec 30 15:17:08 dx-pc aiccu: TIC Server does not support TLS but TLS is not required, continuing Dec 30 15:17:08 dx-pc aiccu: sock_printf() : "username xxx-SIXXS" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "200 Choose your authentication challenge please" Dec 30 15:17:08 dx-pc aiccu: sock_printf() : "challenge md5" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "200 9asdbef9c87ac9050efecfe4f682a14d" Dec 30 15:17:08 dx-pc aiccu: sock_printf() : "authenticate md5 e5fea72d16hb73e9c50394800eax260x" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "200 Succesfully logged in using md5 as xxx-SIXXS (Nikola Petkanski) from 2001:7b8:3:4f:202:b3ff:fe46:bec" Dec 30 15:17:08 dx-pc aiccu: sock_printf() : "tunnel show Txxxxx" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "201 Showing tunnel information for T13883" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "TunnelId: Txxxxx" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "Type: 6in4-static" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "IPv6 Endpoint: 2001:15c0:65ff:xxx::2" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "IPv6 POP: 2001:15c0:65ff:xxx::1" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "IPv6 PrefixLength: 64" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "Tunnel MTU: 1280" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "Tunnel Name: My First Tunnel" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "POP Id: simbx01" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "IPv4 Endpoint: 212.73.xxx.xxx" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "IPv4 POP: 212.18.63.xx" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "UserState: enabled" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "AdminState: enabled" Dec 30 15:17:08 dx-pc aiccu: sock_getline() : "202 Done" Dec 30 15:17:08 dx-pc aiccu: Succesfully retrieved tunnel information for Txxxxx Dec 30 15:17:08 dx-pc aiccu: sock_printf() : "QUIT Even the spirits are afraid" Dec 30 15:17:08 dx-pc aiccu: AICCU running as PID 13691 Dec 30 15:17:08 dx-pc sixxs: Disabled Privacy Extensions Any help on the issue will be appreciated. Thanks in advance and happy new year :)

Linux setup with iproute2 issue

Shadow Hawkins on Tuesday, 30 December 2008 15:13:47

I've forgot to provide you with the aiccu config file, if someone would like to assist me with it: username xxxx-SIXXS password xxxx ipv6_interface sixxs tunnel_id Txxxxx verbose true daemonize true automatic true requiretls false defaultroute true makebeats true behindnat true

Linux setup with iproute2 issue

Shadow Hawkins on Tuesday, 30 December 2008 15:47:08

I haven't tried this with Linux yet, but can you post the output of ifconfig -a ?

Linux setup with iproute2 issue

Shadow Hawkins on Sunday, 11 January 2009 16:31:14

Here is the 'ifconfig -a': eth0 Link encap:Ethernet HWaddr 00:19:db:cb:37:60 inet addr:192.168.1.85 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::219:dbff:fecb:3760/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:132815 errors:0 dropped:0 overruns:0 frame:0 TX packets:200953 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11560022 (11.0 MiB) TX bytes:212184732 (202.3 MiB) Interrupt:19 Base address:0x4000 ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 NOARP MTU:1460 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) 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:41 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:994 (994.0 B) TX bytes:994 (994.0 B) 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:15c0:65ff:xxx::2/64 Scope:Global inet6 addr: fe80::d449:8f8d/128 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) The host is under DMZ, so the fact that it is behind router should not be an issue. At least, the last time i've got this running it wasn't :)

Linux setup with iproute2 issue

Jeroen Massar SixXS Staff

on Sunday, 11 January 2009 16:38:33

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Clearly not even a single packet has been sent/received through that interface. Please actually go through the "Reporting Problems / Checklist" and supply *ALL* those details *after* AICCU is running.

Linux setup with iproute2 issue

Shadow Hawkins on Sunday, 11 January 2009 17:40:42

I have sent an email to info@sixxs.net, so they can check the issue and inform me how to proceed further, however, here is the major information you requested. I would be very happy if you could assist me :) Here is the output of 'aiccu test' command: dx-pc scripts # aiccu test Tunnel Information for T13883: POP Id : simbx01 IPv6 Local : 2001:15c0:65ff:148::2/64 IPv6 Remote : 2001:15c0:65ff:148::1/64 Tunnel Type : 6in4-static Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (212.73.143.141) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 212.73.143.141 (212.73.143.141) 56(84) bytes of data. 64 bytes from 212.73.143.141: icmp_seq=1 ttl=64 time=0.000 ms 64 bytes from 212.73.143.141: icmp_seq=2 ttl=64 time=0.000 ms 64 bytes from 212.73.143.141: icmp_seq=3 ttl=64 time=0.000 ms --- 212.73.143.141 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms ###### Did this work? [Y/n] ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.18.63.73) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur PING 212.18.63.73 (212.18.63.73) 56(84) bytes of data. 64 bytes from 212.18.63.73: icmp_seq=1 ttl=53 time=950 ms 64 bytes from 212.18.63.73: icmp_seq=2 ttl=53 time=860 ms 64 bytes from 212.18.63.73: icmp_seq=3 ttl=53 time=530 ms --- 212.18.63.73 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2020ms rtt min/avg/max/mdev = 530.000/780.000/950.000/180.554 ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the PoP (212.18.63.73) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem traceroute to 212.18.63.73 (212.18.63.73), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.000 ms 0.000 ms 10.000 ms 2 h212-73-143-1.galaxylan.com (212.73.143.1) 20.000 ms 20.000 ms 20.000 ms 3 212.73.141.197 (212.73.141.197) 20.000 ms 20.000 ms 20.000 ms 4 192.168.141.1 (192.168.141.1) 30.000 ms 30.000 ms 30.000 ms 5 212.73.141.37 (212.73.141.37) 570.000 ms 570.000 ms 570.000 ms 6 212.73.128.125 (212.73.128.125) 610.000 ms 580.000 ms 580.000 ms 7 87.121.6.66 (87.121.6.66) 610.000 ms 610.000 ms 610.000 ms 8 decix-aon.highway.telekom.at (80.81.192.69) 610.000 ms 610.000 ms 610.000 ms 9 195.3.70.205 (195.3.70.205) 600.000 ms 1180.000 ms 600.000 ms 10 195.3.70.70 (195.3.70.70) 610.000 ms 720.000 ms 720.000 ms 11 80.120.176.182 (80.120.176.182) 720.000 ms 680.000 ms 690.000 ms 12 maribor3-po-1.amis.net (212.18.41.137) 690.000 ms 670.000 ms 670.000 ms 13 simbx01.sixxs.net (212.18.63.73) 630.000 ms 680.000 ms 680.000 ms ###### Did this work? [Y/n] ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.000 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.000 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.000 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:15c0:65ff:148::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:15c0:65ff:148::2(2001:15c0:65ff:148::2) 56 data bytes 64 bytes from 2001:15c0:65ff:148::2: icmp_seq=1 ttl=64 time=0.000 ms 64 bytes from 2001:15c0:65ff:148::2: icmp_seq=2 ttl=64 time=0.000 ms 64 bytes from 2001:15c0:65ff:148::2: icmp_seq=3 ttl=64 time=0.000 ms --- 2001:15c0:65ff:148::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:15c0:65ff:148::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem PING 2001:15c0:65ff:148::1(2001:15c0:65ff:148::1) 56 data bytes From 2001:15c0:65ff:148::2 icmp_seq=1 Destination unreachable: Address unreachable From 2001:15c0:65ff:148::2 icmp_seq=2 Destination unreachable: Address unreachable From 2001:15c0:65ff:148::2 icmp_seq=3 Destination unreachable: Address unreachable --- 2001:15c0:65ff:148::1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2000ms ###### Did this work? [Y/n] n --------------------------------- The aiccu was installed from the Gentoo linux repository using the 'emerge -av aiccu' command. Here is the output of 'aiccu version': AICCU 2007.01.15-console-linux by Jeroen Massar -------------------------------- Here is the config file I am using for aiccu, located at /etc/aiccu.conf: username NPL1-SIXXS password ********* ipv6_interface sixxs tunnel_id T13883 verbose true daemonize true automatic true requiretls false defaultroute true makebeats true behindnat true ------------------------------ The linux distribution I'm using is Gentoo 2008.0, here is the uname -a: Linux dx-pc 2.6.27-gentoo-r2 #2 SMP Tue Dec 30 13:16:55 EET 2008 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ AuthenticAMD GNU/Linux ------------------------------ iptables is not even installed, so no firewall is running at the machine: dx-pc scripts # iptables -nL FATAL: Module ip_tables not found. iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. ------------------------------ Here is the routing table: dx-pc scripts # route -6 Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If 2001:15c0:65ff:148::/64 :: Un 256 0 1 sixxs fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: Un 256 0 0 sixxs ::/0 fe80::e970:cd28:953b:7add UGDAe 1024 0 220 eth0 ::/0 2001:15c0:65ff:148::1 UG 1024 0 0 sixxs ::/0 :: !n -1 1 236 lo ::1/128 :: Un 0 1 15 lo 2001:15c0:65ff:148::2/128 :: Un 0 1 0 lo fe80::d449:8f8d/128 :: Un 0 1 0 lo fe80::219:dbff:fecb:3760/128 :: Un 0 1 11 lo ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 sixxs ::/0 :: !n -1 1 236 lo dx-pc scripts # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 loopback localhost 255.0.0.0 UG 0 0 0 lo default 192.168.1.1 0.0.0.0 UG 4 0 0 eth0 As you may have noticed, the server is using internal network ip address. This is so and it was checked at the configuration of aiccu. Also, the server is under full DMZ. ------------------------------ Here is the network configuration: dx-pc scripts # ip link show && ifconfig -a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: sit0: <NOARP> mtu 1480 qdisc noop state DOWN link/sit 0.0.0.0 brd 0.0.0.0 3: ip6tnl0: <NOARP> mtu 1460 qdisc noop state DOWN link/tunnel6 :: brd :: 4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:19:db:cb:37:60 brd ff:ff:ff:ff:ff:ff 9: sixxs@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN link/sit 212.73.143.141 peer 212.18.63.73 eth0 Link encap:Ethernet HWaddr 00:19:db:cb:37:60 inet addr:192.168.1.85 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::219:dbff:fecb:3760/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:282816 errors:0 dropped:0 overruns:0 frame:0 TX packets:411872 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23180850 (22.1 MiB) TX bytes:425058213 (405.3 MiB) Interrupt:19 Base address:0x4000 ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 NOARP MTU:1460 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) 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:118 errors:0 dropped:0 overruns:0 frame:0 TX packets:118 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4082 (3.9 KiB) TX bytes:4082 (3.9 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:15c0:65ff:148::2/64 Scope:Global inet6 addr: fe80::d449:8f8d/128 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:1 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Linux setup with iproute2 issue

Jeroen Massar SixXS Staff

on Sunday, 11 January 2009 18:33:49

I have sent an email to info@sixxs.net, so they can check the issue

That is not a helpdesk. Only submit your problems there when you think it is not you. Read the contact page for more details.

::/0 fe80::e970:cd28:953b:7add UGDAe 1024 0 220 eth0

::/0 2001:15c0:65ff:148::1 UG 1024 0 0 sixxs

You have two default routes. Somebody else on your local network is announcing IPv6 connectivity it seems.

From 2001:15c0:65ff:148::2 icmp_seq=1 Destination unreachable: Address unreachable

That indicates that your box itself can't reach the remote address

9: sixxs@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN

link/sit 212.73.143.141 peer 212.18.63.73

That is wrong, 212.73.143.141 is not configured anywhere on your host (according to the output you provide) and thus your host will never be able to use it. Which explains the problem above about not being able to reach the remote host. Try to stop AICCU, then 'ip tunnel del sixxs' and then start AICCU again. That should maybe do the trick.

Linux setup with iproute2 issue

Shadow Hawkins on Wednesday, 21 January 2009 09:12:26

Well, the internal ip address of the server is 192.168.1.85. The external is 212.73.143.141. As I mentioned - it is under full DMZ. This is the reason why the interface is not using the external ip address. I believe this should not be an issue. Could you please give me a suggestion how should I proceed further?

Linux setup with iproute2 issue

Jeroen Massar SixXS Staff

on Wednesday, 21 January 2009 09:21:32

Even in that case the local endpoint is 192.168.1.85, as that is the only thing your box knows about. Use wireshark/tshark/tcpdump and you will never see a packet with 217.73.143.141 in it going to your box, all will be 192.168.1.85. As it is Linux you can easily set the "local" part to "any", which is what AICCU does per default. It seems though you have a lot of old lingering configuration and other hosts on your network doing IPv6 already. Should clean that up first.

Linux setup with iproute2 issue

Shadow Hawkins on Wednesday, 21 January 2009 09:43:08

The "local" setting is not set inside the configuration file, so it should be set to 'any'. I have just removed the ipv6 routines associated with eth0, so here is the routing table now: dx-pc scripts # ip -6 route 2001:15c0:65ff:148::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 default via 2001:15c0:65ff:148::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 dx-pc scripts # route -6 Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If ::1/128 :: Un 0 1 10342 lo 2001:15c0:65ff:148::2/128 :: Un 0 1 9 lo 2001:15c0:65ff:148::/64 :: Un 256 0 3 sixxs fe80::d449:8f8d/128 :: Un 0 1 0 lo fe80::219:dbff:fecb:3760/128 :: Un 0 1 34 lo fe80::/64 :: Un 256 0 0 sixxs ff00::/8 :: U 256 0 0 sixxs ::/0 2001:15c0:65ff:148::1 UG 1024 0 3 sixxs ::/0 :: !n -1 1 10 lo But, the tunnel does not seem to work :( dx-pc scripts # ping6 www.sixxs.net PING www.sixxs.net(noc.sixxs.net) 56 data bytes From cl-329.mbx-01.si.sixxs.net icmp_seq=1 Destination unreachable: Address unreachable From cl-329.mbx-01.si.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable From cl-329.mbx-01.si.sixxs.net icmp_seq=3 Destination unreachable: Address unreachable ^C --- www.sixxs.net ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2002ms I looked once again my configuration file and I have noticed the following part at the end: # Local IPv4 Override (default: none) # Overrides the IPv4 parameter received from TIC # This allows one to configure a NAT into "DMZ" mode and then # forwarding the proto-41 packets to an internal host. # # This is only needed for static proto-41 tunnels! # AYIYA and heartbeat tunnels don't require this. #local_ipv4_override I have uncommented the line and passed as an argument my internal IP address and this seemed to work :) dx-pc scripts # ping6 www.sixxs.net PING www.sixxs.net(noc.sixxs.net) 56 data bytes 64 bytes from noc.sixxs.net: icmp_seq=1 ttl=55 time=116 ms 64 bytes from noc.sixxs.net: icmp_seq=2 ttl=55 time=105 ms 64 bytes from noc.sixxs.net: icmp_seq=3 ttl=55 time=101 ms ^C --- www.sixxs.net ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 101.561/107.684/116.324/6.284 ms Thanks to all ppl for helping me with this issue :)

Linux setup with iproute2 issue

Shadow Hawkins on Thursday, 01 January 2009 18:32:34

please test route add 2000::/3 ip route add 2000::/3 via 2001:15c0:65ff:xxx::1

Linux setup with iproute2 issue

Shadow Hawkins on Sunday, 11 January 2009 16:32:32

Just tried it.. sadly, it does not work :( dx-pc scripts # ip route add 2000::/3 via 2001:15c0:65ff:xxx::1 dx-pc scripts # ping6 www.sixxs.net PING www.sixxs.net(noc.sixxs.net) 56 data bytes From cl-329.mbx-01.si.sixxs.net icmp_seq=1 Destination unreachable: Address unreachable From cl-329.mbx-01.si.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable ^C --- www.sixxs.net ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1010ms Thanks for the suggestion anyway.

Linux setup with iproute2 issue

Jeroen Massar SixXS Staff

on Sunday, 11 January 2009 16:37:27

2000::/3 is only needed when having forwarding enabled on old/broken Linux kernels as they 'ignore' ::/0 in that case.

Linux setup with iproute2 issue

Shadow Hawkins on Sunday, 11 January 2009 17:05:04

Actually, the kernel is not very old. dx-pc scripts # uname -a Linux dx-pc 2.6.27-gentoo-r2 #2 SMP Tue Dec 30 13:16:55 EET 2008 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ AuthenticAMD GNU/Linux I will try post the problem the regular way. Thanks to everyone for their participation in this topic.

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