![]() e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode e1000e: Intel(R) PRO/1000 Network Driver Subsystem: Lenovo Ethernet Connection (2) I219-LM Supported link modes: 10baseT/Half 10baseT/FullĪdvertised link modes: 10baseT/Half 10baseT/FullĠ0:1f.6 Ethernet controller : Intel Corporation Ethernet Connection (2) I219-LM (rev 31) Oct 18 23:10:52 pve systemd: wol.service: Succeeded. Oct 18 23:10:52 pve systemd: Started Wake-on-LAN for eno1. ![]() Main PID: 950 (code=exited, status=0/SUCCESS) Process: 955 ExecStop=/sbin/ethtool -s eno1 wol g (code=exited, status=0/SUCCESS) Process: 950 ExecStart=/sbin/ethtool -s eno1 wol g (code=exited, status=0/SUCCESS) Loaded: loaded (/etc/systemd/system/wol.service enabled vendor preset: enabled)Īctive: inactive (dead) since Mon 23:10:52 CEST 1min 57s ago Sudo chmod 755 /etc/rc0.d/wol_poweroff.sh & sudo chmod 755 /etc/rc6.d/wol_poweroff.sh Created script to bring the ethernet interface down properly at shutdown :Ĭp /etc/rc6.d/wol_poweroff.sh /etc/ rc0.d/wol_poweroff.shįinally changed permissions to make it executable: I tried sending packets to the combination of host's MAC and IP (as well as broadcast to 255.255.255.255), ports 7,9,4343,4000,etc.When the machine is powered off, and I send magic packets using apps like "wol" (from a windows host), an android app (landroid), I understand that they are reaching the NIC as I can see the ethernet port flashing, but the machine doesn't boot.When the machine is powered on, I successfully tested receiving magic packets using netcat.I also created a systemd service " wol.service", to also set the eno1 interface's wol to "g", using ethtool (see #3 below).Created script to bring the ethernet interface eno1 down properly at shutdown, based on this bug (see #2 below).Updated cat /etc/network/interfaces so that at every boot, it sets the vmbr0 interface's wol to "g", using ethtool (see #1 below). ![]() The NIC supports WoL and is (/was already correctly) enabled and set to "g".The BIOS (is up-to-date) supports WoL and is enabled.At this point I am not sure if it is a configuration issue or a BUG? I can't get Wake on Lan (WOL) to work with Proxmox, no matter what. I then installed Proxmox 7 (5.11.22-4-pve) on the same hardware. I was able to wake up the system from a "Hibernate" or "Sleep" mode by sending a magic packet from another windows host. disable "reduce speed on power down") and the UEFI BIOS to make it work. I had to make some changes in the adapter settings (eg. And that is it, now just run your WoL Tool and the System should wake up and boot to Windows.I confirmed that Wake On Lan works with Windows 10 Pr o on a Lenovo ThinkStation P310 with onboard Intel I219-LM GB Ethernet controller.Configure the physical address of the computer you want to wake up (here you need the address you noted before).On another System in your Network, download and open your Wake on LAN Tool.Shut down your computer again, or send it into standby.Note the physical address of your LAN-Adapter.įigure 1: Physical Address of the Network Adapter. ![]() Open start type in CMD, right-click command prompt and choose Run as Administrator. Once in Windows, open the command prompt with administrator rights. Start the System that you want to wake up.To configure your Wake on LAN Tool follow these steps (steps may vary on other tools): You can find plenty of them in a Websearch like Bing or Google. Please choose the Wake on LAN tool that suits your needs and download it. NOTE: Dell does not endorse this Software and using it is at your own risk.
0 Comments
Leave a Reply. |