Re: [gentoo-user] systemd-224 Look out for new networking behavior
Am Tue, 4 Aug 2015 00:37:54 +0100 schrieb Neil Bothwick n...@digimed.co.uk: On Mon, 3 Aug 2015 08:50:24 -0500, Canek Peláez Valdés wrote: Is this server-related? I have only simple workstations/laptops and I don't enable systemd-networkd at all. It seems that NetworkManager takes care of both wired and wireless without assistance (including dhcp). In latptops/workstations NetworkManager takes care of everything. However, I still enable systemd-networkd and systemd-resolved in my laptop and workstations. If enabled without any configuration, it just monitors the network interfaces and keeps them in the loop for the rest of the system to know about them from a central registry. It doesn't interfere with NetworkManager (or any other network management program for that matter). Alternatively, you can use systemd-networkd and do without NetworkManager altogether, avoiding a load of dependencies if you don't use GNOME. For typical wireless networks, wpa_gui is more than adequate for configuration. I concur, I switched to systemd-netword over two months ago. This replaced netctl on my desktop, and both netctl and NetworkManager on my laptop. My experience with it so far has been just as good as with netifrc and netctl. The only potential downside is that (at least AFAICT) there is no way to restart an individual network. HTH -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup pgppGWpWP2Iov.pgp Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] systemd-224 Look out for new networking behavior
On Mon, 3 Aug 2015 08:50:24 -0500, Canek Peláez Valdés wrote: Is this server-related? I have only simple workstations/laptops and I don't enable systemd-networkd at all. It seems that NetworkManager takes care of both wired and wireless without assistance (including dhcp). In latptops/workstations NetworkManager takes care of everything. However, I still enable systemd-networkd and systemd-resolved in my laptop and workstations. If enabled without any configuration, it just monitors the network interfaces and keeps them in the loop for the rest of the system to know about them from a central registry. It doesn't interfere with NetworkManager (or any other network management program for that matter). Alternatively, you can use systemd-networkd and do without NetworkManager altogether, avoiding a load of dependencies if you don't use GNOME. For typical wireless networks, wpa_gui is more than adequate for configuration. -- Neil Bothwick Bugs are Sons of Glitches pgpDNwnOwouKy.pgp Description: OpenPGP digital signature
Re: [gentoo-user] systemd-224 Look out for new networking behavior
On Mon, Aug 03 2015, Canek Peláez Valdés wrote: In latptops/workstations NetworkManager takes care of everything. However, I still enable systemd-networkd and systemd-resolved in my laptop and workstations. If enabled without any configuration, it just monitors the network interfaces and keeps them in the loop for the rest of the system to know about them from a central registry. It doesn't interfere with NetworkManager (or any other network management program for that matter). It's not mandatory to enable them either. However, there were advantages to doing so; for example, in my laptop, systemd-timesyncd would try to sync the clock only if there was a network connection available. Thank you for the clarification. I will follow your lead. allan
Re: [gentoo-user] systemd-224 Look out for new networking behavior
On Mon, Aug 3, 2015 at 8:30 AM, gottl...@nyu.edu wrote: On Sun, Aug 02 2015, Canek Peláez Valdés wrote: On Sun, Aug 2, 2015 at 10:03 AM, walt w41...@gmail.com wrote: I've been running systemd for a long time without needing to enable the dhcpcd service at boot time. Starting with systemd-224 that is no longer true. Today I had to enable dhcpcd.service specifically or the network interface didn't get an ip address during boot. Seems like this might be especially important for those of you who need to update remote machines. If you enable systemd-networkd.service, and your .network file has DHCP=yes in its [Network] section, then it will use the DHCP client included with systemd-networkd. In my servers I not longer use any net-misc/*dhcp* package. Regards. Is this server-related? I have only simple workstations/laptops and I don't enable systemd-networkd at all. It seems that NetworkManager takes care of both wired and wireless without assistance (including dhcp). In latptops/workstations NetworkManager takes care of everything. However, I still enable systemd-networkd and systemd-resolved in my laptop and workstations. If enabled without any configuration, it just monitors the network interfaces and keeps them in the loop for the rest of the system to know about them from a central registry. It doesn't interfere with NetworkManager (or any other network management program for that matter). It's not mandatory to enable them either. However, there were advantages to doing so; for example, in my laptop, systemd-timesyncd would try to sync the clock only if there was a network connection available. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd-224 Look out for new networking behavior
On Sun, Aug 02 2015, Canek Peláez Valdés wrote: On Sun, Aug 2, 2015 at 10:03 AM, walt w41...@gmail.com wrote: I've been running systemd for a long time without needing to enable the dhcpcd service at boot time. Starting with systemd-224 that is no longer true. Today I had to enable dhcpcd.service specifically or the network interface didn't get an ip address during boot. Seems like this might be especially important for those of you who need to update remote machines. If you enable systemd-networkd.service, and your .network file has DHCP=yes in its [Network] section, then it will use the DHCP client included with systemd-networkd. In my servers I not longer use any net-misc/*dhcp* package. Regards. Is this server-related? I have only simple workstations/laptops and I don't enable systemd-networkd at all. It seems that NetworkManager takes care of both wired and wireless without assistance (including dhcp). thanks, allan
Re: [gentoo-user] systemd-224 Look out for new networking behavior
On Sun, Aug 2, 2015 at 10:03 AM, walt w41...@gmail.com wrote: I've been running systemd for a long time without needing to enable the dhcpcd service at boot time. Starting with systemd-224 that is no longer true. Today I had to enable dhcpcd.service specifically or the network interface didn't get an ip address during boot. Seems like this might be especially important for those of you who need to update remote machines. If you enable systemd-networkd.service, and your .network file has DHCP=yes in its [Network] section, then it will use the DHCP client included with systemd-networkd. In my servers I not longer use any net-misc/*dhcp* package. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd-224 Look out for new networking behavior
On Sun, 2 Aug 2015 08:03:11 -0700, walt wrote: I've been running systemd for a long time without needing to enable the dhcpcd service at boot time. Starting with systemd-224 that is no longer true. Today I had to enable dhcpcd.service specifically or the network interface didn't get an ip address during boot. What are you using for network management? I've just found I had to enable systemd-networkd.service to get the network up. Of course, this happens just when I made some changes to my network setup, so I started undoing those changes before realising systemd had changed behaviour. Maybe I should start reading Changelogs... -- Neil Bothwick Facts are stubborn things, but statistics are more pliable. - Mark Twain pgppgKiITOnoj.pgp Description: OpenPGP digital signature
[gentoo-user] systemd-224 Look out for new networking behavior
I've been running systemd for a long time without needing to enable the dhcpcd service at boot time. Starting with systemd-224 that is no longer true. Today I had to enable dhcpcd.service specifically or the network interface didn't get an ip address during boot. Seems like this might be especially important for those of you who need to update remote machines.
