Forum - ipv6 on gentoo linux :: SixXS - IPv6 Deployment & Tunnel Broker

ipv6 on gentoo linux

Shadow Hawkins on Monday, 14 January 2008 19:19:46

Hello, I have tryed to find a similar subject, but I was unable to find any. However, if there is already described solution to this issue - please excuse me and provide me with the url, so I can check it out. Thanks in advance. So, my problem seems very strange. I can traceroute my connection by using the traceroute tool provided at sixxs.net website, but on the statistics I am displayed as 100% down. This seems very confusing because my iptables is currently reset and the default rules are set to ACCEPT:

dx dx # iptables -nL Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination dx dx #

I am guessing that either there is a problem at the sixxs.net side, either I am configuring my interfaces incorrectly. Here are my settings:

dx dx # ip -6 rule dx dx # ip -6 route 2001:470:1f08:f::2 dev sixbone metric 1024 expires 21334305sec mtu 1280 advmss 1220 hoplimit 4294967295 2001:470:1f08:22::/64 via :: dev sixbone metric 256 expires 17181947sec mtu 1280 advmss 1220 hoplimit 4294967295 2001:470:1f09:22::/64 via :: dev sixbone metric 256 expires 17181947sec mtu 1280 advmss 1220 hoplimit 4294967295 2001:15c0:65ff:148::/64 via :: dev ipv6_dx metric 256 expires 17181457sec mtu 1460 advmss 1400 hoplimit 4294967295 fe80::/64 dev eth0 metric 256 expires 21256623sec mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 via :: dev ipv6_dx metric 256 expires 21333815sec mtu 1460 advmss 1400 hoplimit 4294967295 fe80::/64 via :: dev sixbone metric 256 expires 21334305sec mtu 1280 advmss 1220 hoplimit 4294967295 ff00::/8 dev eth0 metric 256 expires 21256623sec mtu 1500 advmss 1440 hoplimit 4294967295 ff00::/8 dev ipv6_dx metric 256 expires 21333815sec mtu 1460 advmss 1400 hoplimit 4294967295 ff00::/8 dev sixbone metric 256 expires 21334305sec mtu 1280 advmss 1220 hoplimit 4294967295 default dev ipv6_dx metric 1024 expires 21333815sec mtu 1460 advmss 1400 hoplimit 4294967295 dx dx # ifconfig ipv6_dx ipv6_dx Link encap:IPv6-in-IPv4 inet6 addr: 2001:15c0:65ff:148::1/64 Scope:Global inet6 addr: 2001:15c0:65ff:148::2/64 Scope:Global inet6 addr: fe80::d449:8f8d/128 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1460 Metric:1 RX packets:20 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:2080 (2.0 Kb) TX bytes:0 (0.0 b)

The lines I am using to activate the interface are as follows:

ip tunnel add ipv6_dx mode sit remote 212.18.63.73 local 212.73.xxx.xxx ttl 255 dev eth0 ip link set ipv6_dx mtu 1460 ip link set ipv6_dx up ip addr add 2001:15c0:65ff:148::1/64 dev ipv6_dx ip route add ::/0 dev ipv6_dx ip addr add 2001:15c0:65ff:148::2/64 dev ipv6_dx

Please note that this is the second ipv6 tunnel at this gateway. The first one has been established because some of my friends requested to up his ~30 ipv6 addresses and I agreed. However, this should not be an issue, as I am routing only requests to ipv6.plovdivbg.net via his ip addresses and the rest are handled by sixxs.net. Here's an example:

dx dx # tracepath6 ipv6.plovdivbg.net 1?: [LOCALHOST] pmtu 1280 1: nullcx.tunnel.tserv5.lon1.ipv6.he.net 62.468ms 2: xdsgrrr-pt.tunnel.tserv5.lon1.ipv6.he.net 231.686ms reached Resume: pmtu 1280 hops 2 back 2 dx dx # tracepath6 ipv6.research.microsoft.com 1?: [LOCALHOST] pmtu 1460 1: gw-329.mbx-01.si.sixxs.net 69.024ms 2: maribor3-vlan-4.amis.net 73.520ms 3: vienna1-ge-1-21.amis.net 78.442ms 4: M6-Tu6.Space.Net 130.121ms 5: no reply 6: no reply^C^C dx dx #

