Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
On Apr 8, 2014, at 10:42 PM, xinglp wrote: wpa_supplicant support systemd already. Yeah, I had it going with systemd long ago, but without systemd- networkd. Looks like as long as you have all the configuration setup properly it will work fine. I haven't tried it with systemd-networkd, yet. SIncerely, WIlliam Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
Am 08.04.2014 16:40, schrieb xinglp: $ journalctl -b|grep enp Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the enp4s0 interface...Cannot find device enp4s0 Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to enp4s0 So it won't startup network. Wouldn't it be the easiest way to let systemd configure the network interfaces? http://coreos.com/blog/intro-to-systemd-networkd/ http://www.freedesktop.org/software/systemd/man/systemd.link.html http://www.freedesktop.org/software/systemd/man/systemd.network.html -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
xinglp wrote: $ journalctl -b|grep enp Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the enp4s0 interface...Cannot find device enp4s0 Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to enp4s0 So it won't startup network. Are you using /etc/udev/rules.d/70-persistent-net.rules? In the latest book it should be created automatically. I don't know what rule would cause renaming from eth0 to anything. BTW, the contents of 70-persistent-net.rules has changed lately. The predicate KERNEL==something has been removed. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
2014-04-09 0:07 GMT+08:00 Bruce Dubbs bruce.du...@gmail.com: xinglp wrote: $ journalctl -b|grep enp Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the enp4s0 interface...Cannot find device enp4s0 Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to enp4s0 So it won't startup network. Are you using /etc/udev/rules.d/70-persistent-net.rules? No In the latest book it should be created automatically. I don't know There's no 70-persistent-net.rules when in vmware or qemu. I haven't test it on real machine. what rule would cause renaming from eth0 to anything. BTW, the contents of 70-persistent-net.rules has changed lately. The predicate KERNEL==something has been removed. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
2014-04-08 22:50 GMT+08:00 Sebastian Plotz sebastian-pl...@web.de: Am 08.04.2014 16:40, schrieb xinglp: $ journalctl -b|grep enp Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the enp4s0 interface...Cannot find device enp4s0 Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to enp4s0 So it won't startup network. Wouldn't it be the easiest way to let systemd configure the network interfaces? http://coreos.com/blog/intro-to-systemd-networkd/ http://www.freedesktop.org/software/systemd/man/systemd.link.html http://www.freedesktop.org/software/systemd/man/systemd.network.html Thanks, I'll try to learn this way. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
2014-04-09 0:07 GMT+08:00 Bruce Dubbs bruce.du...@gmail.com: xinglp wrote: $ journalctl -b|grep enp Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the enp4s0 interface...Cannot find device enp4s0 Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to enp4s0 So it won't startup network. This issue only in vmware, not qemu. Are you using /etc/udev/rules.d/70-persistent-net.rules? In the latest book it should be created automatically. I don't know what rule would cause renaming from eth0 to anything. BTW, the contents of 70-persistent-net.rules has changed lately. The predicate KERNEL==something has been removed. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
2014-04-08 22:50 GMT+08:00 Sebastian Plotz sebastian-pl...@web.de: Am 08.04.2014 16:40, schrieb xinglp: $ journalctl -b|grep enp Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the enp4s0 interface...Cannot find device enp4s0 Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to enp4s0 So it won't startup network. Wouldn't it be the easiest way to let systemd configure the network interfaces? It works well for my problemed vmware. I think we don't need ifup ifdown script for systemd now. http://coreos.com/blog/intro-to-systemd-networkd/ http://www.freedesktop.org/software/systemd/man/systemd.link.html http://www.freedesktop.org/software/systemd/man/systemd.network.html -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
On Apr 8, 2014, at 8:00 PM, xinglp wrote: Wouldn't it be the easiest way to let systemd configure the network interfaces? It works well for my problemed vmware. I think we don't need ifup ifdown script for systemd now. It's best to let systemd's networkd deal with all of the network. You can change interface names, setup bonds, and all kinds of other configurations and settings. The only reason a person will not want to use systemd networkd is when: the dhcp server requires more information from a dhcp client which systemd networkd's dhcp client can't provide (such as a hostname) wireless is to be used with encryption and probably some others. When having both systemd and sysvinit in the LFS Book, the network section would be best written so that if a user is using systemd, do this if using sysvinit, do this. Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] systemd ifup get run before systemd rename interface sometimes.
2014-04-09 10:12 GMT+08:00 William Harrington kb0...@berzerkula.org: On Apr 8, 2014, at 8:00 PM, xinglp wrote: Wouldn't it be the easiest way to let systemd configure the network interfaces? It works well for my problemed vmware. I think we don't need ifup ifdown script for systemd now. It's best to let systemd's networkd deal with all of the network. You can change interface names, setup bonds, and all kinds of other configurations and settings. The only reason a person will not want to use systemd networkd is when: the dhcp server requires more information from a dhcp client which systemd networkd's dhcp client can't provide (such as a hostname) And there's no dhcp ipv6 cleint in systemd. wireless is to be used with encryption wpa_supplicant support systemd already. see this https://bbs.archlinux.org/viewtopic.php?id=178625 and probably some others. When having both systemd and sysvinit in the LFS Book, the network section would be best written so that if a user is using systemd, do this if using sysvinit, do this. Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
