I have a home network consisting of one linux box, 2 winxp sp3. I set up an ipv6 tunnel per instructions and what I could find documented and had an initial problem that the linux box would access the ipv6 easily but the windows boxes would not make any connections at all. Leaving most of the experimentation out of this story, I finally got all boxes using ipv6 by making radvd prefix the same as my routed ipv6 /64 prefix given here and giving my linux system a manual global address in the if-cfg file. It doesn't seem to matter what ipv6 address I use as long as I assign it first. If I don't assign it manually it never gets an address even with radvd running. The addresses appear to be assigned to the win boxes by radvd running on the linux box. I have seen explanations that imply I should set it up so that my hurricane routed prefix provides the global address to all the boxes so that each box gets its address from that not the local LAN radvd.
I don't know how to do this and can not find any explanations how, just that it should be done. How do I get the global ipv6 addresses from my tunnel?
If I'm following your post correctly, I think you're over th)ng this.
1) host your tunnel on linux (done)
2) configure radvd to advertise your routed prefix, which to this point you haven't used yet.
3) configure other hosts to get an address from radvd (most modern os's do this automatically)
If I'm missing something, please let me know
Yep, this is the scenario that I use.
I have radvd (prefix & route) and wide-dhcp6 (specific addrs for each host) on my Linux system with the HE tunnel.
Quote from: cholzhauer on August 15, 2013, 07:44:36 PM
If I'm following your post correctly, I think you're over th)ng this.
1) host your tunnel on linux (done)
2) configure radvd to advertise your routed prefix, which to this point you haven't used yet.
3) configure other hosts to get an address from radvd (most modern os's do this automatically)
If I'm missing something, please let me know
I very well could be over thinking it but finding details of setting this up is difficult.
Things seem to be working correctly but I don't know if they could be working better.
I find out now that my linux laptop wifi is getting kicked off every once in a while that didn't happen before but I can work on that later.
It could be related to the ipv6 address, I don't know.
And I noticed I didn't mention before that the tunnel is going through a FiOS router, if that changes anything. The linux box is not acting as a gateway.
Anyway I guess my main question here is:
Do I explicitly use this line in the radvd.conf file : prefix 2001:470:d:dee::/64
My full radvd commands;
interface wlan0
{
AdvSendAdvert on;
IgnoreIfMissing on;
prefix 2001:470:d:dee::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
The previous poster mentioned setting the route also. I haven't seen references to this before.
Is wide-dhcp6 a substitute for radvd? radvd seems to hand out addresses on its own.
And do I explicitly assign an address in the ifcfg-wlan0 file as : IPV6ADDR=2001:470:d:dee::/64
or should I explicitly list the full "hextet" that will be assigned by radvd. Is it important to assign the wlan0 an address of the same prefix as the one in radvd and as the one assign to the tunnel. It didn't seem to matter when I was testing it.
Quote from: terryipvsix on August 19, 2013, 10:57:40 PM
The previous poster mentioned setting the route also. I haven't seen references to this before.
Is wide-dhcp6 a substitute for radvd? radvd seems to hand out addresses on its own.
Sorta. You need to use RADVD to set the route (DHCPv6 does not do this) RADVD is fine for most implementations; use DHCPv6 if you want more control over which hosts are assigned which addresses or if you need to pass along other info (DNS, ect)
Quote from: cholzhauer on August 20, 2013, 05:17:36 AM...
Sorta. You need to use RADVD to set the route (DHCPv6 does not do this) RADVD is fine for most implementations; use DHCPv6 if you want more control over which hosts are assigned which addresses or if you need to pass along other info (DNS, ect)
fwiw, FreeBSD's rtadvd and rtsol can set DNS servers. I know it works on FreeBSD 9.1, I do not know if that capability is in earlier versions.
If you do set DNS via rtadvd for IPv6 and DNS via dhcp for IPv4, then you may want to introduce yourself to the resolvconf (http://www.freebsd.org/cgi/man.cgi?query=resolvconf&apropos=0&sektion=0&manpath=FreeBSD+9.1-RELEASE&arch=default&format=html) program. Otherwise you'll have a race condition at /etc/resolv.conf