You are not logged in.
Hi there,
a new arch system has been set up by me and now I try to get IPv6 working. Sixxs is my tunnel provider and it did work on my previous (Ubuntu 10.04) system. So in general it should be possible :-). I installed the aiccu package from the AUR and if I do "aiccu start" it gets all the correct tunnel data. Testing things with "aiccu test" shows that everything, but outbound connections, works. I can ping myself, but test 6 (Ping the IPv6 Remote/PoP Inner Tunnel Endpoint), 7 (Traceroute6 to the central SixXS machine) and 8 (Traceroute6 to (www.kame.net)) fail. Test 6 gives the following hint:
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problemIt seems that the sixxs interface is configured correctlyt, ifconfig shows (the *'s are replacements by me):
sixxs Link encap:UNSPEC HWaddr C0-A8-02-56-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::c0a8:256/64 Scope:Link
inet6 addr: 2001:6f8:***:***::2/64 Scope:Global
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)Unfortunately, there is not much experience with ip tables, but this is the output from "route":
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
default arcor.easybox 0.0.0.0 UG 0 0 0 eth0And this is the output from "ip -f inet6 route show":
2001:6f8:***:***::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
default via 2001:6f8:***:***::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0The configuration from /etc/aiccu.conf is tha following:
username ****
password ****
protocol tic
server tic.sixxs.net
ipv6_interface sixxs
tunnel_id ****
verbose true
daemonize true
automatic true
requiretls false
pidfile /var/run/aiccu.pid
defaultroute true
makebeats true
behindnat trueI am behind a NAT which connects me to the internet. Do you have any hints where to look else? Should it work by default or am I missing some settings?
Furthermore I need to use the teredo protocol with meredo, but this is likely another issue (as running meredo does not affect the general ipv6 situation with aiccu for me).
Edit: After executing
ip route add ::/0 dev sixxsI could get sometimes a connection. For a ping6 the best was about 50% package loss. I found this on the wiki pake for manual 6in4 tunnels. So it seems that it actually has something to do with routing and which routes are created by the aiccu -- so this is not yet resolved.
Thanks in advance, regards,
Tom
Last edited by mind_the_gap (2010-12-13 22:34:14)
Offline
have you tried using the default settings? I'm behind several NATs and my sixxs tunnel works with the following aiccu.conf:
username ....
password ....ipv6_interface sixxs
verbose false
daemonize true
automatic true
requiretls false
nothing more.
Offline
Thanks for posting your conig, smayer. Unfortunately I got the same result as before
--- 2001:6f8:***:***::1 ping statistics ---
3 packets transmitted, 1 received, 66% packet loss, time 2008ms
rtt min/avg/max/mdev = 29.139/29.139/29.139/0.000 msSome packet get through -- strange. My router is probably alright, since it did work on Ubuntu two weeks ago.
I tried the same config with an ArchLinux on my notebook. It is connected via wlan to the same router. There happens exactly the same -- packet loss. Well, either my router is not working correcly for about two weeks now or my arch setups have both some problems. I'll try this on another machine.
Edit: I tried it on another machine in this LAN -- Ubuntu 10.10. The same result there -- so it is probably not arch or my configuration. I'll exchange the router and see what happens.
Edit: It seems to work now. After I have disable intrusion detection and firewalls on my router (I'll fine tune that) the packet loss is gone. So sorry for the spam here :-)
Last edited by mind_the_gap (2010-12-16 00:21:01)
Offline