Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[goslow2gofast]

Just wondering if anyone has gotten wake on lan to work on the dir-645? Sending the wake packet from the internet, not the local network.

~gs2gf

[FurryNutz]

Have you tried the WOL sticky posts in the FAQ Library? Might help. Some DIR series routers do not support WOL FYI.

[goslow2gofast]

Yes, have read that and other posts on the board here, but never found a combo that seemed to work with the 645, very disappointing.  So wanted to check back here and see if anyone had ever made it happen.

~gs2gf

[FurryNutz]

You might want to call DLink support, level 2 or higher and ask if this router supports WOL, and if not, ask them which ones do?  Let us know if you find out anything. 

[ambercap]

My DIR-645 (A1 f/w 1.03) has an option on the Virtual Server page (under Advanced tab) to forward Wake-On-Lan UDP packets on port 9 to an internal host. I have enabled this but not had the chance to test it yet since currently I can't get DDNS to work properly, but I'll try later today if the WAN IP has not changed yet.

[ambercap]

I just tried WOL and it did not work. However it could be because my external IP might have changed in the last 2 hours, or I've configured the router incorrectly. Perhaps the virtual server rule should be changed from port 9 and IP 192.168.1.4 (the specific PC I'm trying to wake) to 192.168.1.255 (the broadcast address) for it to work properly. I'll try again over the weekend. (I know I'm using the correct MAC address - I tested WOL on the local network yesterday and that worked.)

[ambercap]

I made some changes to my computer's settings to ensure WOL works properly (I have an iMac with OSX Mountain Lion 10.8.2) and tried to re-enable the Virtual Server rule for wake-on-lan to redirect UDP packets to port 9 to my computer's specific IP, and it now works via the internet!

I read that WOL on some computers does not work if the WOL packet is sent to a specific IP, and that the broadcast IP must be used (such as 192.168.0.255), and that is why WOL via a router does not work, but it is working for me just fine.

I did also try force the router to send the WOL packet to the broadcast address on my LAN and that works too but it does not seem necessary. (You can't do this via the web UI, only by telnet into the router and fiddling with the ARP cache.)

[FurryNutz]

Was curious, under Advanced/Applications...Is WoL listed as an option in the preset drop down menu?

[ambercap]

No WoL is not listed under Application Rules, but it is listed in the dropdown under Virtual Servers.

[FurryNutz]

Has VS been configured and tested yet?

[ambercap]

As I wrote in my earlier post, I configured VS rule for WOL to redirect UDP packets on port 9 to the IP of my iMac. It worked perfectly using the Scany utility on my iPhone, using the ddns server and the iMacs MAC address.

[FurryNutz]

Glad you got it working with VS. Thanks for sharing.

[ambercap]

By the way, I tried waking my Mac via the online tool at www.depicus.com and it does not work for me, but the Scany app on my iPhone works every time, so if anyone is having problems getting WOL to work, the problem might not be with the router but with the tool sending the WOL packet (or the computer that you want to wake up is not setup right for WOL).

[goslow2gofast]

@ambercap

So it sounds like in the VS you are directing the WOL packet to the IP (I assume reserved?) that the computer is assigned?  If so, then have you tried waking it after a few days, or maybe easier yet after rebooting the router? My understanding was from other posts here that the specific IP approach you are using only works for a short period of time after the computer to be woken has been turned off. But at some point the router releases that IP and at that point can't forward the incoming packets. That seemed to be the case when I tried to use this approach a while back.

~gs2gf

[ambercap]

Yes I am forwarding the packet to the specific (unicast) address of the computer (192.168.0.4 - I'm not using DHCP), and I've not tested it beyond a sleep time of about 3 hours.

You are right, there is a good chance that after a day or two that IP/MAC will be cleared from the ARP cache and after that WOL will stop working. The router will then have to send out an ARP to get the MAC address but the computer won't respond since it is asleep.

I don't want to leave my computer off for a few days to test this.

However I just connected to my router and listed the arp cache, and next to the entry for my computer's IP it has PERM! This means that the router must have added a static entry for it (I didn't do it) and therefore even after a few days WOL should still work (as long as the router does not reboot)! The entries for other computers don't have PERM next to them. That's interesting.

(Note I'm now using f/w 1.03 B11 (Oct 2012) from the tds.dlink.com.tw site.)

There is another approach that works (at least until the router is rebooted) but it requires telnet into the router. I did test this and it works. What I did was telnet in, then I added a static ARP entry (permanent until the router is rebooted) for an IP address not in use (192.168.0.254) giving it the broadcast MAC address ff:ff:ff:ff:ff:ff as follows:
# arp -i br0 -s 192.168.0.254 FF:FF:FF:FF:FF:FF
Then I added a VS rule to redirect WOL packets to this fake IP, which results in a broadcast.
It worked (but it did not survive a router reboot).