Print

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

[jaffadog]

Hello All,

I've going through the trials and tribulations of getting WOL running on my DIR-655.  Well, I'm actually trying to get wake-on-wan (WOW) or WOL via internet working... There are plenty of threads out there that provide tidbits, but they all seem to be lacking some crucial piece of information - like what firmware version people eventually succeeded with - and whether the solution proved to be long lived (was not subject to the arp cache aging issue).  So, I hope this thread may become the single source of truth - over time - to provide comprehensive information and solutions, so that more people may get this seemingly simple piece of functionality to work.

So with that, let's visit some of the purported issues.  Having read many posts before starting this thread, it seems clear to me that some of these issues manifest in some firmware versions but not others.  So as you contribute to this thread - PLEASE explicitly state what firmware and hardware version your information pertains to. On to the issues...

1. Validator prevents use of x.x.x.255 (broadcast ip) in the Virtual Server configuration.  There are workarounds for this issue, including disabling javascript in your browser; or switching your subnet mask so that you have a different broadcast ip (x.x.x.127).
2. The arp cache gets flushed - after which point the WOL packet does not get delivered to your dormant PC.  Not aware of any effective workaround.  Setting a static dhcp reservation does not seem to be effective.
3. Must use the "Wake-on-Lan" preset in the Virtual Server configuration rather than creating your own identical rule.  There's something magic about the preset?  Not sure why this makes a difference, but some folks claim it did.

I currently have the 1.34NA firmware loaded, and I have hardware version A3.  I'm using the "Wake-on-Lan" Virtual Server preset, and it lets me specify x.x.x.255 (broadcast) as the internal IP - no validator/javascript error preventing me from doing this.  However, I do seem to be suffering from the arp cache flush issue.  After the PC sleeps for a few minutes, I am no longer able to wake it from a WAN magic packet.

Please contribute your information to the table below.  Add specifics about your working configuration.

Thanks!

Firmware	Hardware	WOL Works	Can set x.x.x.255	ARP flush issue	Notes
1.34NA	A3	no	yes	yes	-
1.33NA	?	?	?	?	-
1.32NA	?	?	?	?	-
1.31NA	?	?	?	?	-
1.21	?	?	?	?	-
1.21SS	?	?	?	?	-
1.20	?	?	?	?	-
1.11	?	yes	yes	?	Sounds like lots of people stuck with 1.11 because WOL works there

[hackztor]

Yes, firmware 1.11 works best for the wol. Passes the broadcast to 192.168.0.255 ect to the correct location. I finally just felt like upgrading after 1-2 years on it to 1.34 and wol does not work well. In the end it is not as important to me anymore, because I can set up my popcorn or my nas to wake up the computers on the network since those devices are on all the time anyways. It is the one feature I wish dlink would still have supported as it was useful.

[kyeck]

I, too, am trying to get WOL working, but I've got the DIR-655 V2 with the latest firmware, 2.00NA.

Can anyone tell me how to configure it to work?

I've tried setting up a Virtual Server as others have said, selecting the "Wake-On-Lan" application, but as the previous versions, it won't let me save an address of 192.168.0.255 (out of range).  I've also tried the java.submit() command to no avail.

Any insight would be appreciated.  Please tell me D-Link supports WOL!

Thanks!

[FurryNutz]

http://forums.dlink.com/index.php?topic=16418.0

See if anything will help you out. Let us know.

[emax]

Kyeck,

Have you found out a way to do this with the 2.00NA firmware?

[dagodfather]

I got WOL to work for DIR-655, Hardware Version: B1, Firmware Version: 2.00NA

FIRST STEP
On SETUP, NETWORK SETTINGS, I changed the Subnet Mask to 255.255.255.128, where the Router IP Address was already set to 192.168.0.1

SECOND STEP
I then saved the change. My router hung and had to reset it, but the change occurred. Admittedly this is a pain in the ass, but blame D-LINK.

THIRD STEP
On ADVANCED, VIRTUAL SERVER, I added 192.168.0.127 as the device to wake-up EVEN THOUGH the actual IP Address of the PC I want to wake-up is 192.168.0.100. I am not an expert, but I believe ALL PCs on my local network that are setup to Wake-up On Lan, will in fact wake-up. I can live with that as ONLY my PC that is PERMANENTLY ASSIGNED 192.168.0.100 is set to wake up which is exactly what I want. BEFORE saving the changes on ADVANCED, VIRTUAL SERVER, I additionally set Name to Wake-On-LAN, Public and Private ports to 9, Protocol to UDP, Schedule to Always, Inbound Filter to Allow All. I then saved the changes.

I can't begin to tell you how many suggestions I tried that did NOT work! However the above procedure worked for my DIR-655, Hardware Version: B1, Firmware Version: 2.00NA.

[mh0001]

I don't know why there should be any problems with WOL.
I'm using a DIR-655 Revision A5 with firmware 1.34EU.

