On 5/31/23 9:18 AM, Peter Robinson wrote:
NetworkManager has defaulted to it's own dhcp client by default for
some time and systemd-networkd has it's own as well, I suspect actual
users are quite minimal. I'm not sure if anything like cloud-init uses
it but I also doubt it.
I'll come out of my shell to cough up as one of those "minimal" users. I'm using it
only on a single server that is still using "network-scripts" for network
management. Yes, I know they are deprecated. I wouldn't be surprised if there are a
few other "network-scripts" users. The scripts call dhclient.
It would be nice if a change notice went out about it.
This email is not intended to be a "-1" or other negative response. I will end up
changing network management to something else.
I'm not using NetworkManager due to an issue with IPv6 and SLAAC. Clients under the
server get an initial SLAAC IP from NetworkManager, but after the IP expires they
never get a new IP. I've asked upstream about it and didn't get anywhere. Granted,
this was 3 years ago now. Maybe things are better and I can try NetworkManager
again... or systemd-networkd.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
