On Fri, 15 Jul 2011 20:21:56 +0000 (UTC), Stuart Henderson wrote:
On 2011-07-15, Eric <e...@nyx.fm> wrote:
 Hello folks,

 I'm trying to setup an IPv6 address on my server, it's a simple box
with a nic connected to the internet, the housing facility provided me
 with a /64 matching my IPv4 address and told me to setup rtadv.

 Quite easy I thought, looking at hostname.if(5), I added a simple
"inet6 alias 2001:41d0:2:1d4f::1 64" to my hostname.sis0, turned rtadv

 Upon reboot, ifconfig shows me
        inet6 fe80::21c:c0ff:fe82:9213%sis0 prefixlen 64 scopeid 0x1

 Another reboot without the "alias" flag in the hostname.sis0, and
 ifconfig gives me the following result:
        inet6 fe80::21c:c0ff:fe82:9213%sis0 prefixlen 64 scopeid 0x1
        inet6 2001:41d0:2:1d4f::1 prefixlen 64

 I made sure pf allows icmp6 through to get the gateway address, but
 looking at my routing I suspected something was wrong.
 Checking with rtsol I end up with the following result:
 # rtsol -d sis0
 checking if sis0 is ready...
 sis0 is ready
 send RS on sis0, whose state is 2
 received RA from fe80::5:73ff:fea0:0 on sis0, state is 2
 stop timer for sis0
 there is no timer

The documentation of the housing facility tells me their routers are
 always on ::FF:FF:FF:FF:FF so I tried a ping6:
 # ping6 2001:41d0:2:1F:FF:FF:FF:FF
 PING6(56=40+8+8 bytes) 2001:41d0:2:1d4f::1 -->
 2001:41d0:2:1f:ff:ff:ff:ff
 ^C
 --- 2001:41d0:2:1F:FF:FF:FF:FF ping6 statistics ---
 7 packets transmitted, 0 packets received, 100.0% packet loss

Most documents I found on the web focus on setting up things through
 tunnels as most providers still don't offer IPv6 connectivity yet.
 What am I missing here?



The address you're trying to ping is outside of your subnet,
should it be 2001:41d0:2:1d4f:ff:ff:ff:ff ?

$ sipcalc 2001:41d0:2:1d4f::/64 | grep -A1 range
Network range           - 2001:41d0:0002:1d4f:0000:0000:0000:0000 -
                          2001:41d0:0002:1d4f:ffff:ffff:ffff:ffff

netstat -rnfinet6 might give clues.
Thank you for pointing that out Stuart, it was of course the wrong
subnet, but as I figured a while later, the ipv6 configuration
was right, pinging with ping6 -I sis0 returned working replies
from both ipv6.google.com and some other addresses.
I'm not yet very familiar with all the IPv6 subtle changes but
working on it.

Regards.

Reply via email to