[Users] OpenVZ and IPv6

[Pavel Odintsov]

Heh, sorry. I should be more clear. I want to delegate whole /64
subnet and customer could decide how much IP's he need. He could use
only ::1 but he could use as much as possible IP addresses.

On Thu, Jun 18, 2015 at 11:50 PM, Pavel Odintsov
<pavel.odintsov at gmail.com> wrote:
> Hello!
>
> Yep, I do not want whole /64 to container. I wan't to provide whole
> subnet. And customer could decide what IP's he need.
>
> On Thu, Jun 18, 2015 at 11:30 PM, Volker Janzen <voja at voja.de> wrote:
>> Hi,
>>
>> I don't think it's possible to add a complete /64 to a container. Commercial solutions I know allow to add single IPv6 from a /64 to a container, but not in bulk. This would also eat many ressources, even if the kernel could handle the large number of /64 IPs. Perhaps the list of IPs could exceed container memory.
>>
>>
>> Regards
>>    Volker
>>
>>
>>> Am 18.06.2015 um 18:13 schrieb Pavel Odintsov <pavel.odintsov at gmail.com>:
>>>
>>> Hello, folks!
>>>
>>> I deployed IPv6 two years ago and everything goes smooth.
>>>
>>> But there are some guidance from RIPE about IPv6 allocation. And I
>>> want to mention they there. Every company receives /48 IPv6 allocation
>>> (65 535 of /64 networks) and each end side device should receive /64
>>> subnet.
>>>
>>> Actually, for OpenVZ I should allocate /128 IPv6 IP's for customers
>>> instead of /64. It's die to "openvz features" in this case.
>>>
>>> Do you have any ideas about ability to add /64 subnet per container
>>> instead ugly /128?
>>>
>>> Thank you so much!
>>>
>>> --
>>> Sincerely yours, Pavel Odintsov
>>> _______________________________________________
>>> Users mailing list
>>> Users at openvz.org
>>> https://lists.openvz.org/mailman/listinfo/users
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
>
>
>
> --
> Sincerely yours, Pavel Odintsov



-- 
Sincerely yours, Pavel Odintsov