WOL sends on port 40000? Why?

[opnsenseuser]

is there a problem with WOL?
Reinstall but problem still exists.
It was alway working on 7-9. Why is it now 40000?
But even 40000 doesn´t work.

WOL doesn´t work anymore

regards
René

[opnsenseuser]

Maybe its a problem with truenas? I dont´know. I changed nothing.

[opnsenseuser]

Can somebody help me getting wol to work?
Port 7-9 doesnt work. port 40000 also not.

What is the right way?

A few opnsense versions ago it works by using port 7-9. now it doesn´t anymore.
please help

thx

[opnsenseuser]

thats my rule which works since a few versions ago. see screenshot

[XeroX]

More details pls.

What are you trying to wake up? Same subnet? What device? Wireshark capture?

[opnsenseuser]

Same subnet, truenas i want to wake up, but the Interface on truenas hast Not changed and the Interface of truenas is Set to wol enabled. When i See my live log on the Firewall it sends only on Port 40000. no Port 7 or 9

[Fright]

works as expected on my test vm.
yes, wol sends magic packets on udp 40000 by default
https://www.freebsd.org/cgi/man.cgi?query=wol&apropos=0&sektion=1&manpath=FreeBSD+13.1-RELEASE+and+Ports&arch=default&format=html
(as it does earlier
https://www.freebsd.org/cgi/man.cgi?query=wol&apropos=0&sektion=1&manpath=FreeBSD+12.0-RELEASE+and+Ports&arch=default&format=html
)
but this should only play a role in terms of setting up firewalls. the client should not pay attention to this level. the client NIC is only interested in the magic packet pattern imho

[opnsenseuser]

But Even if i Open Port 40000 nothing Happens

[Fright]

is it possible to check on anything other than truenas? (Checked on a regular workstation (asus mb with intergaretd realtek chip and WOL enabled) on the network - it works).
I don't work with truenas, but as I understand it, they can have problems with WOL:
https://www.truenas.com/community/threads/enable-wol.95856/

[opnsenseuser]

I checken the Interface with ifconfig and the Interfaces sag’s wol g is enabled

[opnsenseuser]

can one rule out that it is due to opnsense? and what port do I have to open on the firewall for wol

[Fright]

sorry, there is only an idea to check the bios settings ("Power on by PCI/PCI-E" or some)
can one rule out that it is due to opnsense? and what port do I have to open on the firewall for wol
"let out anything from firewall host itself" should be enough imho
you can try with firewall temporary disabled (pfctl -d) or just create fast rule with "allow any from LAN" (but it still
seems to me that the problem is either in truenas or in the bios settings of the truenas host)

[meyergru]

The thread linked on the TrueNAS forums specifically says that of TrueNAS SCALE 22.02.2, the previous method of WOL does not work any more. Further down in the thread, someone gives a way of re-enabling it.

The reason seems that on shutdown, the WOL g setting is being reset in newer TrueNAS versions, so if you look at this setting when the TrueNAS box is up is by no means an indication of it being enabled when the system is down and then receiving a WOL packet.

Also, I always had to use the MAC address to wake up machines, an IP broadcast address like 192.168.1.255 alone never worked for me as IP is not active when the box is down and network adapters usually only react to WOL packets directed at them. But I think that you already did that, only your images do not reflect the MAC.

[opnsenseuser]

After updating to OPNsense 22.7.3 release, WOL works again! :-)
But i also did yesterday an truenas update. Maybe the problem was on truenas. I don´t know