On Wed, Oct 31, 2018 at 03:00:02PM -0400, Tom Horsley wrote:
> I swear I tried to find out what rpm provided /etc/rc.d/init.d/network
> and go no results. Maybe I made a typo. I guess I'll try using NM
> again. After it never worked properly in the first umpteen fedora releases
> I gave up even attempting to use it. Maybe it is better now.
If you don't need or don't want advanced functionality, you may be
interested in configure-and-quit mode:
configure-and-quit
When set to 'true', NetworkManager quits after performing initial
network configuration but spawns small helpers to preserve DHCP
leases and IPv6 addresses. This is useful in environments where
network setup is more or less static or it is desirable to save
process time but still handle some dynamic configurations. When
this option is true, network configuration for WiFi, WWAN,
Bluetooth, ADSL, and PPPoE interfaces cannot be preserved due to
their use of external services, and these devices will be
deconfigured when NetworkManager quits even though other
interface's configuration may be preserved. Also, to preserve DHCP
addresses the 'dhcp' option must be set to 'internal'. The default
value of the 'configure-and-quit' option is 'false', meaning that
NetworkManager will continue running after initial network
configuration and continue responding to system and hardware
events, D-Bus requests, and user commands.
--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