I just activated the Virtual Server - profile "Wake-On-LAN" pointing to 192.168.0.255, nothing else. I don't need to do any tricks to set this setting, I don't get any errors like "out of range" or something like that. If your Subnet-Mask is 255.255.255.0 and your IP-range is 192.168.0.100 to 192.168.0.199 (0 everywhere!) then it should accept it.
With everything else than this 0 I get out of range, too.

And it works, I can wakeup every PC at home I want to. All have fixed DHCP-reservations (but I don't even think this is important, because 192.168.0.255 packets are accepted by everything that is connected to the router).
I have already used it over 3 weeks, two times. I switched my PC off before I went to vacation, and after 1 week I sent the WOL package over the internet to start the PC which has an remote server installed, and it worked without any problems. I did several complete shutdowns and reboots over internet.

I noticed only one situation in which it doesn't work. If you set the PC-specific IP for WOL instead of 192.168.0.255, then it works just for the next minutes after you switched off your PC (ARP flush issue I think?), but if you set the IP broadcast, there are no problems at all.

I have 3 PCs at home, installed remote control servers on each of them, and wrote a list with their MAC adresses, then I can just use this website (http://stephan.mestrona.net/wol/) to reactivate the PC I want to have access to.

It took me 5 minutes to set up a completely working Wake-On-Internet without having any knowledge about WOL before, so I really don't know why I always read statements about the DIR-655 and other Dlink-router that this isn't possible.
Maybe differences between the EU and NA firmware?

[dagodfather]

I have DIR-655, Hardware Version: B1, Firmware Version: 2.00NA, where the webpage will NOT allow me to use a Virtual Server with an address of 192.168.0.255. Specifically, when I enter that address and other settings you suggested, the response I get when I save the changes is that 192.169.0.255 is illegal! Additionally, I viewed the webpage code and can see where it blocks using 192.168.0.255. Apparently is does matter that I am using Firmware Version: 2.00NA for  DIR-655, Hardware Version: B1.

[daedao]

I have DIR-655, Hardware Version: B1, Firmware Version: 2.00NA, where the webpage will NOT allow me to use a Virtual Server with an address of 192.168.0.255. Specifically, when I enter that address and other settings you suggested, the response I get when I save the changes is that 192.169.0.255 is illegal! Additionally, I viewed the webpage code and can see where it blocks using 192.168.0.255. Apparently is does matter that I am using Firmware Version: 2.00NA for  DIR-655, Hardware Version: B1.

dagodfather

I'm on hardware A4, firmware 1.20ON.
I have a fix for your problem. It's a simple, yet effective hack.

Here are the steps:
************************************************
1) Download and install Firefox 4
2) Install Firebug as an add-on for Firefox
3) In Firefox, login in your router's administration page
4) Go to Advanced --> Virtual Server
5) Change the IP to 192.168.0.255 for the WoL rule
6) Open Firebug
7) In Firebug click on Console
8 ) In the console enter the following line of code


page_verify=function(){return 1;}


9) Click on Run in Firebug
************************************************
10) Then on the page, Virtual Server, hit Save Settings


Voila, hackfix.

Here, an image as  "a image is worth 1000 words" guide.




It should work, because it works on my setup.
The image is a bit large, because I was lazy when I wrote this post, you'll have to scroll  right, or you could download the image on your PC for easy viewing.

[dagodfather]

Thank you, daedao! I will give it a try as it seems like a better solution.

[daedao]

Thank you, daedao! I will give it a try as it seems like a better solution.

Let us know if it works on your version of the router, so others might have a solution for their routers.

Oh, and the hackfix if nothing permanent. That mean, that the next time you want to change some Virtual Server's rules, you'll have to follow these steps again, in order to save the 192.168.0.255 IP.

[dagodfather]

It did not work. I still get the following message: The 4th range of IP address must be between  1 ~ 254.
It is possible that I did not correctly follow the instructions you provided.

[daedao]

It did not work. I still get the following message: The 4th range of IP address must be between  1 ~ 254.
It is possible that I did not correctly follow the instructions you provided.

You're doing it wrong, if it pops up  a message. My hackfix overloads a JavaScript function, so it's impossible for any kind of popup to be displayed.

[emax]

daedao,

I get the same message as dagodfather.  I don't think this hackfix works with the: Hardware Version: B1, Firmware Version: 2.00NA.  Thanks for the info though.

[daedao]

 

daedao,

I get the same message as dagodfather.  I don't think this hackfix works with the: Hardware Version: B1, Firmware Version: 2.00NA.  Thanks for the info though.

On the page "Virtual Server", in your browser, could you view the source and then copy it and send it to me as a message?
I might be able to help.

From what I've seen D-Link uses a JavaScript function called page_submit() on my router, to save the settings in the "Virtual Server" page. In this function, it calls another function page_verify(), that validates the values from all the inputs. If this function return the numeric value 1, then the values are considered as valid.
Maybe your version of the firmware, uses a JavaScript validation A BIT different than 1.20 firmware, but something tells me that with a little bit of hacking, this validation could be bypassed in order to save the broadcast IP.
So if you could provide the source code, I'll look into it.