Virtual network adapter stops "Wake these computers on resume" working

Problems or questions about Lights-Out on all Windows platforms are answered here
Antworten
beeswax
Foren-Einsteiger
Beiträge: 5
Registriert: 29. Aug 2022, 11:40

Virtual network adapter stops "Wake these computers on resume" working

Beitrag von beeswax » 29. Aug 2022, 12:08

In collecting all the data required for this second thread, I've actually figured out the root cause of my mobile app issue (thread yet to be approved), and this issue I was about to post. I was finding that as well as not being able to wake my server from the Android app, none of the machines configured in "Wake these computers on resume/start-up" were waking up.

I just gathered the logs to attach to the post and noticed that all the WoL commands were going to the Virtual Network Adapter for WSL/HyperV:

Code: Alles auswählen

2022-08-29 03:10:14:399 [   30] DEBUG WindowsPlatformInfo.EntryWritten: ******** 42/Microsoft-Windows-Kernel-Power=The system is entering sleep.,,Sleep Reason: Application API ********
2022-08-29 08:29:10:636 [    4] DEBUG 
2022-08-29 08:29:10:769 [    4] DEBUG > ------ Power event ResumeSuspend ------
2022-08-29 08:29:10:769 [    4] DEBUG < ------ Power event ResumeSuspend ------
2022-08-29 08:29:10:769 [    4] DEBUG 
2022-08-29 08:29:10:841 [   30] DEBUG WindowsPlatformInfo.EntryWritten: ******** 107/Microsoft-Windows-Kernel-Power=The system has resumed from sleep. ********
2022-08-29 08:29:11:086 [   17] DEBUG 
2022-08-29 08:29:11:086 [   17] DEBUG > ------ Power event ResumeAutomatic ------
2022-08-29 08:29:11:086 [   17] DEBUG NotifyClients Enabled=True
2022-08-29 08:29:11:086 [   17] DEBUG NotifyConsole Enabled=True
2022-08-29 08:29:11:086 [   17] DEBUG RunEvery15Minutes reset
2022-08-29 08:29:11:086 [   17] DEBUG > ResumeFromStandby, m_BlockSleep=False
2022-08-29 08:29:11:605 [   17] DEBUG > ResumeFromStandby, m_BlockSleep=False
2022-08-29 08:29:11:605 [   17] DEBUG ResetGlobalTimer: changed m_BlockSleep=True
2022-08-29 08:29:11:605 [   17] DEBUG WindowsPowerManagement.SetSleepBlock, IsSleepBlocked=False, reason='' -> 'Lights-Out-3, keeps the server awake...'
2022-08-29 08:29:11:605 [    7] DEBUG BlockStandby: Changed block=True, Reason=Lights-Out-3, keeps the server awake...
2022-08-29 08:29:11:605 [   17] DEBUG Running in thread: powercfg.exe -requests with secondsDelay 1, set working dir=False
2022-08-29 08:29:11:605 [   17] DEBUG last event recorded: Resume 
2022-08-29 08:29:11:605 [   17] DEBUG LastEventListWriter.Write: 4 items written
2022-08-29 08:29:11:605 [   17] DEBUG last event written
2022-08-29 08:29:11:605 [   17] DEBUG WindowsServiceController.StartMode: Service MySQL_Kodi, has start mode Automatic
2022-08-29 08:29:11:605 [   17] DEBUG   HandleServices: MySQL_Kodi, currently running=False, expected=True
2022-08-29 08:29:11:615 [   17] DEBUG     starting MySQL_Kodi
2022-08-29 08:29:11:683 [   20] DEBUG .
2022-08-29 08:29:12:059 [   30] DEBUG MulticastServer.NetworkAddressHasChanged
2022-08-29 08:29:12:078 [   30] DEBUG    NIC Ethernet 3 - Intel(R) Ethernet Connection (2) I219-V Status=Down, MulticastSupport=True, Type=Ethernet
2022-08-29 08:29:12:078 [   30] DEBUG    NIC Loopback Pseudo-Interface 1 - Software Loopback Interface 1 Status=Up, MulticastSupport=True, Type=Loopback
2022-08-29 08:29:12:078 [   30] DEBUG    NIC vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter Status=Up, MulticastSupport=True, Type=Ethernet
2022-08-29 08:29:12:078 [   30] DEBUG     added 172.31.96.1 on vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter
2022-08-29 08:29:12:078 [   30] DEBUG MulticastServer.AddInterface 172.31.96.1
2022-08-29 08:29:12:078 [   30] INFO  MulticastServer is now listening on 172.31.96.1
2022-08-29 08:29:12:269 [   17] DEBUG Running in thread with cmd.exe:  with secondsDelay 15
2022-08-29 08:29:12:282 [   17] DEBUG > WakeOnResume
2022-08-29 08:29:12:294 [   17] DEBUG WakeUp: Broadcast magic packet for mac=00-FD-45-FC-D7-C4 on 172.31.96.1:0 to port 7
2022-08-29 08:29:12:308 [   17] DEBUG WakeUp: Broadcast magic packet for mac=00-FD-45-FC-D7-C5 on 172.31.96.1:0 to port 7
2022-08-29 08:29:12:308 [   17] DEBUG ServiceCore.DeviceListChanged: index 1 = W1806881037-00FD45FCD7C4/MicroServer2, property LastWakeup=29/08/2022 08:29:12
2022-08-29 08:29:12:321 [   17] DEBUG WakeUp: Broadcast magic packet for mac=34-64-A9-9A-DF-EC on 172.31.96.1:0 to port 7
2022-08-29 08:29:12:321 [   17] DEBUG WakeUp: Broadcast magic packet for mac=34-64-A9-9A-DF-ED on 172.31.96.1:0 to port 7
2022-08-29 08:29:12:334 [   17] DEBUG ServiceCore.DeviceListChanged: index 2 = W2084801732-3464A99ADFEC/MICROSERVER1, property LastWakeup=29/08/2022 08:29:12
2022-08-29 08:29:12:334 [   17] DEBUG WakeUp: Broadcast magic packet for mac=1C-98-EC-0E-A2-8C on 172.31.96.1:0 to port 7
2022-08-29 08:29:12:359 [   17] DEBUG WakeUp: Broadcast magic packet for mac=1C-98-EC-0E-A2-8D on 172.31.96.1:0 to port 7
2022-08-29 08:29:12:359 [   17] DEBUG ServiceCore.DeviceListChanged: index 3 = W922002318-1C98EC0EA28C/MicroServer3, property LastWakeup=29/08/2022 08:29:12
2022-08-29 08:29:12:372 [   17] DEBUG WakeUp: Broadcast magic packet for mac=3C-A8-2A-A0-13-38 on 172.31.96.1:0 to port 7
2022-08-29 08:29:12:372 [   17] DEBUG ServiceCore.DeviceListChanged: index 4 = W1681517205-3CA82AA01338/MICROSERVER4, property LastWakeup=29/08/2022 08:29:12
2022-08-29 08:29:12:372 [   17] DEBUG < WakeOnResume True
2022-08-29 08:29:12:372 [   17] DEBUG ServerRuntime: resumed
I checked the settings on the server and could not find a way to specify an adapter to use on the server so for now, I have disabled the virtual network adapter and everything works now. Is there a way I can re-enable that adapter and still have everything work?

