On Wed, 2018-10-31 at 08:06 -0400, Tom Horsley wrote: I'm still seeing network.target in systemctl. poc

On 10/31/18 5:06 AM, Tom Horsley wrote: It's not gone yet, but it will be sometime... $ service network status WARN : [network] You are using 'network' service provided by 'network-scripts', which are now deprecated. WARN : [network] 'network-scripts' will be removed from distribution in near future. WARN : [network] It is advised to switch to 'NetworkManager' instead for network management. Configured devices: lo eth0 Currently active devices: lo eth0 Note that 'network' has never been a systemd unit, its always been the old style sysvinit script, so you need to use 'service' and 'chkconfig' with it. kevin

On Wed, Oct 31, 2018 at 03:00:02PM -0400, Tom Horsley wrote: 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(a)fedoraproject.org&gt; Fedora Project Leader

On Wed, 31 Oct 2018 15:00:02 -0400 Tom Horsley wrote: The basic stuff seemed to work OK, but I suspect my big problem will be getting my wifi dongle to work as an access point. I think that was what caused me to give up in disgust last time I tried NM, it kept grabbing it and trying to connect to wifi and I couldn't for the life of me figure out how to make it act like an access point under NM. Running hostapd and dhcpd manually worked fine once I turned off NM.