can't get my tunnel up and running after new debian install
Carmen Sandiego on Tuesday, 06 January 2009 08:36:19
Have this problem when im setting up IPv6 tunnel on my new server.
im running: /usr/sbin/aiccu test
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:16d8:ee00:76::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:16d8:ee00:76::1(2001:16d8:ee00:76::1) 56 data bytes
--- 2001:16d8:ee00:76::1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1000ms
and in the end i get sh: ip: command not found.
my route -6 is here:
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::1/128 :: U 0 30 1 lo
2001:16d8:ee00:76::2/128 :: U 0 52 1 lo
2001:16d8:ee00:76::2/128 :: U 0 0 1 lo
2001:16d8:ee00:76::/64 :: U 256 26828 0 sit1
2001:16d8:ee00:76::/64 :: U 256 0 0 eth0
fe80::5294:905a/128 :: U 0 0 1 lo
fe80::20c:29ff:fe2c:318f/128 :: U 0 0 1 lo
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 sit1
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 sit1
::/0 :: U 1 0 0 sit1
::/0 :: U 256 35 0 sit1
can't get my tunnel up and running after new debian install
Jeroen Massar on Tuesday, 06 January 2009 11:26:15
install the iproute package.
Using sit0/sit1 interfaces is deprecated and it looks a lot like you have a lot of weird things in your routing tables.
2001:16d8:ee00:76::2/128 :: U 0 52 1 lo 2001:16d8:ee00:76::2/128 :: U 0 0 1 lo 2001:16d8:ee00:76::/64 :: U 256 26828 0 sit1 2001:16d8:ee00:76::/64 :: U 256 0 0 eth0
Both on sit1 and eth0
::/0 :: U 1 0 0 sit1 ::/0 :: U 256 35 0 sit1
Double default route.
That is indeed not going to work. You'll have to clean up that mess first. AICCU won't fix it. What is strange is that the aiccu package should be depending on the iproute package. 'ip' also gets installed in /bin/ip thus one also really can't have any path issues with it either.
can't get my tunnel up and running after new debian install
Carmen Sandiego on Tuesday, 06 January 2009 11:33:39
ahh, i missed the iproute pack.
Debian Etch does not have support for the aiccu yet..
can't get my tunnel up and running after new debian install
Jeroen Massar on Tuesday, 06 January 2009 11:41:33
The only thing holding it back from not working is strange Debian 'policies', you can just download the source and when having installed the 'build-essential' package you can inside the directory of the source, just run "debian/rules binary" and it will nicely build a package for you. Funny was that Debian folks asked if we would remove that directory from our source, yeah right, us doing the work and then locking people into only Debian, not happening as there are other distros using the dpkg format.
It is also available from etch-backports it seems and you can of course always switch to Ubuntu which seem to have less strange policies.
Posting is only allowed when you are logged in. |