Wake-on-LAN non-functional

Issue

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 wlp69s0
Settings for wlp69s0:
        Link detected: yes
sudo ethtool wlp74s0
Settings for wlp74s0:
        Link detected: yes
sudo iw dev
phy#1
        Unnamed/non-netdev interface
                wdev 0x100000002
                addr 8c:b8:7e:a0:65:86
                type P2P-device
        Interface wlp69s0
                ifindex 4
                wdev 0x100000001
                addr 8c:b8:7e:a0:65:86
                ssid TNCAPD0390D
                type managed
                channel 108 (5540 MHz), width: 80 MHz, center1: 5530 MHz
                txpower 22.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                        0       0       0       0       0       0       0       0               0
phy#0
        Interface wlp74s0
                ifindex 3
                wdev 0x1
                addr 00:91:9e:53:5f:57
                ssid TNCAPD0390D
                type managed
                channel 108 (5540 MHz), width: 80 MHz, center1: 5530 MHz
                txpower 22.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                        0       0       0       0       0       0       0       0               0

WOL is disabled on your adapter.

Wake-on: d

Enable WOL in BIOS and use one of the described methodes:
https://wiki.archlinux.org/title/Wake-on-LAN

2 Likes

Thanks, @hui. I followed Wake-on-LAN - ArchWiki

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.

I’ll do a systemctl poweroff and try to boot it using the MAC address via https://github.com/Florianisme/WakeOnLan/releases/download/1.9.0/app-release.apk.

I did not read all details above, but this is a link to my experiences:

1 Like

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.

Wake-on-LAN - ArchWiki worked!

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.

@arvidjaar,

I’m referring to the instructions in Wake-on-LAN - ArchWiki, as aforecited in the comment you responded to.

I’m aware — did you not see Wake-on-LAN non-functional - #6 by rokejulianlockhart?

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.

If of interest, I’ve designed a basic programmatic version at `{title: "Entities", id: "s1gvg2"}`{.JSON5}.dir/ `{name: {short: "Beedell.RokeJulianLockhart", long: {third: "Beedell", first: "Roke"}}, id: "s1gvgt"}`{.JSON5}.dir/ `{title: "Technical", id: "s20cxw"}`{.JSON5}.dir/ `{title: "Projects", id: ""}`{.JSON5}.dir/ `{title: "Configurator", id: "s3wrcl"}`{.JSON5}.dir/ `{title: "Code", id: ""}`{.JSON5}.dir/ ``{title: "`Set-Configuration`{.PS1}", id: ""}``{.JSON5}.txt.PS1 · 6dc3917bfe7eb3fd679972b2f2bad871ee1652f7 · `{third: "Beedell", first: "Roke"}`{.JSON5} / Public · GitLab

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.