IPv6 for LAN clients: something missing?
Shadow Hawkins on Saturday, 10 October 2009 19:05:53
Hi all
I have IPv6 working on my FreeBSD server/ADSL-gateway; in a terminal I can ping6 ipv6.google.com and "lynx http://www.kame.net" indicates the dancing kame.
Next step is to enable IPv6 for LAN clients. On the server, I have these lines in my rc.conf file:
[...]
ipv6_gateway_enable="YES"
rtadvd_enable="YES"
rtadvd_interfaces="rl0"
[...]
On a Fedora 11 client, I have added this line "IPV6INIT=yes" to the file
/etc/sysconfig/networking/devices/ifcfg-eth0
Now, when I restart the networking this is what I see:
$ ifconfig | grep inet6
inet6 addr: 2001:610:645:3:217:31ff:fecd:e17d/64 Scope:Global
inet6 addr: fe80::217:31ff:fecd:e17d/64 Scope:Link
inet6 addr: ::1/128 Scope:Host
The first line looks promising, as is appears within the subnet which I obtained here: 2001:610:645::/48
However, I can't ping6 google:
$ ping6 ipv6.google.com
PING ipv6.google.com(fx-in-x68.google.com) 56 data bytes
From 2001:610:645:3:217:31ff:fecd:e17d icmp_seq=2 Destination unreachable: Address unreachable
[...]
Some piece of the puzzle is still missing. Can someone point me in the right direction?
Thanks,
Colin
IPv6 for LAN clients: something missing?
Shadow Hawkins on Sunday, 11 October 2009 20:57:51
Check your IPv6 firewall settings on the machine you are using as the IPv6 router.
IPv6 for LAN clients: something missing?
Jeroen Massar on Monday, 12 October 2009 14:12:09 From 2001:610:645:3:217:31ff:fecd:e17d icmp_seq=2 Destination unreachable: Address unreachable
That is your local host (the host itself) responding. As such:
- check the routing tables:
* Do you have a proper default route (::/0) via another host?
- check if you have forwarding enabled on this client host
(When forwarding is enabled, Linux does not honor ::/0 routes)
"traceroute6 <host>" is btw what you want to do in these kind of situations, as then you already see on which host things go wrong.
Posting is only allowed when you are logged in. |