|
Autoconfiguration, radvd, and servers
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 07 June 2007 20:31:17
I have a simple policy (best practice) question regarding servers and IPv6 autoconfiguration.
I have radvd running on my router. It works fine, and seems to be a blessing for desktop machines, wireless clients, etc.
But what about servers? They accept the router advertisements too. Is it preferred to go ahead and allow the autoconfiguration to take place on servers, and assign them additional ipv6 addresses manually? Or is it preferred to disable autoconfiguration on these machines? I see Linux has a sysctl net.ipv6.conf.default.accept_ra which can be used to disable autoconfiguration.
What are other people doing?
Thanks,
Jeff
Autoconfiguration, radvd, and servers
Servers have two things: they are a 'box' and provide a 'service'.
As such, use the RA's to autoconfigure the 'box', but provide the services with static IP addresses. This way you can address them separately. Using SSH to access the machine itself directly on it's own IP and then even have the possibility of moving the 'service' addresses to other boxes etc.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 07 June 2007 20:38:28
Posting is only allowed when you are