# Wake over LAN WOL dietpi x86 pc **URL:** \ **Category:** General Discussion\ **Created:** [10 June 2022 21:19 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397 "2022-06-10T21:19:29Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [10 June 2022 21:19 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/1 "2022-06-10T21:19:29Z")
I want wake over lan (WOL)for my Dietpi PC. in past that pc windows was installed & i was able to wake up that computer from android APP while it was sleeping. last week i have format that pc & install dietpi. my android phone app now not able to wake that pc. In mother board/Bios side i have not change anything so that pc is wol compatible as it was working in past. please guide me what change i have to made in pc so that it can wake up via WOL through android mobile app. what packages are missing which not allow dietpi X86 pc not to wake up from sleep mode. thanks ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [10 June 2022 21:44 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/2 "2022-06-10T21:44:27Z")
Hi, maybe you can have a look into this article [WakeOnLan - Debian Wiki](https://wiki.debian.org/WakeOnLan) I guess you need to add `ethernet-wol g` into `/etc/network/interfaces` as we use `ifupdown` ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [10 June 2022 22:12 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/3 "2022-06-10T22:12:27Z")
Thanks, my system start using WOL, the command i gave as ```auto sudo nano /etc/network/interfaces.d/eth0 ``` save these words in eth0 file ```auto auto eth0 iface eth0 inet dhcp ethernet-wol g ``` & reboot system & system boot with WOL commands, thanks @Joulinar ---
**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\ **Post date:** [11 June 2022 04:48 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/4 "2022-06-11T04:48:18Z")
Awesome, I didn’t know that one, and so easy. I’ll put it on the list for `dietpi-network` to be available as GUI option when I find time to finish it. Docs: [WakeOnLan - Debian Wiki](https://wiki.debian.org/WakeOnLan#Enabling_WOL) Requires `ethtool` package, but it’s pre-installed on DietPi for link speed and debugging already. ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [11 June 2022 06:04 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/5 "2022-06-11T06:04:58Z")
@MichaIng but there would need to be a check, to verify if the feature is supported by the system. ---
**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\ **Post date:** [11 June 2022 13:48 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/6 "2022-06-11T13:48:45Z")
Yes, the `ethtool` output contains this info. ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 15:31 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/7 "2022-09-12T15:31:08Z")
Is any thing change with this configuration. my working WOL system stop since last week. i have not changed anything. in past WOL working fine. i just gave “apt-get update” “apt-get upgrade” commands also installed & uninstall docker cli & docker-compose via dietpi-software. this setup working fine before but now with this computer is not wakeup via WOL. my system is working headless so no change in BIOS etc. ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [12 September 2022 18:06 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/8 "2022-09-12T18:06:39Z")
I guess the updated packages broke something. What did you update? ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 19:11 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/9 "2022-09-12T19:11:40Z")
only update system via standard commands “apt-get update” “apt-get upgrade” & i have install docker & docker compose & then uninstall it. is any linux command verify the WOL system or needed packages working /available or not? ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 19:16 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/10 "2022-09-12T19:16:59Z")
these commands gives following results ```auto root@DietPi:/etc/network# networkctl list WARNING: systemd-networkd is not running, output will be incomplete. IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback n/a unmanaged 2 eth0 ether n/a unmanaged 3 wlan0 wlan n/a unmanaged ``` ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 19:17 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/11 "2022-09-12T19:17:37Z")
```auto root@DietPi:/etc/network# ifquery eth0 ethernet-wol: g address: 192.168.1.90 netmask: 255.255.255.0 gateway: 192.168.1.254 broadcast: 192.168.1.255 ``` ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 19:20 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/12 "2022-09-12T19:20:33Z")
```auto root@DietPi:/etc/network# ethtool ethtool: bad command line argument(s) For more information run ethtool -h ``` ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [12 September 2022 19:25 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/13 "2022-09-12T19:25:51Z")
You could have a look to official docs [WakeOnLan - Debian Wiki](https://wiki.debian.org/WakeOnLan) Dietpi is using `ifupdown`. ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 19:28 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/14 "2022-09-12T19:28:37Z")
```auto root@DietPi:~# sudo ethtool eth0 Settings for eth0: Supported ports: [TP MII] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/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 Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Full 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: No 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 ``` [https://dpaste.org/LXpDX](https://dpaste.org/LXpDX) ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [12 September 2022 19:47 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/16 "2022-09-12T19:47:04Z")
> [@mail2rst](#): > > root@DietPi:/etc/network# ethtool ethtool: bad command line argument(s) For more information run ethtool -h Did you tried and ran `ethtool -h` to see more info? ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 19:53 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/17 "2022-09-12T19:53:45Z")
yes it is giving hundreds line ```auto root@DietPi:~# ethtool -h ethtool version 5.9 Usage: ethtool [--debug MASK][--json] DEVNAME Display standard information about device ethtool [--debug MASK][--json] -s|--change DEVNAME Change generic options [speed %d] [duplex half|full] [port tp|aui|bnc|mii|fibre|da] [mdix auto|on|off] [autoneg on|off] [advertise %x[/%x] | mode on|off ... [--] ] [phyad %d] ``` ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [12 September 2022 20:08 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/18 "2022-09-12T20:08:26Z")
Can you provide: `ethtool -i eth0 `? And what happens when you do: ```auto sudo ethtool -s eth0 wol g ``` ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 20:17 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/19 "2022-09-12T20:17:49Z")
```auto root@DietPi:~# ethtool -i eth0 driver: r8169 version: 5.10.0-18-amd64 firmware-version: rtl8411-1_0.0.3 06/18/12 expansion-rom-version: bus-info: 0000:02:00.2 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no ``` ---
**Author:** ![mail2rst](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/m/ee59a6/32.png) [@mail2rst](https://dietpi.com/forum/u/mail2rst)\ **Post date:** [12 September 2022 20:18 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/20 "2022-09-12T20:18:46Z")
```auto root@DietPi:~# sudo ethtool -s eth0 wol g root@DietPi:~# ``` ---
**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\ **Post date:** [12 September 2022 20:34 UTC](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397/21 "2022-09-12T20:34:17Z")
Ok no output at all, I would take this as “it worked”?! 😃 This command basically activated WOL mode g on eth0, like it was already before. I just wanted to get sure… You can reboot the machine and try if it works no, but I think not since we didn’t change anything. Hm this looks all fine, my only idea left is to check the LAN cable / physical connections. [Next page](https://dietpi.com/forum/t/wake-over-lan-wol-dietpi-x86-pc/13397.md?page=2)