From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] Anyone opposed to dropping runtime dhclient dependency for NetworkManager
Date: Wed, 05 Jun 2019 17:45:09 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12167@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
New issue by thomas-t-w on void-packages repository
https://github.com/void-linux/void-packages/issues/12167
Description: NetworkManager has a built in dhcp server which I have been using for a few days now. It seems to be faster and more reliable in band steering senarios. I have tested on a few networks, one being Eduroam which uses wpa2 enterprise and I haven't had troubles. I would propose that the runtime dependency only be dropped and the default still be left at dhclient. If dhclient isn't installed. if a user installed NetworkManager, they will get the built-in dhcp server by default because NetworkManager falls back to that. If the user installs dhclient, they will get that because it is set by default which makes it easy if someone runs into a problem which I don't expect but it is obviously possible. If a user has dhclient installed and they want the dhcp server built into NetworkManager, they clearly know what they are doing and can change it manually in NetworkManagers config. Any opposed to this change? I will leave this open for a few days and close it if I don't hear anything and open a pull request with the change.
next reply other threads:[~2019-06-05 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:45 voidlinux-github [this message]
2019-06-05 15:50 ` voidlinux-github
2019-06-05 15:54 ` voidlinux-github
2019-06-06 15:27 ` voidlinux-github
2019-06-06 15:32 ` voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12167@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).