HP Switches - VLAN - WOL - How?

[Chuckster]

How do I get WOL working across other VLANs?

 

Below is a snippet of the config file from my core switch. As you can see I have enabled the relevant bits such as ip directed-broadcast and ip udp-bcast-forward at the root. I've also tried putting ip forward-protocol in VLAN 10 to forward the WOL packets to VLAN 20 where my workstations sit, but to no avail.

 

 

• WOL is on the server IP address 172.20.10.14. THis is also our MDT/WDS server.
  
• 172.20.5.1 is our gateway router.
  
• DHCP servers are 172.20.10.2 and .3
  

 

ip default-gateway 172.20.5.1

ip directed-broadcast

ip route 0.0.0.0 0.0.0.0 172.20.5.1

ip routing

ip udp-bcast-forward

vlan 10

name "Servers"

untagged D1-D20

tagged Trk1-Trk2

ip address 172.20.10.1 255.255.255.0

ip forward-protocol udp 172.20.20.255 9

ip forward-protocol udp 172.20.21.255 9

ip forward-protocol udp 172.20.20.0 9

exit

vlan 20

name "Wired.Clients"

untagged A1-A24,B1-B24,C1-C20

tagged Trk1-Trk2

ip address 172.20.20.1 255.255.254.0

ip helper-address 172.20.10.2

ip helper-address 172.20.10.3

ip helper-address 172.20.10.14

exit

Edited July 13, 2018 by Chuckster

[mrbios]

Assuming the application you're using is send WOL on port 9 rather than port 7 and you're sending the WOL from a device on vlan10 that looks about right i think. Test an end to end WOL client, I can't remember the name of it, but there's one that will pop up a notification with the received WOL packet on the remote client when you run it.

 

However more concerning is that your IP range is outside of the private block. The private block for 172 addresses starts at 172.16. unless I'm mistaken?

[Chuckster]

Sorry, the formatting has messed up the config.

 

WOL is using port 9.

[localzuk]

The private block for 172 addresses starts at 172.16. unless I'm mistaken?

The private block is 172.16.0.0 - 172.31.255.255.

[Chuckster]

I have tested WOL using https://wol.aquilatech.com/

 

--------------------- Received Packet ---------------------

Date: Friday, July 13, 2018

Time: 10:46:08 AM

Source: 172.20.10.14:51855

Destination: 172.20.21.255

Length: 102

Protocol: Udp

Port: 9

Hostname:

MAC Address: 30:85:A9:9A:0A:34

 

 

Raw Data:

FF FF FF FF FF FF 30 85 A9 9A 0A 34 30 85 A9 9A

0A 34 30 85 A9 9A 0A 34 30 85 A9 9A 0A 34 30 85

A9 9A 0A 34 30 85 A9 9A 0A 34 30 85 A9 9A 0A 34

30 85 A9 9A 0A 34 30 85 A9 9A 0A 34 30 85 A9 9A

0A 34 30 85 A9 9A 0A 34 30 85 A9 9A 0A 34 30 85

A9 9A 0A 34 30 85 A9 9A 0A 34 30 85 A9 9A 0A 34

 

 

So it is receiving the packets but none of the stations wake up.

[ThomL]

Bios settings enabled to allow WOL?

[mrbios]

The private block is 172.16.0.0 - 172.31.255.255.

 

Ah yea, he's changed it now, it said 172.0 before (unless I'm going blind and he hasn't changed it!?)

[koryo]

Bios settings enabled to allow WOL?

 

Further to this - some certain sleep modes on some models don't allow the workstation to be woken up by WOL (network adapter goes off) - might be worth testing this on your devices too.

[Julian]

Most WOL software, can address the magic packet, to an ip address, as well as a mac address, with a ip address the magic packet will be routed to the correct vlan. I wrote a powershell script to use the DHCP lease database, as a auto updating source of mac and ip addresses.

[fiza]

Further to this - some certain sleep modes on some models don't allow the workstation to be woken up by WOL (network adapter goes off) - might be worth testing this on your devices too.

 

Low Power mode if enabled on Dells does this. We have to switch it off to allow WOL to work.

[ass17]

If your clients are Dell machines then disable deep sleep control in the BIOS located under ‘Power Management’. Also make sure under the same heading the you have turn in ‘wake on lan’.

 

Then you have to make sure WOL/magic packets are enabled in the driver using the loose instructions below:

 

Go to Device Manager.

Expand the Network Adapters section.

Right-click the adapter in use and click Properties.

Click Advanced tab.

Select Wake on Magic Packet from the Property list.

Expand the Value section and select Enabled.

Click Power Management tab.

Select the check box for Allow this device to wake the computer.

Click OK.