Remote wake-up [or power-on] via wide area network (intelnet) diagram

WAN remote wake-up is different from LAN remote wake-up, which requires the support of hardware such as motherboard, network card and so on, and requires a valid intelnet connection, unlike LAN remote wake-up, WAN remote wake-up requires a router, So I'm going to go over the details on how to set up on the router to support WAN remote wake-up, if you've successfully made a LAN remote wake-up call.

introduction of WOL (remote wake-up) tool

There are many software implementations for remote wake-up, and the principle is the same. Here are a few common WOL software:

Lanhelper

Magic Packet Utility

Netwaker for Windows

Wakeonlangui (http://www.depicus.com)

Second, prepare

WAN differs from LAN in that there are many network devices, such as routers, on the WAN, which may make the magic packet package inaccessible to the computer card we want to wake up on. Therefore, to achieve wake-up over the Internet, you must have the support of your router. The following is an example of my tp-link wr841n wireless routing to illustrate the configuration process.

First of all ensure that the router can normally access the Internet, that is, through the service provider to get a public network IP (for the family, ADSL, Cable Modem is a common way to access the Internet), into the Router Web configuration page http://192.168.1.1.

iii. Port Mappings (virtual server)

Click on "Forwarding Rules"-> "virtual Server", add a new entry, the port is 2301 (2301 is the default port number, can also be other port number, as long as not with other conflicts), IP address for the need to wake the computer network card used by the IP address (such as 192.168.1.250), the protocol is UDP, and make it in the "effective" state.

This step allows the router to receive data that is sent to its 2301 port to be forwarded to this computer with an IP address of 192.168.1.250.

Four, the binding between IP address and MAC address

Click on "IP and MAC bindings"-> "static ARP Binding Settings", add a new entry, MAC address added to the NIC (on the wake of the computer) Mac, such as 50-E5-60-CA-1A-4A,IP for the previous step set the IP address: 192.168.1.250.

Note: Remember to enable the "ARP binding" feature of the router (the red circle portion of the picture), otherwise this step is not set to take effect.

When a router receives a magic packet package that is sent from the Internet to port 2301, the router forwards the Magic Packet packet directly to the 192.168.1.250 because the port mapping is set. But because the computer is processing shutdown state, ARP can not be broadcast to find 192.168.1.250 this computer, Magic packet packets will be discarded by the router, so the static Ip-mac binding, Enables the packet to be sent directly to the NIC with the MAC address 50-e5-60-ca-1a-4a.

At this point, in theory, remote wake-up over the Internet can be successful. However, if the remote host does not have a static IP address configured, but instead obtains a dynamic IP address through DHCP, there is still work to be done to ensure that it is foolproof.

v. Static IP address assignment

As we all know, the DHCP lease agreement is valid, the Tp-link DHCP lease is valid for 2 hours by default, In order to ensure that the remote computer can obtain 192.168.1.250 this IP address after startup, you need to set up a static address assignment in the DHCP server, that is, 50-e5-60-ca-1a-4a statically assign 192.168.1.250 this IP address for MAC address, and never expire.

vi. using Dynamic DNS features

Use dynamic DNS on routers so that you can use a domain name to access without having to view frequently changing public-network IP (ADSL dial-up IP is often changed). At the same time, allowing routers to do unwarranted web management is convenient when we can check the state of the router anywhere.

Speaking of DDNS, had to mention the famous peanut shell, Tp-link router By default embedded Dynamic DNS function, just to the peanut shell of the official website to register a passport, and apply for a free domain name, and then login on the router. Login successful, you will see the domain name, so that the peanut shell will be domain names and routers on the public network IP address binding together.

Vii. remote wake-up using third party tools

Visit the Http://www.depicus.com/wake-on-lan/woli.aspx this page, which is a depicus provided by an online remote wake-up tool page, easy to use. The working interface is as follows:

Below is a description of the four parameters for remote wake-up:

Your network Cards MAC Address:(internal local Area network) the network card MAC addresses of the remote host, not the MAC address of the router. [At the beginning I was wrong here, filled with the MAC address of the router, how can not wake up remotely] Any Computers IP number or FQDN: the public network IP address that the router obtains or the legal domain name that is bound using the peanut shell DDNS. It is best to use the DDNS feature to bind a domain name, because the domain name is unchanged, and you don't know when your router will be able to retrieve the public IP address from the ISP service provider again. However, if the DDNS is used, the IP address of the router is automatically updated to the Peanut shell server even if it is changed. Your Subnet Mask: subnet mask. This is important, because the router is dynamically from the ISP to obtain the IP address, you do not know the IP address corresponding to the subnet mask, so simply fill in the 255.255.255.255, which means that the only IP address, not a network segment. Any port number : the network port, the router listens to the network port all the time, and forwards it once it detects a packet being sent to that port. With the above configuration, I have successfully awakened my server remotely over the Internet. Did you succeed, too?