|
Fritzbox 7170 AICCU Modded, what is wrong?
![[de]](/s/countries/de.gif) Carmen Sandiego on Monday, 07 December 2009 21:23:58
I am new there, naw i will ipv6 too.
Im modded the Fritzbox 7170 with Freez, and it is something wrong.
AICCU Test on my Ftitzbox:
with: "aiccu autotest /var/mod/etc/aiccu.conf"
Result:
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (169.254.2.1)
### 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 169.254.2.1 (169.254.2.1): 56 data bytes
64 bytes from 169.254.2.1: seq=0 ttl=64 time=0.917 ms
64 bytes from 169.254.2.1: seq=1 ttl=64 time=0.565 ms
64 bytes from 169.254.2.1: seq=2 ttl=64 time=0.566 ms
--- 169.254.2.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.565/0.682/0.917 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.189)
### 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.224.0.189 (212.224.0.189): 56 data bytes
64 bytes from 212.224.0.189: seq=0 ttl=58 time=8.794 ms
64 bytes from 212.224.0.189: seq=1 ttl=58 time=8.196 ms
64 bytes from 212.224.0.189: seq=2 ttl=58 time=8.695 ms
--- 212.224.0.189 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 8.196/8.561/8.794 ms
######
####### [3/8] Traceroute to the PoP (212.224.0.189) 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.224.0.189 (212.224.0.189), 30 hops max, 38 byte packets
1 217.0.116.171 (217.0.116.171) 6.779 ms 6.465 ms 7.899 ms
2 217.0.72.242 (217.0.72.242) 6.759 ms 6.507 ms 8.064 ms
3 62.154.33.37 (62.154.33.37) 9.489 ms 8.226 ms 8.700 ms
4 217.243.219.86 (217.243.219.86) 7.981 ms 8.596 ms 7.707 ms
5 ge1-12.br2.isham.de.easynet.net (87.86.69.165) 9.549 ms 8.553 ms 8.688 ms
6 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 9.710 ms 8.571 ms 8.446 ms
7 212.224.0.189 (212.224.0.189) 8.920 ms 8.871 ms 9.671 ms
######
###### [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: seq=0 ttl=64 time=1.485 ms
64 bytes from ::1: seq=1 ttl=64 time=0.794 ms
64 bytes from ::1: seq=2 ttl=64 time=0.794 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.794/1.024/1.485 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:1c00:114::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:6f8:1c00:114::2 (2001:6f8:1c00:114::2): 56 data bytes
64 bytes from 2001:6f8:1c00:114::2: seq=0 ttl=64 time=0.883 ms
64 bytes from 2001:6f8:1c00:114::2: seq=1 ttl=64 time=0.833 ms
64 bytes from 2001:6f8:1c00:114::2: seq=2 ttl=64 time=1.434 ms
--- 2001:6f8:1c00:114::2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.833/1.050/1.434 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:1c00:114::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:6f8:1c00:114::1 (2001:6f8:1c00:114::1): 56 data bytes
--- 2001:6f8:1c00:114::1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
######
###### [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 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:6f8:1c00:114::2, 30 hops max, 16 byte packets
1 2001:6f8:1c00:114::1 (2001:6f8:1c00:114::1) 10.556 ms 9.952 ms 9.659 ms
2 2001:6f8:800:1003::209:55 (2001:6f8:800:1003::209:55) 11.055 ms 10.373 ms 9.992 ms
3 2001:6f8:800:0:1:0:d4e0:49a (2001:6f8:800:0:1:0:d4e0:49a) 11.794 ms 10.053 ms 9.966 ms
4 2001:6f8:1:0:87:86:71:240 (2001:6f8:1:0:87:86:71:240) 9.882 ms 9.849 ms 9.498 ms
5 2001:6f8:1:0:86:87:77:64 (2001:6f8:1:0:86:87:77:64) 26.516 ms 25.869 ms 25.208 ms
6 2001:6f8:1:0:87:82:50:236 (2001:6f8:1:0:87:82:50:236) 22.004 ms 23.055 ms 22.316 ms
7 2001:838:5:a::2 (2001:838:5:a::2) 27.171 ms 27.911 ms 27.195 ms
8 2001:838:1:1:210:dcff:fe20:7c7c (2001:838:1:1:210:dcff:fe20:7c7c) 27.539 ms 26.886 ms 27.416 ms
######
###### [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:6f8:1c00:114::2, 30 hops max, 16 byte packets
1 2001:6f8:1c00:114::1 (2001:6f8:1c00:114::1) 9.277 ms 10.217 ms 10.073 ms
2 2001:6f8:800:1003::209:55 (2001:6f8:800:1003::209:55) 10.048 ms 10.72 ms 9.521 ms
3 2001:6f8:800:0:1:0:d4e0:49a (2001:6f8:800:0:1:0:d4e0:49a) 11.303 ms 9.831 ms 9.484 ms
4 2001:6f8:1:0:87:86:71:240 (2001:6f8:1:0:87:86:71:240) 10.606 ms 9.883 ms 10.221 ms
5 2001:6f8:1:0:86:87:77:64 (2001:6f8:1:0:86:87:77:64) 28.028 ms 25.32 ms 25.077 ms
6 2001:6f8:1:0:87:86:77:68 (2001:6f8:1:0:87:86:77:68) 23.187 ms 23.125 ms 23.052 ms
7 2001:6f8:1:0:87:86:77:28 (2001:6f8:1:0:87:86:77:28) 364.807 ms 418.972 ms 35.167 ms
8 2001:6f8:1:0:87:86:77:120 (2001:6f8:1:0:87:86:77:120) 33.101 ms 32.62 ms 35.981 ms
9 2001:6f8:1:0:87:86:77:111 (2001:6f8:1:0:87:86:77:111) 103.181 ms 102.7 ms 103.306 ms
10 2001:6f8:1:0:87:86:77:105 (2001:6f8:1:0:87:86:77:105) 99.927 ms 100.255 ms 100.001 ms
11 2001:458:26:2::200 (2001:458:26:2::200) 100.572 ms 101.494 ms 101.432 ms
12 2001:48b0:bb00:8010::4014 (2001:48b0:bb00:8010::4014) 131.325 ms 131.274 ms 151.412 ms
13 2001:48b0:bb00:800f::400b (2001:48b0:bb00:800f::400b) 176.762 ms 177.213 ms 176.541 ms
14 2001:48b0:bb00:8004::73 (2001:48b0:bb00:8004::73) 273.054 ms 273.646 ms 273.693 ms
15 2001:240:bb00:9002::7d (2001:240:bb00:9002::7d) 274.46 ms 272.736 ms 288.13 ms
16 2001:240:bb01:31::15 (2001:240:bb01:31::15) 275.475 ms 275.942 ms 276.012 ms
17 2001:200:0:fe00::9c4:11 (2001:200:0:fe00::9c4:11) 277.713 ms 277.61 ms 277.276 ms
18 2001:200:0:1802:20c:dbff:fe1f:7200 (2001:200:0:1802:20c:dbff:fe1f:7200) 272.833 ms 273.635 ms 272.43 ms
19 2001:200:0:11::66 (2001:200:0:11::66) 274.303 ms 272.94 ms 272.305 ms
20 2001:200:0:12::74 (2001:200:0:12::74) 273.907 ms 273.49 ms 273.634 ms
21 2001:200:0:4803:212:e2ff:fe28:1ca2 (2001:200:0:4803:212:e2ff:fe28:1ca2) 274.02 ms 274.369 ms 274.09 ms
22 2001:200:0:8002:203:47ff:fea5:3085 (2001:200:0:8002:203:47ff:fea5:3085) 275.532 ms 275.032 ms 273.822 ms
######
###### 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.
--------------------------------------------------------------------------
I have -35 ISK, is that the Problem?
Fritzbox 7170 AICCU Modded, what is wrong?
Im modded the Fritzbox 7170 with Freez, and it is something wrong.
What problem exactly, except for:
PING 2001:6f8:1c00:114::1 (2001:6f8:1c00:114::1): 56 data bytes --- 2001:6f8:1c00:114::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss
Which just indicates that you can't ping the PoP endpoint. Firewalled, mis-routed? If you want people to help you debug this, provide the items requested for in the big orange box which references to the contact page.
I have -35 ISK, is that the Problem?
Negative ISK is not a problem, you only can't get new stuff. See the FAQ.
Fritzbox 7170 AICCU Modded, what is wrong?
Carmen Sandiego on Tuesday, 08 December 2009 16:37:27
In first test it works at all, but in second test the PoP endpoint fails.
It needs a reboot for my Fritzbox, than it works once more, but than the second test is ever the same result, the PoP endpoint fails.
I think i need the requested Subnet how same for the Fritzbox 7270.
But i have -35 ISK, i need 40 new ISK to have 15 ISK.
But i cant earn this 40 ISK at this state.
Do i need a new Account to resolve this Problem?
Fritzbox 7170 AICCU Modded, what is wrong?
Do i need a new Account to resolve this Problem?
Nope, you just need some patience and actually read, the FAQ is a good start.
Fritzbox 7170 AICCU Modded, what is wrong?
Carmen Sandiego on Tuesday, 08 December 2009 18:57:27
Now, a Forum Question:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
217.80.247.175 * 255.255.255.255 UH 2 0 0 dsl
192.168.180.1 * 255.255.255.255 UH 2 0 0 dsl
192.168.180.2 * 255.255.255.255 UH 2 0 0 dsl
192.168.178.0 * 255.255.255.0 U 0 0 0 lan
169.254.0.0 * 255.255.0.0 U 0 0 0 lan
default * 0.0.0.0 U 2 0 0 dsl
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::1/128 :: U 0 0 2 lo
2001:6f8:1c00:114::/128 :: U 0 0 2 lo
2001:6f8:1c00:114::/128 :: U 0 0 2 lo
2001:6f8:1c00:114::2/128 :: U 0 20 2 lo
2001:6f8:1c00:114::2/128 :: U 0 0 2 lo
2001:6f8:1c00:114::/64 :: U 256 21 0 sixxs
2001:6f8:1c00:114::/64 :: U 256 0 0 lan
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::a9fe:101/128 :: U 0 0 2 lo
fe80::a9fe:201/128 :: U 0 0 2 lo
fe80::c0a8:b201/128 :: U 0 0 2 lo
fe80::21c:4aff:fed2:605/128 :: U 0 0 2 lo
fe80::21c:4aff:fed2:605/128 :: U 0 0 2 lo
fe80::21c:4aff:fed2:605/128 :: U 0 0 2 lo
fe80::21c:4aff:fed2:605/128 :: U 0 0 2 lo
fe80::21c:4aff:fed2:605/128 :: U 0 0 2 lo
fe80::21c:4aff:fed2:605/128 :: U 0 0 2 lo
fe80::21c:4aff:fedf:5e66/128 :: U 0 0 2 lo
fe80::21c:4aff:fedf:5e66/128 :: U 0 0 2 lo
fe80::21c:4aff:fedf:5e66/128 :: U 0 33 2 lo
fe80::/64 :: U 256 0 0 cpmac0
fe80::/64 :: U 256 0 0 tiwlan0
fe80::/64 :: U 256 0 0 wdsup0
fe80::/64 :: U 256 0 0 wdsdw0
fe80::/64 :: U 256 0 0 wdsdw1
fe80::/64 :: U 256 0 0 wdsdw2
fe80::/64 :: U 256 0 0 wdsdw3
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 lan
fe80::/64 :: U 256 0 0 sixxs
ff02::1/128 ff02::1 UC 0 1 1 lan
ff00::/8 :: U 256 0 0 cpmac0
ff00::/8 :: U 256 0 0 tiwlan0
ff00::/8 :: U 256 0 0 wdsup0
ff00::/8 :: U 256 0 0 wdsdw0
ff00::/8 :: U 256 0 0 wdsdw1
ff00::/8 :: U 256 0 0 wdsdw2
ff00::/8 :: U 256 0 0 wdsdw3
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 lan
ff00::/8 :: U 256 0 0 sixxs
::/0 2001:6f8:1c00:114::1 UG 1024 67 0 sixxs
Fritz Box IPV6 expand - Script to add this to rc.custom
-----------------------------------------------------------------------------------------------------------------------------
####################### ipv6 firewall ###############################
IP6TABLES=ip6tables
ROUTER_ADDR="2001:6f8:1c00:114::2/64"
PREFIX="2001:6f8:1c00:114::1/64"
MODULES="ipv6 ip6_tables ip6table_filter ip6t_LOG ip6t_limit ip6t_rt"
echo -n "Starting firewall (ipv6)..."
# insert kernel modules
for i in $MODULES; do
modprobe $i
done
# delete all rules and chains
$IP6TABLES -F
$IP6TABLES -X
# default policies
$IP6TABLES -P INPUT DROP
$IP6TABLES -P OUTPUT ACCEPT
$IP6TABLES -P FORWARD DROP
# allow loopback
$IP6TABLES -A INPUT -i lo -j ACCEPT
# Remove RH0 vulnerability
$IP6TABLES -A INPUT -m rt --rt-type 0 -j DROP
# allow some icmpv6
$IP6TABLES -N ICMPV6
# 1: Destination Unreachable
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 1 -j ACCEPT
# 2: Packet Too Big
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 2 -j ACCEPT
# 3: Time Exceeded
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 3 -j ACCEPT
# 4: Parameter Problem
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 4 -j ACCEPT
# 128: Echo Request
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 128 -j ACCEPT
# 129: Echo Reply
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 129 -j ACCEPT
# 133: Router Solicitation
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 133 -j ACCEPT
# 134: Router Advertisement
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 134 -j ACCEPT
# 135: Neighbour Soliciation
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 135 -j ACCEPT
# 136: Neighbour Advertisement
$IP6TABLES -A ICMPV6 -p icmpv6 --icmpv6-type 136 -j ACCEPT
$IP6TABLES -A INPUT -p icmpv6 -j ICMPV6
# allow link local
$IP6TABLES -A INPUT -s fe80::/10 -d fe80::/10 -j ACCEPT
# allow ssh to router
$IP6TABLES -A INPUT -d $ROUTER_ADDR -p tcp --dport 22 -j ACCEPT
# log and drop the packages
$IP6TABLES -A INPUT -m limit -j LOG
# drop all new tcp connections
$IP6TABLES -A INPUT -p tcp --syn -j DROP
# drop all packages
$IP6TABLES -A INPUT -j DROP
# forward rules: allow routing between lan and sixxs
$IP6TABLES -A FORWARD -m rt --rt-type 0 -j DROP
$IP6TABLES -A FORWARD -i lan -o sixxs -s $PREFIX -j ACCEPT
$IP6TABLES -A FORWARD -i sixxs -o lan -d $PREFIX -j ACCEPT
# output: allow loopback (for accounting)
$IP6TABLES -A OUTPUT -o lo -j ACCEPT
$IP6TABLES -A OUTPUT -m rt --rt-type 0 -j DROP
echo "done."
--------------------------------------------------------------------------------------------------------
First AICCU Test with "aiccu autotest /var/mod/etc/aiccu.conf"
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (169.254.2.1)
### 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 169.254.2.1 (169.254.2.1): 56 data bytes
64 bytes from 169.254.2.1: seq=0 ttl=64 time=1.559 ms
64 bytes from 169.254.2.1: seq=1 ttl=64 time=0.564 ms
64 bytes from 169.254.2.1: seq=2 ttl=64 time=0.563 ms
--- 169.254.2.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.563/0.895/1.559 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.189)
### 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.224.0.189 (212.224.0.189): 56 data bytes
64 bytes from 212.224.0.189: seq=0 ttl=58 time=12.074 ms
64 bytes from 212.224.0.189: seq=1 ttl=58 time=34.935 ms
64 bytes from 212.224.0.189: seq=2 ttl=58 time=10.900 ms
--- 212.224.0.189 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 10.900/19.303/34.935 ms
######
####### [3/8] Traceroute to the PoP (212.224.0.189) 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.224.0.189 (212.224.0.189), 30 hops max, 38 byte packets
1 217.0.116.171 (217.0.116.171) 6.241 ms 6.376 ms 7.294 ms
2 217.0.72.242 (217.0.72.242) 8.619 ms 6.994 ms 7.769 ms
3 62.154.33.34 (62.154.33.34) 11.268 ms 9.533 ms 10.812 ms
4 217.243.219.86 (217.243.219.86) 25.643 ms 9.447 ms 8.501 ms
5 ge3-7.br2.isham.de.easynet.net (87.86.71.241) 11.399 ms 10.434 ms 9.667 ms
6 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 10.221 ms 16.020 ms 8.574 ms
7 212.224.0.189 (212.224.0.189) 14.171 ms 9.549 ms 9.458 ms
######
###### [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: seq=0 ttl=64 time=0.870 ms
64 bytes from ::1: seq=1 ttl=64 time=0.800 ms
64 bytes from ::1: seq=2 ttl=64 time=0.795 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.795/0.821/0.870 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:1c00:114::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:6f8:1c00:114::2 (2001:6f8:1c00:114::2): 56 data bytes
64 bytes from 2001:6f8:1c00:114::2: seq=0 ttl=64 time=0.889 ms
64 bytes from 2001:6f8:1c00:114::2: seq=1 ttl=64 time=0.821 ms
64 bytes from 2001:6f8:1c00:114::2: seq=2 ttl=64 time=1.516 ms
--- 2001:6f8:1c00:114::2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.821/1.075/1.516 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:1c00:114::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:6f8:1c00:114::1 (2001:6f8:1c00:114::1): 56 data bytes
64 bytes from 2001:6f8:1c00:114::1: seq=0 ttl=64 time=11.087 ms
64 bytes from 2001:6f8:1c00:114::1: seq=1 ttl=64 time=12.472 ms
64 bytes from 2001:6f8:1c00:114::1: seq=2 ttl=64 time=11.066 ms
--- 2001:6f8:1c00:114::1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 11.066/11.541/12.472 ms
######
###### [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 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:6f8:1c00:114::2, 30 hops max, 16 byte packets
1 2001:6f8:1c00:114::1 (2001:6f8:1c00:114::1) 13.737 ms 11.477 ms 10.16 ms
2 2001:6f8:800:1003::209:55 (2001:6f8:800:1003::209:55) 27.54 ms 17.031 ms 10.983 ms
3 2001:6f8:800:0:1:0:d4e0:49a (2001:6f8:800:0:1:0:d4e0:49a) 11.284 ms 12.707 ms 31.324 ms
4 2001:6f8:1:0:87:86:71:240 (2001:6f8:1:0:87:86:71:240) 14.347 ms 11.387 ms 29.087 ms
5 2001:6f8:1:0:86:87:77:64 (2001:6f8:1:0:86:87:77:64) 26.251 ms 26.677 ms 26.41 ms
6 2001:6f8:1:0:87:82:50:236 (2001:6f8:1:0:87:82:50:236) 23.264 ms 25.449 ms 54.466 ms
7 2001:838:5:a::2 (2001:838:5:a::2) 30.429 ms 30.462 ms 44.458 ms
8 2001:838:1:1:210:dcff:fe20:7c7c (2001:838:1:1:210:dcff:fe20:7c7c) 30.438 ms 35.42 ms 28.234 ms
######
###### [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:6f8:1c00:114::2, 30 hops max, 16 byte packets
1 2001:6f8:1c00:114::1 (2001:6f8:1c00:114::1) 11.048 ms 41.144 ms 11.271 ms
2 2001:6f8:800:1003::209:55 (2001:6f8:800:1003::209:55) 17.912 ms 11.16 ms 10.952 ms
3 2001:6f8:800:0:1:0:d4e0:49a (2001:6f8:800:0:1:0:d4e0:49a) 26.143 ms 187.109 ms 202.329 ms
4 2001:6f8:1:0:87:86:71:240 (2001:6f8:1:0:87:86:71:240) 11.816 ms 11.007 ms 12.384 ms
5 2001:6f8:1:0:86:87:77:64 (2001:6f8:1:0:86:87:77:64) 28.358 ms 26.881 ms 27.928 ms
6 2001:6f8:1:0:87:86:77:68 (2001:6f8:1:0:87:86:77:68) 43.53 ms 158.166 ms 40.635 ms
7 2001:6f8:1:0:87:86:77:28 (2001:6f8:1:0:87:86:77:28) 693.229 ms 326.242 ms 183.671 ms
8 2001:6f8:1:0:87:86:77:120 (2001:6f8:1:0:87:86:77:120) 35.026 ms 33.876 ms 32.889 ms
9 2001:6f8:1:0:87:86:77:111 (2001:6f8:1:0:87:86:77:111) 105.18 ms 104.926 ms 104.463 ms
10 2001:6f8:1:0:87:86:77:105 (2001:6f8:1:0:87:86:77:105) 106.538 ms 100.141 ms 100.837 ms
11 2001:458:26:2::200 (2001:458:26:2::200) 107.374 ms 114.831 ms 102.045 ms
12 2001:48b0:bb00:800b::400b (2001:48b0:bb00:800b::400b) 184.623 ms 192.039 ms 185.67 ms
13 2001:48b0:bb00:8004::73 (2001:48b0:bb00:8004::73) 287.374 ms 282.365 ms 280.017 ms
14 2001:240:bb00:9002::7d (2001:240:bb00:9002::7d) 279.712 ms 279.189 ms 287.782 ms
15 2001:240:bb01:31::15 (2001:240:bb01:31::15) 283.047 ms 287.722 ms 291.143 ms
16 2001:200:0:fe00::9c4:11 (2001:200:0:fe00::9c4:11) 284.352 ms 284.031 ms 284.868 ms
17 2001:200:0:1802:20c:dbff:fe1f:7200 (2001:200:0:1802:20c:dbff:fe1f:7200) 294.327 ms 295.069 ms 279.104 ms
18 2001:200:0:11::66 (2001:200:0:11::66) 281.244 ms 279.397 ms 285.221 ms
19 2001:200:0:12::74 (2001:200:0:12::74) 280.249 ms 280.775 ms 279.535 ms
20 2001:200:0:4803:212:e2ff:fe28:1ca2 (2001:200:0:4803:212:e2ff:fe28:1ca2) 280.164 ms 298.701 ms 281.628 ms
21 2001:200:0:8002:203:47ff:fea5:3085 (2001:200:0:8002:203:47ff:fea5:3085) 280.736 ms 280.556 ms 302.954 ms
######
###### 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.
--------------------------------------
Second Test than fails at : ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:1c00:114::1)
---------------------------------------------------------------------------------------------------------------
Aiccu config result with "cat /mod/etc/aiccu.conf"
username own
password own
tunnel_id own
ipv6_interface sixxs
protocol tic
server tic.sixxs.net
verbose false
daemonize true
automatic true
pidfile /var/run/aiccu.pid
-------------------------------------------------------------------
Radvd result with "cat /mod/etc/radvd.conf"
interface lan
{
AdvSendAdvert on;
prefix 2001:6f8:1c00:114::1/64
{
};
};
------------------------------------------------------------------
Freetz bootlog:
/var/log/mod_load.log
Loading /var/flash/freetz...done.
Loading users, groups and passwords...done.
Loading hosts...done.
Loading config...done.
Loading modules...done.
/var/log/mod.log
rc.mod version freetz-devel-4012
crond is disabled
telnetd is disabled
Starting Freetz webinterface...done.
Starting dropbear SSH server...done.
Starting aiccu...done.
Setting up SSH authorized_keys for root...initialized.
Set IPv6 address: 2001:6f8:1c00:114::2/64 done.
Enable IPv6 forwarding...done.
Starting radvd...done.
Starting firewall (ipv6)...done.
Starting swap...done.
---------------------------------------------------------------
Have someone in this Forum a Idea, what is the Problem?
Fritzbox 7170 AICCU Modded, what is wrong?
There are several problems:
- you use the tunnel /64 on the tunnel (correct) and on the lan (wrong), you need a /64 from a subnet for the latter, thus also remove it from the radvd.
- you are using both rfc1918 (192.16.0.0/16) and autoconf (169.254.0.0/16) on your network, IPv4 is really only made to use one address per interface, it might work for a bit but weird things will happen.
- read up what ICMP is and what each type does, you are clearly doing firewalliing the wrong way.
Fritzbox 7170 AICCU Modded, what is wrong?
Carmen Sandiego on Thursday, 10 December 2009 18:14:15
OK, i found out that at this time Fritzboxes supports only Tic.
To go on next step i need the Requestet Subnet.
For first i can only wait for ISKs, than i can compile a Freetz - Image.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 08 December 2009 09:53:37
Posting is only allowed when you are