Can anyone advise me on what to do? I presumed it might be of laggy connection, but this does not seems to be the case:

dx dx # ping6 2001:15c0:65ff:148::1 PING 2001:15c0:65ff:148::1(2001:15c0:65ff:148::1) 56 data bytes 64 bytes from 2001:15c0:65ff:148::1: icmp_seq=1 ttl=64 time=0.041 ms 64 bytes from 2001:15c0:65ff:148::1: icmp_seq=2 ttl=64 time=0.052 ms 64 bytes from 2001:15c0:65ff:148::1: icmp_seq=3 ttl=64 time=0.036 ms --- 2001:15c0:65ff:148::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.036/0.043/0.052/0.006 ms

I will appreciate prompt answer, as I am a novice when it comes to vpn tunnels. Thanks in advance to anyone tried to help me!

ipv6 on gentoo linux

Shadow Hawkins on Tuesday, 15 January 2008 09:35:00

According to https://noc.sixxs.net/pops/amis/ simbx01 allocates tunnels out of 2001:15c0:65ff::/48 and subnets out of 2001:15c0:6600::/40. And you â as quoted above â have both 2001:15c0:65ff:148::1/64 and 2001:15c0:65ff:148::2/64 configured to your interface. I believe you should only have 2001:15c0:65ff:148::2/64 and that 2001:15c0:65ff:148::1/64 is the other end of your tunnel. Try removing 2001:15c0:65ff:148::1/64 from your setup script. Also, if my suspicion above is correct and were you using aiccu, your default route would be to 2001:15c0:65ff:148::1/64 rather than to the interface. So you might want:

ip tunnel add ipv6_dx mode sit remote 212.18.63.73 local 212.73.xxx.xxx ttl 255 dev eth0 ip link set ipv6_dx mtu 1460 ip link set ipv6_dx up ip addr -6 add 2001:15c0:65ff:148::2/64 dev ipv6_dx ip route -6 add ::/0 via 2001:15c0:65ff:148::1

You might also want to add

src 2001:15c0:65ff:148::1

to that last line.Â¹ 1] I have a subnet in addition to a tunnel, add an address from the first /64 of the /48 to my sixxs dev, and specify that as the src in my default route so that packets from the gw box itself come from an address whose PTR I control. I then use another of the /64s from the /48 for the gwâs ethernet.

ipv6 on gentoo linux

Shadow Hawkins on Tuesday, 15 January 2008 09:41:38

Grrr. It looks like this software screws up

utf-8

input, treating it as thought it were

latin1

(or maybe

cp1252

?) octets and converting those to

utf-8

for display.... SIGH :( Please read ^1 for Â¹, -- for â, and ' for â.

ipv6 on gentoo linux

Jeroen Massar SixXS Staff

on Wednesday, 16 January 2008 09:48:56

It is treating it as US-ASCII. How else would it have to treat it? Your browser is definitely not sending a Content-Type/Encoding scheme while doing a POST message. As such it strips it and the above what is then left. Try simply typing your message, instead of cut&pasting it from Word or something similar which has these effects.

ipv6 on gentoo linux

Shadow Hawkins on Friday, 18 January 2008 15:16:03

Word? Ewww! Gross! :) I did type directly in the browser. Interestingly the email displayed correctly. Were the html to be generated such that the octets were sent as submitted it would also have displayed OK. But I do see the issue; I should've thought a bit more before sending off the 2nd reply, but I wanted to make sure no one was confused by the formatting of the first reply. I just have gotten used to utf8 just working in issue trackers like bugzilla and was surprised that it didn't do so here.... In any case thanks for all of the work here; Sixxs is invaluable to the community!

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