Hello,
here's the situation: a newly installed WAPT server on a VLAN (server), with the console on a workstation on the same VLAN. The client workstations are on a different VLAN.
On the network side, there's an Aruba 6300 core and Aruba 2930f Layer 2 stacks.
The network configuration is correct for inter-VLAN Wake-on-LAN (WOL). However, on the same workstation where I have the WAPT console, there's a simple WOL utility. If I perform a Wake-on-LAN command to a workstation, everything works fine, but nothing happens when I perform the same WOL command from the WAPT console. Could there be a bug with WOL in WAPT 1.8.2 on Debian 10? Is it possible to send a WOL command from the command line on the WAPT server?
wapt 1.8.2 workstation startup problem via wol
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Hello, I'm adding my own research on the same problem, since a request already exists.
- WAPT version installed: 1.8.2
- Server OS: Debian 4.9.12
- Administration/package creation machine OS: Windows 10
Since we upgraded to version 1.8.2, wake-up via Wake-on-LAN no longer works (but it works with other tools).
After digging around on the server, I found this script: /opt/wapt/lib/python2.7/site-packages/wakeonlan/wol.py which seems to be used for this function.
Inside, we can see this configuration:
BROADCAST_IP = '255.255.255.255'
Such a subnet mask doesn't work through routers, and we have several routed subnets.
When checking with Wireshark, the WOL packet is indeed being sent from the server, but it's not passing through the routers and therefore not reaching the workstations.
Changing the subnet mask to 10.255.255.255, which corresponds to our subnets, seems to stop the packet being sent, according to the packets observed in Wireshark.
Do you have a solution to get WOL working again?
Perhaps an improvement to the WOL function to take into account the IP addresses of the workstations and dynamically set this broadcast_ip?
Thank you.
- WAPT version installed: 1.8.2
- Server OS: Debian 4.9.12
- Administration/package creation machine OS: Windows 10
Since we upgraded to version 1.8.2, wake-up via Wake-on-LAN no longer works (but it works with other tools).
After digging around on the server, I found this script: /opt/wapt/lib/python2.7/site-packages/wakeonlan/wol.py which seems to be used for this function.
Inside, we can see this configuration:
BROADCAST_IP = '255.255.255.255'
Such a subnet mask doesn't work through routers, and we have several routed subnets.
When checking with Wireshark, the WOL packet is indeed being sent from the server, but it's not passing through the routers and therefore not reaching the workstations.
Changing the subnet mask to 10.255.255.255, which corresponds to our subnets, seems to stop the packet being sent, according to the packets observed in Wireshark.
Do you have a solution to get WOL working again?
Perhaps an improvement to the WOL function to take into account the IP addresses of the workstations and dynamically set this broadcast_ip?
Thank you.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
https://github.com/tranquilit/WAPT/blob ... r.py#L1510
After reviewing the code, following a change, it no longer works. I'll look into a patch.
After reviewing the code, following a change, it no longer works. I'll look into a patch.
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello stephaneB and fifoulefou,
Sincerely,
Denis
There is indeed a bug. I've opened an internal ticket. If you're on the enterprise version, contact support to have it prioritized if it's urgent for you. Otherwise, you can submit a pull request on the community GitHub repository.stephaneB wrote: ↑Oct 13, 2020 - 10:56 AM Hello, I'm adding my own research for the same problem, since a request already exists.
- Installed WAPT version: 1.8.2
- Server OS: Debian 4.9.12
- Administration/package creation machine OS: Windows 10
Since we upgraded to version 1.8.2, waking up workstations via Wake-on-LAN no longer works (but it works with other tools).
After digging around a bit on the server, I found this script: /opt/wapt/lib/python2.7/site-packages/wakeonlan/wol.py which seems to be used for this function.
...
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
