Re: [gentoo-user] systemd-networkd: simpler config for my network

[Stefan G. Weichinger]

Am 15.04.2014 20:25, schrieb Stefan G. Weichinger:

> Tom Gundersen, one of the main coders said "IPv6 support is so far very
> basic (you can set static IPv6 addresses, and that's it). We plan to
> support it fully in the future though."
>
> -> https://plus.google.com/+TomGundersen/posts/8d1tzMJWppJ
>
> Maybe things developed since then.

I took the opportunity and asked Tom myself (we were in contact last
week due to my questions around my KVM-related network-setup).

Some quotes out of his reply, I showed him this thread for a start.

->

> Am 15.04.2014 19:25, schrieb Pavel Volkov:
>>> Not yet, but it seems weird to have DHCP= for DHCPv4 and not to have any
>>> options (DHCPv6/SLAAC/unconfigured) for IPv6. Only Address= for static
>>> address.
>
> Currently, the only IPv6 support we have is static addresses and
> whatever the kernel provides natively. The reason for this is just
> lack of hours in the day, and it is definitely on the TODO. We expect
> to have DHCPv6 soon, but the patches have not yet been posted. Any
> further assistance in the form of patches or testing would be greatly
> appreciated of course.
>
>>> Here is another problem. I need to issue this command:
>>> "ip token set ::2/64 dev br0"
>>> 1. after the bridge device is created
>>> 2. before IP address is configured on it
>
> This seems like a useful feature and should be simple to implement.
> Can't promise to work on that any time soon though, but, again,
> patches would be appreciated.
>
>>> netctl still seems a lot more capable than systemd-networkd...
>
> Yes, we still have a lot of features left on our TODO. Things are
>
>>> And netctl runs separate services (line netctl@××××.service) for
>>> separate interfaces unlike systemd-networkd, you can create more custom
>>> deps on top of it.
>
> That is also true, but this was a conscious choice from our side. Most
> of the deps (as the token use-case you mentioned above) are sorted out
> by networkd internally (when support is added), so the config remains
> purely declarative. Moreover, exposing network state simply as systemd
> units is not really powerful enough, as we probably want much more
> fine-grained status information (if an interface is up, if it has a
> link-local address assigned, a routable address assigned, if the
> global internet is reachable etc, etc.). We have therefore taken the
> approach of exposing this info (and more, such as DHCP leases and
> their associated information) through a C library. The plan is to
> obviously also add a dbus API.
>
>> And it is not meant to be a drop-in replacement for big guns like
>> gnome-networkmanager or netctl, but just a simple tool for static setups.
>
> True, we target mainly static setups (i.e., ones where you don't
> usually change the network configuration at run-time, though you may
> still use dynamic configuration such as DHCP of course). However, we
> still have a lot more features we need/want before we are done
>
>> Maybe things developed since then.
>
> Not really. I have been working mostly on IPv4 so far, but Patrik
> Flykt from Intel is hard at work on DHCPv6, so that should be coming
> along soon.
>
> Cheers,
>
> Tom

So IPv6 isn't yet much supported as you noticed, right.

Interesting anyway, isn't it?

Best, Stefan