WOL Address only first 6 values

[brians]

I tried this and didn't work, but not sure if my PC is working correctly to do a WOL.

However, I noticed that if I enter a MAC address eg. 11:22:33:44:55:66/192.168.10.10 (mac address is just and example here)

It only lists the first 5 vales:

Is this just cosmetic/normal due to node naming limitation?

 

[bpwwer]

You're looking at the node address and yes, the ISY limits what characters and how many can make up a node address.  The node server is converting the mac address to a node address by stripping out the characters that aren't legal in an address and truncating it to fit the length limitation.

If you look at the node server log it should show it sending the packet to the proper mac address.

[brians]

I have it working, I had to make some changes to my Network Driver in Windows 11.

Pretty much this in case anyone else is interested.

 

https://rog.asus.com/forum/showthread.php?101283-Wake-on-LAN-not-working-from-shutdown-Asus-Deluxe-Z170

I also have WOL app tested working now on a VM on my HP server which works.

I also have WOL setup in my pfSense router.

However, after a couple hours while I went out and came back, WOL is no longer working through IoP and Node server. I can however still use the Windows app on my server to WOL my desktop, and can use WOL on my pfSense router.

The only thing I could think of is that my IoP is connected to a different switch downstream from main switch, where my server an pfSense and Desktop are connected to... maybe the WOL doesn't broadcast the MAC address of my Desktop correctly from the remote switch. To test this, after failing like a half dozen times, I started my desktop and ping the IoP IP from my desktop, this updated the switch's ARP table to learn the MAC address of my desktop, then shutdown desktop and then try IoP WOL right after and it works!!! Therefore some issue with broadcasting WOL over multiple switches in my case! I will look into this maybe this is limitation of WOL.

 

 

Edited June 3, 2022 by brians

[larryllix]

I have it working, I had to make some changes to my Network Driver in Windows 11.
Pretty much this in case anyone else is interested.
 
https://rog.asus.com/forum/showthread.php?101283-Wake-on-LAN-not-working-from-shutdown-Asus-Deluxe-Z170
I also have WOL app tested working now on a VM on my HP server which works.
I also have WOL setup in my pfSense router.
However, after a couple hours while I went out and came back, WOL is no longer working through IoP and Node server. I can however still use the Windows app on my server to WOL my desktop, and can use WOL on my pfSense router.
The only thing I could think of is that my IoP is connected to a different switch downstream from main switch, where my server an pfSense and Desktop are connected to... maybe the WOL doesn't broadcast the MAC address of my Desktop correctly from the remote switch. To test this, after failing like a half dozen times, I started my desktop and ping the IoP IP from my desktop, this updated the switch's ARP table to learn the MAC address of my desktop, then shutdown desktop and then try IoP WOL right after and it works!!! Therefore some issue with broadcasting WOL over multiple switches in my case! I will look into this maybe this is limitation of WOL.
 
 

WoL needs to be on the same subnetwork as the ip address is xx.yy.zz.255 for any device.
The MAC address us what is particular.

With or eithout a bridge between subnets I doubt it will ever work.

Sent from my SM-G781W using Tapatalk

[bpwwer]

There could be issues with the way it's being broadcast as well.  How FreeBSD does network broadcasts is different from how it's done on Linux and the Python library being used to do the WOL in the node server was probably written to work on Linux.

In general, the IP address shouldn't be needed when sending out WOL, but without it, it didn't work at all on FreeBSD.

If there are too many problems getting this to work, I may have to abandon using the library and just write the code to handle the FreeBSD broadcast directly in the node server.

[brians]

3 hours ago, larryllix said:

WoL needs to be on the same subnetwork as the ip address is xx.yy.zz.255 for any device.
The MAC address us what is particular.

With or eithout a bridge between subnets I doubt it will ever work.

Sent from my SM-G781W using Tapatalk
 

The Polisy is on the same subnet, but not on the same switch as my PC.

I believe is issue with the switch IoP that it is connected to not rebroadcasting after its ARP table, or dynamic forwarding table clears.

 

 

 

[brians]

2 hours ago, bpwwer said:

There could be issues with the way it's being broadcast as well.  How FreeBSD does network broadcasts is different from how it's done on Linux and the Python library being used to do the WOL in the node server was probably written to work on Linux.

In general, the IP address shouldn't be needed when sending out WOL, but without it, it didn't work at all on FreeBSD.

If there are too many problems getting this to work, I may have to abandon using the library and just write the code to handle the FreeBSD broadcast directly in the node server.

Ya, my pfSense doesn't require IP address.

I will try placing a test PC on the same switch as the IoP and then trying WOL from it, also will try my other WOL program and pfSense to see if it traverses back through to that switch and wakes up the host. I will also try app on my laptop and plug in and see if wakes up my other PC. This will help rule out if my switches are at fault.

 

[larryllix]

13 minutes ago, brians said:

The Polisy is on the same subnet, but not on the same switch as my PC.

I believe is issue with the switch IoP that it is connected to not rebroadcasting after its ARP table, or dynamic forwarding table clears.

 

 

 

hmmmm.. that could be  LAN switch problem. IIRC Switches determine which device (IP) requests a response and only passes the packets through to the device that wants it. This would be opposed to a LAN hub that just broadcasts everything to everybody and it is up the the receiving card to only listen to it's own packets.

Maybe some LAN guru knows more about whether WoL can even function through a switch. OTOH my isy was on the other side of a switch from my TVs and other devices I was turning on using WoL, just fine.

[kzboray]

WOL packets are layer 2, or broadcast traffic. So every device on the sub-net from which the packet was sent will see the incoming WOL packet. Since the WOL packet is addressed to one unique device via it's MAC address, only that NIC will reply.

As long as both the originating device and the intended target device are on the same sub-net, there shouldn't be a problem with communications. Switches will pass the layer 2 traffic (broadcast) to all ports unless you have segmented the switch into layer 2 VLAN's. Most consumer switches don't do this. Some allow you to segment port's by layer 3 VLAN's, but not layer 2.