Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 659178

Summary: systemd link files ignored for making settings on network adapter like WOL
Product: Gentoo Linux Reporter: Mehmet Giritli <mehmet>
Component: Current packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED NEEDINFO    
Severity: normal CC: jstein
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Mehmet Giritli 2018-06-25 20:06:50 UTC
I'm trying to make the wake on lan settng persistent on a headless machine. Network is setup by systemd networkd. To enable and make WOL setting persistent, I am trying to use systemd link files.

I have a /etc/systemd/network/50_WOL.link file with:

[Link]
WakeOnLan=magic

in it and it is having no effect, despite numerous examples that it should work are available on the net. The interesting thing is, when I run the following, the WOL will be enabled! But otherwise WOL is disabled. It is like systemd/udev is not parsing the file or something and I believe that this could be a bug in gentoo.

$udevadm test-builtin net_setup_link /sys/class/net/eth0/

calling: test-builtin
Load module index
Parsed configuration file /lib64/systemd/network/99-default.link
Parsed configuration file /etc/systemd/network/50_WOL.link
Created link configuration context.
ID_NET_DRIVER=r8169
Config file /etc/systemd/network/50_WOL.link applies to device eth0
link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Could not set Alias, MACAddress or MTU on eth0: Device or resource busy
Could not apply link config to eth0, ignoring: Device or resource busy
ID_NET_LINK_FILE=/etc/systemd/network/50_WOL.link
Unload module index
Unloaded link configuration context.
Comment 1 Jonas Stein gentoo-dev 2018-08-19 18:10:22 UTC
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/