![]() While you’re in your router’s options, bind the NAS’ IP with its MAC address. Due to the fact that a “Magic Packet” (the data packet that wakes your hardware) is always broadcasted to the MAC address and not to the IP address, we need to tell our router that the signal it is receiving from an IP and port, should go to a MAC address. “Source target” : I think that value should be left empty. The 3 following lines are for Wake on lan attempts. The first line is to access your NAS’ interface. To make sure which port was the right one, I added many port forwards in my router. So I found out after many tests that my Diskstation uses the port 9. But he doesn’t have the same Diskstation or router I have. Is there a way to know it other than with trial and errors? According to bigeddu on the Synology forum, the port is 22. I really had no idea which port the router or the NAS uses for waking on LAN. To configure the devices for wake on wan, the 2nd step is to setup port forwarding on the router. I also tried port forwarding instead of DMZ, but it didn’t work for me. While this solution is not ideal, it has solved part of the problems for me. What it does is pass on all internet traffic to the router. So the solution I found was to use the modem-router’s DMZ function. There may be ways to hack this modem router but I didn’t try. Big problem here : my modem router does not have bridge mode and my ISP does not intend to add this function via a firmware upgrade in the future. To solve that, it is advised to put the modem router into bridge mode, so that the router gets a public WAN IP. But wake on wan needs a DDNS that reaches its target: the NAS. Instead, as per my tests, when you type this address, you’ll see the web interface of your modem-router. This web interface won’t appear in your web browser if you don’t fix the problem. Your own NAS DDNS, will look like :5000, and will be useful to connect to your NAS’ web interface remotely. So there are a lot of things I can’t do on the router with a private WAN IP: activating a DDNS for the router, and all AI Cloud services, which rely on DDNS, like Cloud Disk, Smart Access, Smart Sync.Īnother problem is that your own DDNS, the one we will set up later in this article, will not be reachable if this limitation is not avoided. Its a known fact that dynamic DNS concept will not work on dual natting. This router may be in the multiple-NAT environment and DDNS service cannot work in this environment.” That is because the asus router took an internal ip from my modem. Why is my router’s WAN address private? Because the SFR modem-router is issuing a private IP to the Asus router.īecause of that, the Asus router is complaining that “The wireless router currently uses a private WAN IP address. But for external access to our devices, it’s better to have a public address. If it looks like 10.x.x.x, .x or 172.16.x.x to 172.31.x.x then you have what is known as an RFC-1918 IP address (often referred to as private addresses). ![]() But before we start, there’s something we should check…Ĭheck the WAN IP address of your router. We want to start configuring the devices for wake on wan. Try these apps. You should observe the target PC powering up almost instantly upon hitting enter. I’m not sure, but when one uses wake on lan, only the MAC address is involved. ![]() Try also 7 and 22 if 9 does not work.īut adding an IP should not be absolutely necessary. Just enter your NAS’ local IP and MAC address,Īlso add the local port. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |