Jan Tomasek a écrit :
> Benoit Branciard wrote:
>>
>> IPv6 forwarding is still mandatory, but this implies manual 
>> configuration of IP address, netmask and default route on hardware 
>> node. This last point may be annoying: in our case the default route 
>> is hardware-dependent, so if some day we need to replace the router 
>> (or the router interface), default route will become invalid and 
>> manual reconfiguration of all openVZ hardware nodes will be needed.
>> Too bad Linux kernel doesn't allow enabling forwarding without 
>> disabling autoconfiguration.
> 
> I'm not sure, but I think that my setup is router independent. For my 
> virtual servers I got prefix 2001:718:1:e::/64 (which is unbelivable 
> waste of IP range but they say this is normal in IPv6). This network 
> block is asigned to dedicated VLAN. IPv6 Gateway for all physical 
> systems in that network is 2001:718:1:e::1.

Here's the clue: you have been assigned a static gateway IP address by 
your network provider. So no problem.

In our case we are operating our nework, and have chosen to not set 
static gateway IP adresses, relying on autoconfiguration to discover the 
EUI-64 (MAC-dependant) default route IP. That sounded nice (nothing to 
hardcode) until openVZ came on.
Maybe we could change our router config policy, and assign static IP 
addresses to router interfaces. But that's not trivial operation, 
involving network downtime, and we wont do that without motivated reasons.

-- 
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.