[systemd-devel] systemd-nspawn and IPv6

[Dimitri John Ledkov]

On 27 April 2015 at 15:56, Lennart Poettering <lennart at poettering.net> wrote:
> On Mon, 27.04.15 15:44, Dimitri John Ledkov (dimitri.j.ledkov at intel.com) wrote:
>
>> > Well, networkd on the host automatically sets up IPv4 masquerading for
>> > each container. We simply don't do anything equivalent for IPv6
>> > currently.
>> >
>> > Ideally we wouldn't have to do NAT for IPv6 to make this work, and
>> > instead would pass on some ipv6 subnet we acquired from uplink without
>> > NAT to each container, but we currently don't have infrastructure for
>> > that in networkd, and I am not even sure how this could really work,
>> > my ipv6-fu is a bit too limited...
>> >
>> > or maybe we should do ipv6 nat after all, under the logic that
>> > containers are just an implementation detail of the local host rather
>> > than something to be made visible to the outside world. however code
>> > for this exists neither.
>> >
>> > Or in other words: ipv6 setup needs some manual networking setup on
>> > the host.
>>
>> One should roll the dice and generate unique local address /48 prefix
>> and use that to setup local addressing, ideally with
>> autoconfigurations (e.g. derive a fake mac from container uuid and
>> using the "hosts's" ULA prefix auto-assign ipv6 address)
>
> Well, would that enable automatic, correcting routing between the
> container and the host's external network? That's kinda what this all
> is about...

yes... that is host needs to be assigned a subnet and ip from /48, and
containers routed via that host ip.

Or "simply" (aka "expensively") run radvd on the host for the
containers to do all of that (route & ULA prefix advertisement and
complete auto-configuration therefore)

-- 
Regards,

Dimitri.
Pura Vida!

https://clearlinux.org
Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.