I’m using cpe:/o:opensuse:tumbleweed:20240308. My last installation (using a different motherboard — unfortunately, I have forgotten which) correctly accepted WOL packets after I configured them via the OS (hence why I’m asking here) but I don’t seem to be able to get my current installation to accept them following what I believe to be the same steps.
Does anyone have any ideas of what I might need to do?
Configuration
sudo ethtool wlp69s0
Settings for wlp69s0:
Link detected: yes
PS /home/RokeJulianLockhart> sudo ethtool enp75s0
Settings for enp75s0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
master-slave cfg: preferred slave
master-slave status: slave
Port: Twisted Pair
PHYAD: 0
Transceiver: external
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: d
Link detected: yes
sudo ethtool -s enp75s0 wol g
sudo ethtool enp75s0
Settings for enp75s0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
master-slave cfg: preferred slave
master-slave status: slave
Port: Twisted Pair
PHYAD: 0
Transceiver: external
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: g
Link detected: yes
I recall the last time that I tried, enabling it not persisting upon reboot. I’m aware that Wake-on-LAN - ArchWiki describes solely modifying a file to get it to work, but I didn’t need to last time. I’ll still try this time if testing it doesn’t work.
Yeah, that worked, @hui. I wonder what I did so wrong last time. Thanks, and apologies for asking a silly question. Does openSUSE have an alternative for Wake-on-LAN - ArchWiki? I don’t want to mess around with SystemD files.
What are you talking about? Wicked, NetworkManager, sytsemd-networkd all have native ways to enable (ot disable) WoL. And default is to not touch this setting, so as long as it is enabled in BIOS it should just work.
That’s never been the case for me, across 3 UEFI MBs and 5 OSes (Windows 10, Windows 11, Fedora 35, 36, and Rawhide, via Kinoite, the default Workstation and Server GNOME and the KDE Spin, and OSTW).
Instead, enabling it via the OS has always worked. I’d merely forgotten how I accomplished that last.