You are not logged in.
Hi
In my new installation i want to switch to a simple systemd-networkd config.
Currently NetworkManager (NM) is installed, but I only need one Ethernet connection which should be up ASAP after powering on.
First I have disabled the NM service.
Then I have created a rule in UDEV renaming my only device to net0
# change the network device name by defining the name manually
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="23:4b:35:49:e0:58", NAME="net0"
# Enable WOL on net0/1/2 ...
ACTION=="add", SUBSYSTEM=="net", KERNEL=="net*", RUN+="/usr/bin/ethtool -s %k wol g"
Created a /etc/systemd/network/HomeLAN.network
[Match]
Name=net*
[Network]
DHCP=ipv4
Followed by:
systemctl enable systemd-networkd.service
On every boot I get a 1min30sec timeout saying
a start job is running sys-subsystem-net-devices-enp2s0.device
Although networking is fine through net0 i would like to remove this.
Any help greatly appreciated.
Last edited by boomshalek (2017-03-15 20:38:37)
Offline
systemd-networkd works great on this system. What is the output of find /etc/systemd on your system?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Why bother renaming the interface?
Offline
Rename using networkd, also set WoL via networkd
/etc/systemd/network/20-net0.link
[Match]
MACAddress=23:4b:35:49:e0:58
[Link]
Name=net0
WakeOnLan=magic
/etc/systemd/network/20-net0.network
[Match]
Name=net0
[Network]
DHCP=ipv4
enjoy
Offline
Hi guys
Beautiful solutions. Thank you very much.
I still had a file in place which caused the delay
/etc/udev/rules.d/81-dhcpcd.rules
ACTION=="add", SUBSYSTEM=="net", ENV{INTERFACE}=="en*|eth*", ENV{SYSTEMD_WANTS}="dhcpcd@$name.service"
But i am now using yopur methods for WOL etc.
Very nice.
SOLVED
Last edited by boomshalek (2017-03-15 20:38:19)
Offline