Florian Lohoff <[email protected]> writes: > we have v6 in the LAN running for years and everything is fine. The thing > missing is > the possibility to hand out ipv6 Nameservers e.g. DHCPv6. Currently we only > do > SLAAC.
Are all the clients Linux? If so, then you can get away with using the RDNSS option in radvd.conf and rdnssd on the clients. Don't know if other OSes support RFC5006 yet. It's only 5 years old, so I guess we cannot expect that. I'd recommend using the RDNSS option in any case, to support the clients which can use it. > I tried using wide-dhcpv6-server and failed to get it to work on multiple > interfaces on > the same machine which does not seem to work. ( e.g. vlans - eth0.5, eth0.10, > eth0.10 etc). > > It fails to start with: > > Jun 8 09:40:06 dhcp-server dhcp6s[26452]: dhcp6_ctl_init: bind(control > sock): Address already in use > Jun 8 09:40:06 dhcp-server dhcp6s[26452]: server6_init: failed to initialize > control channel I tried to reproduce this, but could not: frtest5:~# grep INT /etc/default/wide-dhcpv6-server INTERFACES="eth0 eth2 eth3" frtest5:~# /etc/init.d/wide-dhcpv6-server start [ ok ] Starting WIDE DHCPv6 server on eth0: dhcp6s. [ ok ] Starting WIDE DHCPv6 server on eth2: dhcp6s. [ ok ] Starting WIDE DHCPv6 server on eth3: dhcp6s. frtest5:~# ps aux|grep dhcp6 root 14223 0.0 0.3 4204 480 ? Ss 12:27 0:00 /usr/sbin/dhcp6s -k /dev/null -P /var/run/dhcp6s.eth0.pid eth0 root 14248 0.0 0.3 4204 480 ? Ss 12:27 0:00 /usr/sbin/dhcp6s -k /dev/null -P /var/run/dhcp6s.eth2.pid eth2 root 14273 0.0 0.3 4204 480 ? Ss 12:27 0:00 /usr/sbin/dhcp6s -k /dev/null -P /var/run/dhcp6s.eth3.pid eth3 root 14295 0.0 0.7 7816 872 pts/0 S+ 12:29 0:00 grep dhcp6 You could also try the ISC dhcp server. It has some IPv6 support, although it's not exactly polished yet... > Next thing is that i dont have a clue what the state of the network-manager + > dhcpv6 is. > Google finds some Fedora pages beeing concerned about the added dependency on > dhcpv6 which > i even fail to find - my guess is thats the isc dhcp v6 client. Simply > installing > the wide-dhcpv6-client seems to be broken as its not network-manager > integrated. Don't know much about these things, but I believe there has been a few IPv6 related patches on the NM list recently. This is most likely WIP. > Another thing would be resolvconf - Is it v6 aware? The wide dhcpv6 client will provide a $new_domain_name_servers variable to a shell script of your choice, so it should be easy to fix. I don't think the ISC client supports any sort of scripting for IPV6 yet, but I could be wrong. rdnssd recommends resolvconf, so I expect it supports it. Bjørn -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
