About WOL port forwarding

When using WOL with port forwarding

In Previous article, when I actually sent a magic packet from the WAN to the VPN server, the computer started up successfully, but the computer was turned off. After standing for a while and sending a magic packet, I found that it did not start.

Since it works fine immediately after turning off the computer, isn't the packet not delivered due to cache clearing or something? I thought. According to the Wiki, magic packets must be sent with a broadcast address, so I changed the port forwarding setting to a broadcast address of 192.168.100.255, but it didn't work due to security issues.

When I looked it up, it seemed that some people were suffering from the same problem, so there was no answer in Yahoo Answers.

Is the server ARP table clear? It seems that WOL did not work well.

shell


arp -a

Looking at it, it is true that the MAC addressless of 192.168.100.127 was gone.

shell


sudo arp -s 192.168.100.127 (Host MAC address)

If you execute, this entry will be semi-permanent and will not be cleared, so you can use WOL without any problems from now on. However, if you restart Softether VPN or the server itself, the TAP device itself will be deleted once, so you have to execute the above command every time you restart. Well, rebooting isn't that frequent, and I'll leave it as it is.

Recommended Posts

About WOL port forwarding
UDP port forwarding
Try and learn iptablse, port forwarding
Linux ssh port forwarding (tunnel) settings
Port forwarding your web server using iptables
Including docker-nginx port forwarding on AWS Linux 2