On 06/05/09 12:43, Daniel P. Berrange wrote:
I'm not sure that we should automatically run radvd, because this
has
potential implications for the host as a whole. It is hard to restrict
scope to just the virbr0 interface, as we do with IPv4 using NAT.
We could run a separate instance of radvd using a custom configuration
file (-C option), limiting it to the bridge interface, like so:
interface virbr0
{
IgnoreIfMissing on;
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvDefaultPreference low;
AdvHomeAgentFlag off;
#bernie: we actually have a /48, thus 65536 /64 subnets
prefix 2001:4978:243:1::0/64
{
AdvOnLink on;
AdvAutonomous on;
};
};
--
// Bernie Innocenti -
http://codewiz.org/
\X/ Sugar Labs -
http://sugarlabs.org/