SixXS::Sunset 2017-06-06

Cannot get subnet working
[ie] Shadow Hawkins on Monday, 25 July 2011 16:29:47
router runs radvd on debian6 router can ping6 any address radvd configured as follows on router: root@plug:~# cat /etc/radvd.conf interface eth0 { AdvSendAdvert on; MinRtrAdvInterval 3; MaxRtrAdvInterval 10; prefix 2001:xxx:xxx:xxx::1/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr on; }; }; But it's not working. From a client I get destination host unreachable. I assume I have the prefix wrong... :) I just cut and pasted what was assigned to me. Any suggestions?
Cannot get subnet working
[ch] Jeroen Massar SixXS Staff on Monday, 25 July 2011 16:34:33
prefix 2001:xxx:xxx:xxx::1/64
What are the real numbers there? Also, did you add that address to eth0?
Cannot get subnet working
[de] Shadow Hawkins on Monday, 25 July 2011 19:14:15
Hi, please provide the output of the following commands: ifconfig eth0 cat /proc/sys/net/ipv6/conf/all/forwarding /etc/init.d/radvd stop /usr/sbin/radvd -d 3 -m stderr -u radvd -p /var/run/radvd/radvd.pid netstat -6 -rn for which command did you get a "destination host unreachable"? which typ of client ? BR Martin
Cannot get subnet working
[ie] Shadow Hawkins on Tuesday, 26 July 2011 10:25:12
Router config - debian6 auto eth0 #iface eth0 inet dhcp #allow-hotplug eth0 iface eth0 inet static address 192.168.0.184 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.1 dns-domain conor.local dns-nameservers 192.168.0.184 # ipv6 tunnel auto sixxs iface sixxs inet6 v4tunnel address 2001:770:100:14d::2 #netmask 2001:770:100:14d::1/64 netmask 64 ##endpoint [PoP IPv4 Endpoint] endpoint 193.1.31.74 ttl 64 up ip link set mtu 1280 dev sixxs up ip route add default via 2001:770:100:14d::1 dev sixxs ip addr list root@plug:~# ip addr list 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether f0:ad:4e:00:6a:b0 brd ff:ff:ff:ff:ff:ff inet 192.168.0.184/24 brd 192.168.0.255 scope global eth0 inet6 fe80::f2ad:4eff:fe00:6ab0/64 scope link valid_lft forever preferred_lft forever 3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN link/sit 0.0.0.0 brd 0.0.0.0 4: sixxs: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN link/sit 0.0.0.0 peer 193.1.31.74 inet6 2001:770:100:14d::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::c0a8:b8/64 scope link valid_lft forever preferred_lft forever root@plug:~# cat /proc/sys/net/ipv6/conf/all/forwarding 1 root@plug:~# netstat -6 rn Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State root@plug:~# radvd -d 3 -m stderr -u radvd -p /var/run/radvd/radvd.pid [Jul 26 08:32:54] radvd: version 1.6 started [Jul 26 08:32:54] radvd: mtu for eth0 is 1500 [Jul 26 08:32:54] radvd: hardware type for eth0 is 1 [Jul 26 08:32:54] radvd: link layer token length for eth0 is 48 [Jul 26 08:32:54] radvd: prefix length for eth0 is 64 [Jul 26 08:32:54] radvd: Initializing privsep [Jul 26 08:32:54] radvd: sending RA on eth0 [Jul 26 08:32:54] radvd: setting timer: 10.00 secs [Jul 26 08:33:04] radvd: sending RA on eth0 [Jul 26 08:33:04] radvd: setting timer: 3.38 secs [Jul 26 08:33:07] radvd: sending RA on eth0 and so forth a client (fedora15) gets the following: [conor@lapdog ~]$ ip addr list 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 00:1d:72:9a:c1:4f brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:21:5c:57:05:27 brd ff:ff:ff:ff:ff:ff inet 192.168.0.186/24 brd 192.168.0.255 scope global wlan0 inet6 2001:770:100:14d:221:5cff:fe57:527/64 scope global dynamic valid_lft 86393sec preferred_lft 14393sec inet6 fe80::221:5cff:fe57:527/64 scope link valid_lft forever preferred_lft forever 4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN link/ether ae:97:52:3b:cb:79 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 [conor@lapdog ~]$ ping6 ipv6.google.com PING ipv6.google.com(dy-in-x63.1e100.net) 56 data bytes No response. The destination host unreachable is no longer happenning, not sure what I had changed though but I was playing around with it a lot trying to make it work. I can only access this site once I disable radvd you see. So I take it from Jeroen's response that I need to add the ipv6 address to my eth0 config as well? Any suggestions as to what specific entries I need to add? Its just that the router is headless, and if I feck it up I'll be stuffed until I can re-attach a serial console again. Without the plug there is no internet, phone system, nothing :) Thanks guys for the helpful replies.
Cannot get subnet working
[ch] Jeroen Massar SixXS Staff on Tuesday, 26 July 2011 11:50:02
address 192.168.0.184
iface sixxs inet6 v4tunnel
You are behind a NAT and are using a proto-41 tunnel, that won't work unless you are able to configure your NAT box to forward every single proto-41 packet to your host, which is just trying luck.
inet6 2001:770:100:14d:221:5cff:fe57:527/64 scope global dynamic
That is an address out of the tunnel prefix, that can't work. You need to use a /64 out of a routed subnet.
[conor@lapdog ~]$ ping6 ipv6.google.com
PING ipv6.google.com(dy-in-x63.1e100.net) 56 data bytes
Why are you even trying to ping that. Always do a traceroute to a remote host, and start at trying to reach the PoP, when you can reach the PoP, you can try reaching the rest of the Internet.
So I take it from Jeroen's response that I need to add the ipv6 address to my eth0 config as well? Any suggestions as to what specific entries I need to add?
Start by reading the FAQ on how to set this all up, it has a lot of useful details. Then try to debug it using the details requested by the "problem checklist" on the contact page, as indicated by that big yellow/orange box. But first off, get a subnet and use that. You might want to check the RUNNING configuration.
Cannot get subnet working
[de] Shadow Hawkins on Tuesday, 26 July 2011 20:49:38
Hi, I got some additional comments, please check your config of eth0, I think you need a static Ipv6 (of your subnet) on this interface. according to your posting you don't have one. change your radvd config, you are advertising a prefix, this sould look like prefix xxx:xxx:xxx:xx::/64 and not like xxx:xxx:xxx:xx::1/64 (but this "should" not make a difference.) I've been asking for the output of "netstat -6 -rn" not "netstat -6 rn" this is a minor differnce. according your data you configured a tunelinterface named sixxs, but looking at the output of "ip addr list" this interface does not exsist. -> guess you can not ping your POP -> if not it's clear why you can't ping ipv6 google.com. -> see the last comment. BR Martin
Cannot get subnet working
[de] Shadow Hawkins on Tuesday, 26 July 2011 21:12:18
hi, ignore this one "according your data you configured a tunelinterface named sixxs, but looking at the output of "ip addr list" this interface does not exsist. -> guess you can not ping your POP -> if not it's clear why you can't ping ipv6 google.com. -> see the last comment" problem between keyboard and chair on my side ...

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker