Re: /etc/network/interfaces in jessie and systemd?
On 2015-04-22 14:20:00 +0200, Michael Biebl wrote: Am 22.04.2015 um 10:21 schrieb Vincent Lefevre: On 2015-04-21 17:27:46 +0200, Michael Biebl wrote: The ifup@.service is triggered by a udev rule and responsible to handle allow-hotplug interfaces. I hope that this will remain always optional. For a laptop at least, that's not the correct way to do. Are you advocating the use of auto over allow-hotplug I'm not advocating the use of auto either. Well, auto is OK for lo, but my point is that neither auto nor allow-hotplug is OK for eth* or wlan*, at least when the network can change (e.g. for a laptop). or the use of something enirely else, more dynamic, like network-manager? Yes, something better than allow-hotplug, like the netplug package (for eth*). I don't know how network-manager works; perhaps it can do similar things? The problem with allow-hotplug is that it makes the interface UP even when the interface is not ready for that, e.g. when an Ethernet cable is not plugged in. Waiting for an Ethernet link may be needed for the configuration, e.g. when using mapping and test peer ... mac Or when a laptop is moved from a network to another one, one may want to have the scripts under /etc/network rerun when an Ethernet cable is unplugged / plugged in, and things like that. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150423080017.ga24...@xvii.vinc17.org
Re: /etc/network/interfaces in jessie and systemd?
Am 22.04.2015 um 10:21 schrieb Vincent Lefevre: On 2015-04-21 17:27:46 +0200, Michael Biebl wrote: The ifup@.service is triggered by a udev rule and responsible to handle allow-hotplug interfaces. I hope that this will remain always optional. For a laptop at least, that's not the correct way to do. Are you advocating the use of auto over allow-hotplug or the use of something enirely else, more dynamic, like network-manager? I'm not quite sure what you mean with remain always optional though. Care to elaborate? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: /etc/network/interfaces in jessie and systemd?
On 2015-04-21 17:27:46 +0200, Michael Biebl wrote: The ifup@.service is triggered by a udev rule and responsible to handle allow-hotplug interfaces. I hope that this will remain always optional. For a laptop at least, that's not the correct way to do. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150422082135.ga20...@xvii.vinc17.org
Re: /etc/network/interfaces in jessie and systemd?
Am 21.04.2015 um 14:08 schrieb Mihamina Rakotomandimby:
Hi all,
I used to manage network through /etc/network/interfaces.
Most of my use case are vlans (ie: eth0.1) an aliases (ie: eth1:3)
My context in headless VMs (no DE, no Xorg, no GUI)
With Jessie and systemd: is it still managed with /etc/network/interfaces?
systemd-networkd is an optional component and shipped as disabled by
default in jessie.
If you've configured your network to use ifupdown and
/etc/network/interfaces, it will continue to work as-is.
If you want to give systemd-networkd a try, you'd have to convert/create
your network configuration for networkd manually. There is no automatic
conversion to systemd.{link,network,netdev} configuration files from
/etc/network/interfaces.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Re: /etc/network/interfaces in jessie and systemd?
Hi there, Am 2015-04-21 16:06, schrieb Michael Biebl: Am 21.04.2015 um 15:42 schrieb Christian Seiler: There is something called systemd-networkd, which is not part of Jessie's systemd version, but will (probably) be part of future Debian versions. This offers an alternative way to configure networking. Note, however, that systemd-networkd by default does not touch any network interfaces, you have to tell it explicitly to do something - so even if that were to be installed, as long as the old networking scripts still exist, they'd still be used instead of systemd's component - and only if you explicitly configure something there will it actually do anything. This doesn't concern Jessie anyway, because it doesn't contain that program. Not quite correct. The systemd package in jessie does ship systemd-networkd, but it is disabled by default. If you want to use networkd, you'd have to run systemctl enable systemd-network[d].service and configure it. Oh, interesting, didn't know that, thanks for the pointer. Christian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/a4fe686d64b19ffc746a1c44aff34...@iwakd.de
Re: /etc/network/interfaces in jessie and systemd?
Am 21.04.2015 um 15:42 schrieb Christian Seiler: There is something called systemd-networkd, which is not part of Jessie's systemd version, but will (probably) be part of future Debian versions. This offers an alternative way to configure networking. Note, however, that systemd-networkd by default does not touch any network interfaces, you have to tell it explicitly to do something - so even if that were to be installed, as long as the old networking scripts still exist, they'd still be used instead of systemd's component - and only if you explicitly configure something there will it actually do anything. This doesn't concern Jessie anyway, because it doesn't contain that program. Not quite correct. The systemd package in jessie does ship systemd-networkd, but it is disabled by default. If you want to use networkd, you'd have to run systemctl enable systemd-network.service and configure it. networkd in v215, which is shipped in jessie, is missing some important features though, like e.g. the networkctl command line tool. I'd consider networkd in jessie a tech preview. Good enough for users to play with it in simple environments and get used to it, but not mature yet to have it enabled by default. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: /etc/network/interfaces in jessie and systemd?
On 04/21/2015 04:42 PM, Christian Seiler wrote: Hi, Am 2015-04-21 14:08, schrieb Mihamina Rakotomandimby: I used to manage network through /etc/network/interfaces. Most of my use case are vlans (ie: eth0.1) an aliases (ie: eth1:3) My context in headless VMs (no DE, no Xorg, no GUI) With Jessie and systemd: is it still managed with /etc/network/interfaces? ... To summarize: you should have no surprises under Jessie w.r.t. network configuration. I've set up a couple of different types of configuration (even complex ones) with Jessie so far (using /etc/network/interfaces) and didn't run into any trouble. didn't have Christian Thank you Christian, Just to be sure, I saw that: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1374521 https://github.com/linuxmint/systemd/blob/master/debian/ifup@.service If my reading and deduction is correct, systemd will call ifup that will read /etc/network/interface. But what is going to detect all interfaces and give them as argument to each systemd ifup service call? Thank you. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55365cc2.7000...@rktmb.org
Re: /etc/network/interfaces in jessie and systemd?
Hi, Am 2015-04-21 14:08, schrieb Mihamina Rakotomandimby: I used to manage network through /etc/network/interfaces. Most of my use case are vlans (ie: eth0.1) an aliases (ie: eth1:3) My context in headless VMs (no DE, no Xorg, no GUI) With Jessie and systemd: is it still managed with /etc/network/interfaces? Yes, Debian Jessie still uses /etc/init.d/networking, which reads /etc/network/interfaces by default. (Even on systemd systems, that script is executed.) Two comments here: - if you install some network managing daemon, such as NetworkManager, then this might override the /etc/network configuration, but that is nothing new in Jessie, this was already the case in previous Debian versions - NFS mounts are now done by systemd itself, so instead of using the hook previous Debian versions used to mount NFS shares once the interface is active, Jessie now makes systemd wait for the network and then lets it mount the NFS shares directly. (I had NO trouble with NFS mounts on Jessie, with the same fstab entries as under Wheezy, so unless you do something really weird, the old configuration should still work as expected, the mechanism is now just a little different.) For the mount component, I found that systemd kind of sources /etc/fstab and converts it to something for it (so, no worry about fstab), but how about networking? There is something called systemd-networkd, which is not part of Jessie's systemd version, but will (probably) be part of future Debian versions. This offers an alternative way to configure networking. Note, however, that systemd-networkd by default does not touch any network interfaces, you have to tell it explicitly to do something - so even if that were to be installed, as long as the old networking scripts still exist, they'd still be used instead of systemd's component - and only if you explicitly configure something there will it actually do anything. This doesn't concern Jessie anyway, because it doesn't contain that program. To summarize: you should have no surprises under Jessie w.r.t. network configuration. I've set up a couple of different types of configuration (even complex ones) with Jessie so far (using /etc/network/interfaces) and didn't run into any trouble. didn't have Christian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/f696446c00c13830d65358e9ff0c9...@iwakd.de
Re: /etc/network/interfaces in jessie and systemd?
Am 21.04.2015 um 16:06 schrieb Michael Biebl: If you want to use networkd, you'd have to run systemctl enable systemd-network.service Thats systemctl enable systemd-networkd.service. Note the missing 'd' -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
/etc/network/interfaces in jessie and systemd?
Hi all, I used to manage network through /etc/network/interfaces. Most of my use case are vlans (ie: eth0.1) an aliases (ie: eth1:3) My context in headless VMs (no DE, no Xorg, no GUI) With Jessie and systemd: is it still managed with /etc/network/interfaces? For the mount component, I found that systemd kind of sources /etc/fstab and converts it to something for it (so, no worry about fstab), but how about networking? Thanks.
Re: /etc/network/interfaces in jessie and systemd?
Am 21.04.2015 um 16:20 schrieb Mihamina Rakotomandimby: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1374521 https://github.com/linuxmint/systemd/blob/master/debian/ifup@.service If my reading and deduction is correct, systemd will call ifup that will read /etc/network/interface. But what is going to detect all interfaces and give them as argument to each systemd ifup service call? The ifup@.service is triggered by a udev rule and responsible to handle allow-hotplug interfaces. It basically works the same as in wheezy. The difference is, that in wheezy, the udev rule [1] called ifup directly, under systemd it calls ifup@interface.service, and this service does nothing else then run ifup interface. This has the benefit, that systemd can track it properly. Michael [1] /lib/udev/rules.d/80-networking.rules -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: /etc/network/interfaces in jessie and systemd?
Am 2015-04-21 16:20, schrieb Mihamina Rakotomandimby: Thank you Christian, Just to be sure, I saw that: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1374521 https://github.com/linuxmint/systemd/blob/master/debian/ifup@.service I think that's Ubuntu-specific; even though ifup@.service is installed on Debian systems, at least on my Jessie box it's never been activated (on a system that actually uses /etc/network/interfaces) - at least systemctl says so. If my reading and deduction is correct, systemd will call ifup that will read /etc/network/interface. systemd just starts /etc/init.d/networking on my systems (the same script that is also used under Wheezy, Squeeze, Lenny, etc.) and that in turn calls ifup in the same way it has previously been called under Wheezy etc. I don't see it starting ifup@.service anywhere. Michael, what's up with that service? Christian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ab3a2faf9b8a5cbe7dd2dc63513c4...@iwakd.de
Re: /etc/network/interfaces in jessie and systemd?
Am 21.04.2015 um 17:15 schrieb Christian Seiler: Am 2015-04-21 16:20, schrieb Mihamina Rakotomandimby: Thank you Christian, Just to be sure, I saw that: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1374521 https://github.com/linuxmint/systemd/blob/master/debian/ifup@.service I think that's Ubuntu-specific; even though ifup@.service is installed on Debian systems, at least on my Jessie box it's never been activated (on a system that actually uses /etc/network/interfaces) - at least systemctl says so. If my reading and deduction is correct, systemd will call ifup that will read /etc/network/interface. systemd just starts /etc/init.d/networking on my systems (the same script that is also used under Wheezy, Squeeze, Lenny, etc.) and that in turn calls ifup in the same way it has previously been called under Wheezy etc. I don't see it starting ifup@.service anywhere. Michael, what's up with that service? /etc/init.d/networking (or networking.service) is responsible for handling auto interfaces in Debian, ifup@.service, triggered via udev, is responsible for handling allow-hotplug interfaces. If you don't have any ifup@.service instances running, and you do use ifupdown, I guess your interfaces are all marked auto in /etc/network/interfaces. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