Benutzeravatar
Martin
Moderator
Beiträge: 9817
Registriert: 11. Sep 2007, 10:51
Wohnort: Im wilden Süden

Re: Virtual network adapter stops "Wake these computers on resume" working

Beitrag von Martin » 30. Aug 2022, 22:00

Thanks for update,

Lights-Out should use all available adapters, the physical as well as any virtual if IPv4 is enabled and supported.
Can you please enable the virtual adapter and post output of ipconfig/all?

Regards
Martin
Eigenbau mit WSE 2012 R2, HP N40L mit WSE 2012 R2 als Backupserver, HP Microserver Gen8 unter WSE 2016
Entwickler von Lights-Out

beeswax
Foren-Einsteiger
Beiträge: 5
Registriert: 29. Aug 2022, 11:40

Re: Virtual network adapter stops "Wake these computers on resume" working

Beitrag von beeswax » 31. Aug 2022, 09:52

Hi Martin,

Thanks for your reply, turns out the Virtual Adapter has already re-enabled itself, I think it might be used by Docker for something so my Micrservers are failing to wake again. Here's ipconfig output:

Code: Alles auswählen

Windows IP Configuration

   Host Name . . . . . . . . . . . . : StorageServer
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 3:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V
   Physical Address. . . . . . . . . : E0-D5-5E-6B-2C-93
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::44a1:52ce:5bc3:e630%5(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 30 August 2022 10:27:47
   Lease Expires . . . . . . . . . . : 01 September 2022 00:21:17
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 383833438
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-98-25-DF-90-2B-34-3C-85-7D
   DNS Servers . . . . . . . . . . . : 8.8.4.4
                                       8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter vEthernet (WSL):

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
   Physical Address. . . . . . . . . : 00-15-5D-0A-90-62
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d9f4:2ee5:5f85:2cbe%21(Preferred) 
   IPv4 Address. . . . . . . . . . . : 172.19.64.1(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 352327005
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-98-25-DF-90-2B-34-3C-85-7D
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
And another server wake up log:

Code: Alles auswählen

2022-08-31 00:21:12:924 [   30] DEBUG WindowsPlatformInfo.EntryWritten: ******** 107/Microsoft-Windows-Kernel-Power=The system has resumed from sleep. ********
2022-08-31 00:21:12:944 [   22] DEBUG 
2022-08-31 00:21:12:944 [   22] DEBUG > ------ Power event ResumeSuspend ------
2022-08-31 00:21:12:944 [   22] DEBUG < ------ Power event ResumeSuspend ------
2022-08-31 00:21:12:944 [   22] DEBUG 
2022-08-31 00:21:12:994 [   25] DEBUG 
2022-08-31 00:21:12:994 [   25] DEBUG > ------ Power event ResumeAutomatic ------
2022-08-31 00:21:12:997 [   25] DEBUG NotifyClients Enabled=True
2022-08-31 00:21:12:997 [   25] DEBUG NotifyConsole Enabled=True
2022-08-31 00:21:12:997 [   25] DEBUG RunEvery15Minutes reset
2022-08-31 00:21:12:997 [   25] DEBUG > ResumeFromStandby, m_BlockSleep=False
2022-08-31 00:21:13:356 [   30] ERROR IOCompletionCallback
System.ComponentModel.Win32Exception (0x80004005): The specified network name is no longer available
2022-08-31 00:21:13:356 [   29] ERROR IOCompletionCallback
System.ComponentModel.Win32Exception (0x80004005): The specified network name is no longer available
2022-08-31 00:21:13:511 [   25] DEBUG > ResumeFromStandby, m_BlockSleep=False
2022-08-31 00:21:13:511 [   25] DEBUG ResetGlobalTimer: changed m_BlockSleep=True
2022-08-31 00:21:13:511 [   25] DEBUG WindowsPowerManagement.SetSleepBlock, IsSleepBlocked=False, reason='' -> 'Lights-Out-3, keeps the server awake...'
2022-08-31 00:21:13:511 [    7] DEBUG BlockStandby: Changed block=True, Reason=Lights-Out-3, keeps the server awake...
2022-08-31 00:21:13:511 [   25] DEBUG Running in thread: powercfg.exe -requests with secondsDelay 1, set working dir=False
2022-08-31 00:21:13:513 [   25] DEBUG last event recorded: Resume 
2022-08-31 00:21:13:513 [   25] DEBUG LastEventListWriter.Write: 30 items written
2022-08-31 00:21:13:513 [   25] DEBUG last event written
2022-08-31 00:21:13:513 [   25] DEBUG WindowsServiceController.StartMode: Service MySQL_Kodi, has start mode Automatic
2022-08-31 00:21:13:513 [   25] DEBUG   HandleServices: MySQL_Kodi, currently running=False, expected=True
2022-08-31 00:21:13:513 [   25] DEBUG     starting MySQL_Kodi
2022-08-31 00:21:14:066 [   32] DEBUG   < SuspendSystem hibernate=False, result=1, LastError=0
2022-08-31 00:21:14:066 [   32] DEBUG < WindowsController.ExitWindows: how=Suspend, force=True, result=True
2022-08-31 00:21:14:087 [   32] DEBUG RunAction: <<<<<<<< Suspend returned result=True
2022-08-31 00:21:14:087 [   32] DEBUG ValidateTimeSpan: Time span in Suspend was 0:24:52.2311081, result=True
2022-08-31 00:21:14:087 [   32] DEBUG < RunAction: action=Suspend, force=True
2022-08-31 00:21:14:087 [   32] DEBUG < Forced action Suspend success
2022-08-31 00:21:14:118 [   32] DEBUG MulticastServer.NetworkAddressHasChanged
2022-08-31 00:21:14:133 [   32] DEBUG    NIC Ethernet 3 - Intel(R) Ethernet Connection (2) I219-V Status=Down, MulticastSupport=True, Type=Ethernet
2022-08-31 00:21:14:133 [   32] DEBUG    NIC Loopback Pseudo-Interface 1 - Software Loopback Interface 1 Status=Up, MulticastSupport=True, Type=Loopback
2022-08-31 00:21:14:133 [   32] DEBUG    NIC vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter Status=Up, MulticastSupport=True, Type=Ethernet
2022-08-31 00:21:14:133 [   32] DEBUG     added 172.19.64.1 on vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter
2022-08-31 00:21:14:133 [   32] DEBUG MulticastServer.AddInterface 172.19.64.1
2022-08-31 00:21:14:133 [   32] INFO  MulticastServer is now listening on 172.19.64.1
2022-08-31 00:21:14:442 [   25] DEBUG Running in thread with cmd.exe:  with secondsDelay 15
2022-08-31 00:21:14:455 [   25] DEBUG > WakeOnResume
2022-08-31 00:21:14:467 [   25] DEBUG WakeUp: Broadcast magic packet for mac=3C-A8-2A-A0-13-38 on 172.19.64.1:0 to port 7
2022-08-31 00:21:14:467 [   25] DEBUG ServiceCore.DeviceListChanged: index 2 = W1681517205-3CA82AA01338/MICROSERVER4, property LastWakeup=31/08/2022 00:21:14
2022-08-31 00:21:14:467 [   25] DEBUG WakeUp: Broadcast magic packet for mac=00-FD-45-FC-D7-C4 on 172.19.64.1:0 to port 7
2022-08-31 00:21:14:467 [   25] DEBUG ServiceCore.DeviceListChanged: index 3 = W1806881037-00FD45FCD7C4/MicroServer2, property LastWakeup=31/08/2022 00:21:14
2022-08-31 00:21:14:493 [   25] DEBUG WakeUp: Broadcast magic packet for mac=34-64-A9-9A-DF-EC on 172.19.64.1:0 to port 7
2022-08-31 00:21:14:493 [   25] DEBUG ServiceCore.DeviceListChanged: index 4 = W2084801732-3464A99ADFEC/MICROSERVER1, property LastWakeup=31/08/2022 00:21:14
2022-08-31 00:21:14:505 [   25] DEBUG WakeUp: Broadcast magic packet for mac=1C-98-EC-0E-A2-8C on 172.19.64.1:0 to port 7
2022-08-31 00:21:14:505 [   25] DEBUG ServiceCore.DeviceListChanged: index 5 = W922002318-1C98EC0EA28C/MicroServer3, property LastWakeup=31/08/2022 00:21:14
2022-08-31 00:21:14:505 [   25] DEBUG < WakeOnResume True
2022-08-31 00:21:14:505 [   25] DEBUG ServerRuntime: resumed
It lists the Intel network adapter but then only sends WoL packets from the Virtual WSL one. I wonder if it's jumping into the wakeup routine too quickly afte resuming from sleep? Maybe the Intel adapter doesn't have an IP yet?

By the way, I was looking at the Command Line options as I thought I could work around this by simply running my own "Wait and then WoL" script after server resumes but I can't work out how to wake up a specific machine. The documentation mentions the "--wake_server" switch but not how to wake a specific client/MAC address.

Benutzeravatar
Martin
Moderator
Beiträge: 9817
Registriert: 11. Sep 2007, 10:51
Wohnort: Im wilden Süden

Re: Virtual network adapter stops "Wake these computers on resume" working

Beitrag von Martin » 31. Aug 2022, 21:38

It looks like the physical NIC is not yet operational, the status is Down:
2022-08-31 00:21:14:133 [ 32] DEBUG NIC Ethernet 3 - Intel(R) Ethernet Connection (2) I219-V Status=Down, MulticastSupport=True, Type=Ethernet
2022-08-31 00:21:14:133 [ 32] DEBUG NIC Loopback Pseudo-Interface 1 - Software Loopback Interface 1 Status=Up, MulticastSupport=True, Type=Loopback
2022-08-31 00:21:14:133 [ 32] DEBUG NIC vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter Status=Up, MulticastSupport=True, Type=Ethernet

So you may be right with your assumption. To verify that, please right click on the Lights-Out client (the bulb) and repeat a wake-up of your server. Does it now use the physical NIC?
Eigenbau mit WSE 2012 R2, HP N40L mit WSE 2012 R2 als Backupserver, HP Microserver Gen8 unter WSE 2016
Entwickler von Lights-Out

beeswax
Foren-Einsteiger
Beiträge: 5
Registriert: 29. Aug 2022, 11:40

Re: Virtual network adapter stops "Wake these computers on resume" working

Beitrag von beeswax » 1. Sep 2022, 10:19

Good morning Martin, yes it seems this is the problem. With the LO Server machine (running Win10) having been awake for an hour or so and clicking "Wake all computers" from the console, it uses the physical NIC and all machines wake successfully:

Code: Alles auswählen

2022-09-01 09:02:06:747 [   19] DEBUG GET from fe80::d9f4:2ee5:5f85:2cbe%21/STORAGESERVER\Ian for https://storageserver:7783/AxoNet.LightsOut.WebService/ServerInformation/monitoring, IsAuthenticated=True
2022-09-01 09:02:14:031 [   25] DEBUG PowerRequestsMonitor.DetectAwayModeTimerElapsed: m_LastRequest=None
2022-09-01 09:02:14:738 [   31] DEBUG .
2022-09-01 09:02:22:403 [    4] DEBUG PUT from fe80::d9f4:2ee5:5f85:2cbe%21/STORAGESERVER\Ian for https://storageserver:7783/AxoNet.LightsOut.WebService/ClientControl/wakeup/W1681517205-3CA82AA01338
2022-09-01 09:02:22:403 [    4] DEBUG Wake MICROSERVER4
2022-09-01 09:02:22:419 [    4] DEBUG WakeUp: Broadcast magic packet for mac=3C-A8-2A-A0-13-38 on 192.168.0.3:0 to port 7
2022-09-01 09:02:22:419 [    4] DEBUG WakeUp: Broadcast magic packet for mac=3C-A8-2A-A0-13-38 on 172.19.64.1:0 to port 7
2022-09-01 09:02:22:419 [    4] DEBUG PUT from fe80::44a1:52ce:5bc3:e630%5/STORAGESERVER\Ian for https://storageserver:7783/AxoNet.LightsOut.WebService/ClientControl/wakeup/W1806881037-00FD45FCD7C4
2022-09-01 09:02:22:419 [    4] DEBUG Wake MicroServer2
2022-09-01 09:02:22:431 [   33] DEBUG PUT from fe80::d9f4:2ee5:5f85:2cbe%21/STORAGESERVER\Ian for https://storageserver:7783/AxoNet.LightsOut.WebService/ClientControl/wakeup/W2084801732-3464A99ADFEC
2022-09-01 09:02:22:431 [   33] DEBUG Wake MICROSERVER1
2022-09-01 09:02:22:446 [    4] DEBUG WakeUp: Broadcast magic packet for mac=00-FD-45-FC-D7-C4 on 192.168.0.3:0 to port 7
2022-09-01 09:02:22:446 [    4] DEBUG WakeUp: Broadcast magic packet for mac=00-FD-45-FC-D7-C4 on 172.19.64.1:0 to port 7
2022-09-01 09:02:22:446 [    4] DEBUG PUT from fe80::44a1:52ce:5bc3:e630%5/STORAGESERVER\Ian for https://storageserver:7783/AxoNet.LightsOut.WebService/ClientControl/wakeup/W922002318-1C98EC0EA28C
2022-09-01 09:02:22:446 [    4] DEBUG Wake MicroServer3
2022-09-01 09:02:22:446 [   33] DEBUG WakeUp: Broadcast magic packet for mac=34-64-A9-9A-DF-EC on 192.168.0.3:0 to port 7
2022-09-01 09:02:22:446 [   33] DEBUG WakeUp: Broadcast magic packet for mac=34-64-A9-9A-DF-EC on 172.19.64.1:0 to port 7
2022-09-01 09:02:22:471 [    4] DEBUG WakeUp: Broadcast magic packet for mac=1C-98-EC-0E-A2-8C on 192.168.0.3:0 to port 7
2022-09-01 09:02:22:471 [    4] DEBUG WakeUp: Broadcast magic packet for mac=1C-98-EC-0E-A2-8C on 172.19.64.1:0 to port 7
The original attempt earlier this morning failed to wake them but was only utilising the Virtual adapter:

Code: Alles auswählen

2022-09-01 06:59:53:793 [   27] DEBUG last event recorded: Resume 
2022-09-01 06:59:53:793 [   27] DEBUG LastEventListWriter.Write: 31 items, trimming to 30
2022-09-01 06:59:53:793 [    7] DEBUG BlockStandby: Changed block=True, Reason=Lights-Out-3, keeps the server awake...
2022-09-01 06:59:53:793 [   27] DEBUG LastEventListWriter.Write: 30 items written
2022-09-01 06:59:53:793 [   27] DEBUG last event written
2022-09-01 06:59:53:793 [   27] DEBUG WindowsServiceController.StartMode: Service MySQL_Kodi, has start mode Automatic
2022-09-01 06:59:53:793 [   27] DEBUG   HandleServices: MySQL_Kodi, currently running=False, expected=True
2022-09-01 06:59:53:793 [   27] DEBUG     starting MySQL_Kodi
2022-09-01 06:59:53:870 [   40] DEBUG MulticastServer.NetworkAddressHasChanged
2022-09-01 06:59:53:892 [   40] DEBUG    NIC Ethernet 3 - Intel(R) Ethernet Connection (2) I219-V Status=Down, MulticastSupport=True, Type=Ethernet
2022-09-01 06:59:53:892 [   40] DEBUG    NIC Loopback Pseudo-Interface 1 - Software Loopback Interface 1 Status=Up, MulticastSupport=True, Type=Loopback
2022-09-01 06:59:53:892 [   40] DEBUG    NIC vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter Status=Up, MulticastSupport=True, Type=Ethernet
2022-09-01 06:59:53:892 [   40] DEBUG     added 172.19.64.1 on vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter
2022-09-01 06:59:53:892 [   40] DEBUG MulticastServer.AddInterface 172.19.64.1
2022-09-01 06:59:53:892 [   40] INFO  MulticastServer is now listening on 172.19.64.1
2022-09-01 06:59:54:481 [   27] DEBUG Running in thread with cmd.exe:  with secondsDelay 15
2022-09-01 06:59:54:493 [   27] DEBUG > WakeOnResume
2022-09-01 06:59:54:493 [   27] DEBUG WakeUp: Broadcast magic packet for mac=3C-A8-2A-A0-13-38 on 172.19.64.1:0 to port 7
2022-09-01 06:59:54:493 [   27] DEBUG ServiceCore.DeviceListChanged: index 2 = W1681517205-3CA82AA01338/MICROSERVER4, property LastWakeup=01/09/2022 06:59:54
2022-09-01 06:59:54:520 [   27] DEBUG WakeUp: Broadcast magic packet for mac=00-FD-45-FC-D7-C4 on 172.19.64.1:0 to port 7
2022-09-01 06:59:54:520 [   27] DEBUG ServiceCore.DeviceListChanged: index 3 = W1806881037-00FD45FCD7C4/MicroServer2, property LastWakeup=01/09/2022 06:59:54
2022-09-01 06:59:54:533 [   27] DEBUG WakeUp: Broadcast magic packet for mac=34-64-A9-9A-DF-EC on 172.19.64.1:0 to port 7
2022-09-01 06:59:54:533 [   27] DEBUG ServiceCore.DeviceListChanged: index 4 = W2084801732-3464A99ADFEC/MICROSERVER1, property LastWakeup=01/09/2022 06:59:54
2022-09-01 06:59:54:546 [   27] DEBUG WakeUp: Broadcast magic packet for mac=1C-98-EC-0E-A2-8C on 172.19.64.1:0 to port 7
2022-09-01 06:59:54:546 [   27] DEBUG ServiceCore.DeviceListChanged: index 5 = W922002318-1C98EC0EA28C/MicroServer3, property LastWakeup=01/09/2022 06:59:54
2022-09-01 06:59:54:546 [   27] DEBUG < WakeOnResume True
2022-09-01 06:59:54:546 [   27] DEBUG ServerRuntime: resumed
Looking at Event Viewer, the phycial NIC took a only a few seconds longer to reconnect:

Code: Alles auswählen

Source:        e1dexpress
Date:          01/09/2022 06:59:56
Event ID:      32
Computer:      StorageServer
Description:
Intel(R) Ethernet Connection (2) I219-V
 Network link has been established at 1Gbps full duplex.
Confirmed in the LO logs a second later:

Code: Alles auswählen

2022-09-01 06:59:57:872 [   12] DEBUG MulticastServer.NetworkAddressHasChanged
2022-09-01 06:59:57:888 [   12] DEBUG    NIC Ethernet 3 - Intel(R) Ethernet Connection (2) I219-V Status=Up, MulticastSupport=True, Type=Ethernet
2022-09-01 06:59:57:888 [   12] DEBUG     added 192.168.0.3 on Ethernet 3 - Intel(R) Ethernet Connection (2) I219-V
2022-09-01 06:59:57:888 [   12] DEBUG    NIC Loopback Pseudo-Interface 1 - Software Loopback Interface 1 Status=Up, MulticastSupport=True, Type=Loopback
2022-09-01 06:59:57:888 [   12] DEBUG    NIC vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter Status=Up, MulticastSupport=True, Type=Ethernet
2022-09-01 06:59:57:888 [   12] DEBUG     added 172.19.64.1 on vEthernet (WSL) - Hyper-V Virtual Ethernet Adapter
I wonder if an option can be added in the LO Console for a "Preferred Network Adapter" to make LO wait for a specific adapter to be connected before issuing wake commands? If the Virtual Adapter didn't exist, would it do this anyway? If so, maybe an easier solution is to add an option for some network adapters to be ignored, such as Virtuals.

Thanks for you help with this!

Benutzeravatar
Martin
Moderator
Beiträge: 9817
Registriert: 11. Sep 2007, 10:51
Wohnort: Im wilden Süden

Re: Virtual network adapter stops "Wake these computers on resume" working

Beitrag von Martin » 1. Sep 2022, 11:35

Thanks for confirmation of the issue. I will check next week if I can address the problem.

Regards
Martin
Eigenbau mit WSE 2012 R2, HP N40L mit WSE 2012 R2 als Backupserver, HP Microserver Gen8 unter WSE 2016
Entwickler von Lights-Out

beeswax
Foren-Einsteiger
Beiträge: 5
Registriert: 29. Aug 2022, 11:40

Re: Virtual network adapter stops "Wake these computers on resume" working

Beitrag von beeswax » 1. Sep 2022, 13:24

Thank you Martin :)

Just a thought - a very quick and simple solution would be a user-configurable delay before issuing wake commands via the "Wake these computers on resume/start-up" option.

Benutzeravatar
Martin
Moderator
Beiträge: 9817
Registriert: 11. Sep 2007, 10:51
Wohnort: Im wilden Süden

Re: Virtual network adapter stops "Wake these computers on resume" working

Beitrag von Martin » 8. Sep 2022, 17:03

Hi,

can you please send a complete client log to support@green-it-software.com and add a reference to this discussion here?

Thanks
Martin
Eigenbau mit WSE 2012 R2, HP N40L mit WSE 2012 R2 als Backupserver, HP Microserver Gen8 unter WSE 2016
Entwickler von Lights-Out

Antworten