[Ubuntu Server] IPv6 met SixXs.net probleem

[Judge Duck]

Hallo allen,

Sinds kort probeer ik om via Ubuntu server het IPv6 gedeelte aan de gang te krijgen zoals ik dit
voorheen ook in Windows had. Via SixXs.net heb ik een IPv6 tunnel welke goed werkt via Windows.

De Ubuntu machine staat achter een NAT router waar DMZ staat ingesteld op het Ubuntu ip. Op
deze machine heb ik zelf geen firewall instellingen oid gedaan en is een verse installatie van de
laatste Ubuntu server versie met enkele pakketten geinstalleerd (openss-server proftpd sabnzbd).

Wat ik heb gedaan is het pakket AICCU via de apt-get installeren en de correcte tunnel
specificeren,hierna in de config gezet dat ik achter een NAT zit. Vervolgens laat ik het test scriptje
van AICCU draaien om te controleren of de verbinding goed werkt, wat dus niet het geval is omdat
deze bij stap 6 faalt vanwege "Destination unreachable: Address unreachable". Zie helemaal
onderaan deze post het log bestand van deze test. Kan iemand mij helpen met het goedzetten van
deze IPv6 verbinding?

Voorheen in Windows kon ik via het volgende command een verbinding maken met
newszilla6.xs4all.nl via IPv6, is hiervoor ook een linux command?

"netsh interface portproxy add v4tov6 listenport=119 connectaddress=newszilla6.xs4all.nl connectport=119"

Alvast bedankt!

#######
####### AICCU Quick Connectivity Test
#######

####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (84.27.217.95)
### 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 84.27.217.95 (84.27.217.95) 56(84) bytes of data.
64 bytes from 84.27.217.95: icmp_seq=1 ttl=63 time=0.844 ms
64 bytes from 84.27.217.95: icmp_seq=2 ttl=63 time=0.892 ms
64 bytes from 84.27.217.95: icmp_seq=3 ttl=63 time=0.917 ms

--- 84.27.217.95 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2016ms
rtt min/avg/max/mdev = 0.844/0.884/0.917/0.038 ms

######

####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (192.87.102.107)
### 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 192.87.102.107 (192.87.102.107) 56(84) bytes of data.
64 bytes from 192.87.102.107: icmp_seq=1 ttl=56 time=8.32 ms
64 bytes from 192.87.102.107: icmp_seq=2 ttl=56 time=9.25 ms
64 bytes from 192.87.102.107: icmp_seq=3 ttl=56 time=9.43 ms

--- 192.87.102.107 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2026ms
rtt min/avg/max/mdev = 8.325/9.004/9.435/0.492 ms

######

####### [3/8] Traceroute to the PoP (192.87.102.107) 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

sh: traceroute: not found

######

###### [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.030 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.016 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.030 ms

--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2006ms
rtt min/avg/max/mdev = 0.016/0.025/0.030/0.007 ms

######

###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:610:600:27f::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables

PING 2001:610:600:27f::2(2001:610:600:27f::2) 56 data bytes
64 bytes from 2001:610:600:27f::2: icmp_seq=1 ttl=64 time=0.034 ms
64 bytes from 2001:610:600:27f::2: icmp_seq=2 ttl=64 time=0.018 ms
64 bytes from 2001:610:600:27f::2: icmp_seq=3 ttl=64 time=0.009 ms

--- 2001:610:600:27f::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2007ms
rtt min/avg/max/mdev = 0.009/0.020/0.034/0.011 ms

######

###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:610:600:27f::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:610:600:27f::1(2001:610:600:27f::1) 56 data bytes
From 2001:610:600:27f::2 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:610:600:27f::2 icmp_seq=2 Destination unreachable: Address unreachable
From 2001:610:600:27f::2 icmp_seq=3 Destination unreachable: Address unreachable

--- 2001:610:600:27f::1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2007ms


######

###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.

traceroute: unknown host noc.sixxs.net

######

###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6

traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:610:600:27f::2, 30 hops max, 16 byte packets
1 cl (2001:610:600:27f::2) 0.044 ms !H 0.032 ms !H 0.015 ms !H

######

###### ACCU Quick Connectivity Test (done)

### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.

[Pim.]

Ik gebruik IP tunnel en verder eigenlijk niets:

iptunnel add ipv6 mode sit local 83.137.144.50 remote 213.197.27.252
route add --inet6 default gw 2001:838:300:f8::1
ifconfig ipv6 up
ifconfig ipv6 add 2001:838:300:f8::2/64
ifconfig ipv6 add 2001:838:373::3/64
ifconfig ipv6 add 2001:838:373::2/64
ifconfig ipv6 add 2001:838:373::1/64
route -A inet6 add 2000::/3 ipv6

[Judge Duck]

Bedankt voor de reactie!

Het is dus aan te raden om de tunnel statisch in te stellen begrijp ik hieruit, in welke volgorde moet ik
mijn gegevens invoeren?

Your IPv4 84.27.217.95
IPv6 Prefix 2001:610:600:27f::1/64
PoP IPv6 2001:610:600:27f::1
Your IPv6 2001:610:600:27f::2

Heb je toevallig ook een idee hoe ik de verbinding met newszilla6.xs4all.nl tot stand kan brengen?

[MTWZZ]

Gewoon deze volgen: click

[blaataaps]

1 topic is genoeg