Feature Request - Dirty WOL Machine (Magic Packet)

Started by BGP4, March 16, 2025, 06:02:35 PM

Previous topic - Next topic
If someone needs WOL, it needs to be easy for users. Users arent admins, users are lazy, they need scripts etc.

If we inject WOL Packets from another Router using NAT or over same Router using IPSec, we cant WakeUp using Wake-On-LAN.
We can use the UDP Relay Plugin, so the NAT Router will forward Port x UDP to the goal subnet for a specific IP...

Imagine we use a wakeup tool, which creates an UDP Packet with dst-pc-for-wakeup like aa:bb:cc:dd:ee:ff and as parameter for UDP packet an IP Address like 192.168.x.123 or 192.168.x.255.
In the first case, we will know that this IP Address is not there, as the device is sleeping. so no response of being heared..
in this case, the router should be intelligent, and detect, that the package is for broadcast ff:ff:ff:ff:ff layers 2 and resend it here.
maybe we can add a dummy alias ip as neighbour like 129.168.x.222 with broadcast ff.. mac.. so if proxy arp for this IP is enabled.. the OPNsense will send to broadcast.. anyway thats tricky. there should be a simple thing like:
  forward and obey magic packets correctly
 OR
  add an alias ip, when this ip is pinged from IPsec connection n, then wakeup this host. maybe it could be the same ip of the host.
 OR
  just notice that an UDP packet to ...255 broadcast address should just be resend on ff:.... even if in routing mode for IPSec client etc. or behind NAT.

maybe someone may understand whats my concern ;)