Freek de Kruijf wrote:
Op zondag 22 februari 2015 21:40:40 schreef Per Jessen:
Freek de Kruijf wrote:
Op zondag 22 februari 2015 18:55:59 schreef Per Jessen:
Per Jessen wrote:
Per Jessen wrote:
Is there a reason for this to be running on systems that don't have interfaces with DHCPv6 ?
Ping?
The system has no knowledge about IPv6 being present on the interface or not, it is you who has, so the standard is: it assumes there might be IPv6 on the interface and when it is, it tries to use it.
Okay. Perhaps I should have phrased the question differently - what is the purpose of wickedd-dhcp6 (in general, but specifically on systems with _no_ interface configured for DHCPv6) ?
Does this mean that you have disabled IPv6 in the General settings?
No, IPv6 is enabled as such, I never disable it, but I have no interfaces with DHCPv6 enabled.
And did you choose only DHCP4 in all the interfaces?
Right. (only one interface).
In that case there should not be any need for DHCPv6 or any IPv6 services, not even the Link-Local Address Generation.
The link-local addresses are there, and I might assign IPv6 addresses via/with radvd.
I mean, "man wickedd" says that wickedd-dhcpv6 is a "DHCPv6 client supplicant", but when there are no interfaces configured for dhcpv6, it doesn't seem to be needed. If wicked doesn't know the local network config, well ....
Otherwise this daemon might be involved in IPv6 Stateless Auto Configuration as a minimum.
Yes, that is a possibility. I guess we don't know if that is the case? There is certainly still an issue with RDNSS info not being used to update /etc/resolv.conf : https://bugzilla.opensuse.org/show_bug.cgi?id=916613 -- Per Jessen, Zürich (0.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org