Wake on LAN (WOL) across different VLANS on SG-300-10

[Romeo Sulzer]

Hello there,

I am trying to get WOL working across different VLANS on a SG-300-10 Switch in Layer 3 Mode.  To achieve this, I've setup an UDP-Relay (GUI menu IP Configuration) for UDP-Port 7 to 255.255.255.255 (this should flood all interfaces with the paket), however, WOL doesn't work across different VLANS.  When I am connected directly to the corresponding VLAN, WOL works fine within the same subnet.  Am I missing something here?

Any feedback highly appreciated!

Many thanks!

[David Hornstein · Accepted solution]

Hi Romeo,

Had a few minutes to try it out on my SG300-10P in layer 3 mode.

My NAS unit is WOL capable and i thought I would use it in my test environment..

Ran a baseline test to check my Magic packet sender  from my PC 'woke' up my NAS unit.

As you would expect, on the same subnet,  the WOL magic packet caused my NAS unit to power up, with no issue.

But that's not really the test, just some baseline testing to check that my WOL magic packet sender and NAS worked ok.

The screen capture below shows  WOL Software i used on my PC.  Why did i use this software, no reason except that it was freely available. I'm sure other WOL software out there for different platforms that will work equally as well or with more features.

Firstly,  i note from your question,  that you used UDP relay to destination port 7,   well that's the default setting on the UDP relay on my switch.

I wonder why you used or stayed with UDP destination port 7, because Magic packet senders can use different UDP destination ports?

I had to use wireshark to see the real destination UDP port  that my WOL magic packet sender uses.

Notice from the wireshark capture above,  that my Magic packet software uses UDP destination port 9, NOT the default that you may see on the switch. Ignore what wireshark labels that port.

Ok I then created a VLAN  which I named "VLAN2"  with a VID=2 on my SG300-10P (SRW2008P-K9-NA)

I added an IP interface of 192.168.2.1/24  to VLAN2, which is a different network when compared to the default VLAN.

I then added switch port three to this newly created VLAN as a untagged member of VLAN2.

The default VLAN (VID=1) has a IP network address of 192.168.10.0/24.

My NAS unit  (WOL capable)  has a IP address of 192.168.10.61.

I plugged my PCt to vlan 2 and statically assigned 192.168.2.2/24.  This is the PC that has the  Magic packet software.

I added a static route to my WAN router, just so I could access the WAN router from my PC attached to VLAN2.

I tried the WOL magic packet software  and my NAS did not power up.  This was expected as the magic packet broadcast would never jump over a LAN boundry to a different VLAN..

Now i tried to setup a UDP relay so that the WOL Magic Packet would 'jump' the network interface  from  VLAN2 to  VLAN1.

So I setup and added a UDP relay entry to my SG300-10P.   See the screen capture below.

I must admit, I  am used to using  UDP relay to normally take a netbios broadcast and  unicast  it to a MS server.

But check out the screen capture below, I set the switch to send the UDP relay to the broadcast address of the VLAN1 network.. The Wakeup  magic packet sent from my PC in VLAN 2 must have forwarded over the VLAN boundry as my NAS unit woke up.

So check, using wireshark,  the destination UDP port of your WOL software, and then create an appropriate UDP relay.

Experiment and play with this once you successfully get your WOL device powereing up correctly.

regards Dave

If I answered your question,  please rate the relevance of this answer

[Romeo Sulzer]

Dear David,

Thank you so much for taking the time to try this out.  Indeed it was the port, I had the UDP-Relay set to forward Port 7 and my WOL-client used UDP Port 9 Now I was able to Wake up my Server across 2 VLANs!  Great - thank you!

Kind regards,
Romeo