D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: roundsjr on July 16, 2009, 04:56:28 PM

Title: Why a WOL preset if the router can't do it????
Post by: roundsjr on July 16, 2009, 04:56:28 PM

Why would this router have a preset for Wake On LAN in the virtual servers if it can't do it??  Or is it there in case anyone would want to wake the PC up within 10 min. after it falls asleep???  Jeeeeez!!

Title: Re: Why a WOL preset if the router can't do it????
Post by: cmos on July 30, 2009, 10:32:06 AM

I second that... it's pretty stupid...

Title: Re: Why a WOL preset if the router can't do it????
Post by: casuncion on July 31, 2009, 07:23:48 AM

After reading this forum for the past couple of months, I finally got WOL to work over the internet.  The solution is talked about here:

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

Although this solution did not work for me the first time.  I tried the different subnet masks (255.255.255.128 and 255.255.255.0).  It was only after reading this thread that I realized that there was a preset Wake-On-Lan in the Virtual Server Application Name List (the last drop down item).  I discovered that it was important to use the preset Wake-On-Lan to make this work.  Prior to this, I had created my own "WOL", which was unsuccessful.

I am using subnet mask 255.255.255.0 and used the "trick" of disabling JavaScript in Firefox in order to save 192.168.0.255 as a valid Wake-On-Lan IP address.

So...the preset Wake-On-Lan was the key for me to making WOL to work over the internet.

Title: Re: Why a WOL preset if the router can't do it????
Post by: Lycan on July 31, 2009, 10:31:41 AM

I'll see if I can get that corrected.

Title: Re: Why a WOL preset if the router can't do it????
Post by: cmos on August 04, 2009, 10:07:00 AM

Quote from: casuncion on July 31, 2009, 07:23:48 AM

After reading this forum for the past couple of months, I tried the different subnet masks (255.255.255.128 and 255.255.255.0).  It was only after reading this thread that I realized that there was a preset Wake-On-Lan in the Virtual Server Application Name List (the last drop down item).  I discovered that it was important to use the preset Wake-On-Lan to make this work.  Prior to this, I had created my own "WOL", which was unsuccessful.

I am using subnet mask 255.255.255.0 and used the "trick" of disabling JavaScript in Firefox in order to save 192.168.0.255 as a valid Wake-On-Lan IP address.

So...the preset Wake-On-Lan was the key for me to making WOL to work over the internet.

Thank you! That did the trick! Choosing the Wake on Lan from the Application Name list finally got it working. For good measure I tried to revert my subnet mask back to 255.255.255.0 but it didn't work so I ended up using 255.255.255.128 as the subnet mask and 10.0.0.127 port 9 UDP (I'm on a 10.x.x.x network).... Lycan, it may be a good idea to put this and the other thread as a sticky or document how to use WOL on newer firmware revisions I'm on 1.32NA... Thanks Again guys/gals!