Print

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

[limey_rick]

Hello,

I have been trying in vain to setup my home network so that I can perform wake on lan (WOL) over the internet. I have been able to do WOL with a magic packet utility within my local network - so I know that the PC NICS are configured correctly - but this does not work when I try it from my office for example, over the internet.

I have a virtual server set up forwarding ports 9 and 7, UDP to 192.168.1.101 initially, but found some threads about using the broadcast address so changed this, but still no luck. I had to downgrade to 1.20 from 1.21 as I found several threads here about firmware versions not allowing broadcasts.

My setup is as follows:

Router: 192.168.1.1
PC1      192.168.1.101 (static assigned by MAC address in the router)
PC2      192.168.1.102 (static assigned by MAC address in the router)

Broadcast address was 192.168.1.255

I am stuck now so if anyone has any experience of diagnosing how to see if the setup is correct or how they got it working, it would be appreciated.

Thanks, Rick.

[Demonized]

searching this 655 forum for this already discussed topic will save you a lot of time...

[limey_rick]

As mentioned, I have already searched the forum for this topic, tried many of the suggestions, but still cannot get WOL to work.

[Fatman]

cannot get WOL to work.

You said it!

[Demonized]

It doesn't work.

[limey_rick]

Here is a link to a post where someone has it working:

http://www.broadbandreports.com/forum/r22315056-DIR655-Virtual-Server-broadcast-address-in-131

Also, if you read all the threads in this forum, several DIR655 users had it working at some point.

Also, why would the router have a WOL option in the Virtual Server settings if there was is no intent to support it? Maybe to keep the forums busy perhaps.

[limey_rick]

Okay, so I have this finally working!!

The problem seems to be well documented in other threads; in previous firmware versions of this router, WOL was possible using the virtual server and forwarding port 9 (normally) to the LAN broadcast address (192.168.1.255 is mine for example). However, DLINK (thank you) decided to stop an IP address ending in 255 from being entered in the virtual server page in later firmware.

I figured out a way around this and now I can wake my PCs from the internet when I am at work. Because Java script is used to validate the IP address entries, I just turned off Java script in my firefox browser while I was on the virtual server page, entered the broadcast IP address I wanted to use as above, turned javascript back on and was able to save the settings. Now when I go to the virtual server page, the broadcast IP address remains.

Now I can send magic packets to any of the PCs on my LAN, over the internet using a Dyndns IP address and hey presto!! 

[cxny]

I just bought the DIR665 and began to set it up tonight. I also tried setting up WOL broadcast forwarding but it didn't work, unlike my 12yr. old USR that did! But since I only have one PC that I wanted to wake up I got it to work this way (not using Virtual Server settings):

1. Go to Advanced ->  Port Forwarding
2. Check a new box to enable a new rule and give it a name, ex. WOL
3. Under IP Address enter your PC's address, ex. 192.168.0.10 (not 192.168.0.255)
4. under UDP enter 7, 9
5. Leave the defaults for Schedule: Always and Inbound Filter: Allow All
6. Save Settings and Reboot Now.

It tested fine from the web - I used this site: http://wakeonlan.me/

btw, that site requires your PC's mac address to be entered with the dashes. They also tell you they'll send out UDP 9 but they sometimes they send UDP 7 instead - just enable both to make things easier from any site you choose.

*I also woke up my PC using an iPhone right from within the same room (using same website above), but I had to turn off Wi-Fi and only use 3G, otherwise the site complained that I was sending to the same PC I was on.
(of course they meant the router, which the phone was also connected via Wi-Fi).

[Fatman]

You will find that method fails if your computer has been of for any length of time.

[cxny]

Thanks for the heads-up. I'll have to test that later.

[cxny]

Well, you were right. I'll have to try your method next, else I'm sending this router back because that's a key feature I need.

As an aside, I'm having a problem where the DHCP server is not working. 
'Acquiring Network Address...' in XP. Although it does give an IP (which has been reserved) but browsing fails. I had to go in and release and renew my internet connection IP before it worked again. Weird that those 2 things are related. So this router looks buggy so far. I really thought it would be just like the DGL-4300 I bought my girl 2 yrs. ago - that one is much more solid in comparison.

[limey_rick]

I also pinged D-Link through their online support to get some more information before I figured out how to get it to work for me. Here is the response (a month after I sent the query):

*** START ***
Dear Richard Evans,

Your Case ID is DLK400376212.

[Critical: Please do not change the subject line of your email when you reply. Leaving the subject line as it is will allow us to review your complete history and help us to better serve you.]

Date of Reply: 6/30/2009
Products: DIR-655
Operating System: Windows Vista Ultimate

It is not that it supports or not, because this router is capable of Forwarding ports. Maybe if you reserve the MAC address on the router's DHCP page, so it will not need to send a 'who is' packet. Beyond this, you will need to focus on your WOL NIC device.

Should you require further assistance with your D-Link products, please reply to this message, or call toll free at 877-453-5465.

Thank you for networking with D-Link.

Sincerely,
D-Link Technical Support
*** END ***

This was a completely useless response; according to DLINK then, its not a question of whether its supported or not. I guess its not supported properly nor correctly, but some people seem to have workable solutions.

[Fatman]

That case was answered in ~8 days (still longer than it should have been but nothing like a month), more troublesome is the fact that it is being quoted slightly out of context.

He was saying that it is not that port forwarding for UDP/9 is supported or not, but that the MAC will fall out of your ARP table.  He suggested adding a reservation hoping that would create a static ARP entry (a nice try, but it does not work for this product).  Beyond that he was telling you you are going to have to find a way to keep that device in the ARP table (which is something that can not be done from the DIR itself).

As for solutions, the only one I am aware of (which is posted in this very thread) is extremely hackish, and he couldn't have suggested it.

The biggest problem here is that the only way to accomplish WOL is to either exist on the same L2 network (What WOL was designed for) or to use a L3 broadcast address (which is incredibly insecure).

I would not forward any traffic to L3 broadcast for any reason, which is the reason our validator won't let you.

[Appiejs]

Hi All,

I had the same problem as some other, that WOL didn't worked from the internet.
It seems that the broadcast address x.x.x.255 doesn't work.

So I changed my DHCP subnet to x.x.x.128 and use the IP range from .1 till .128
When you do this you can use the broadcast address x.x.x.127 and it works 

In the router you go to: Advanced \ Virtual Server
Then you select application name: Wake-On-LAN (port 9)
And fill in your broadcast address as mentioned above.

Save settings \ reboot
Then you can use the website www.wakeonlan.me to try it.

Also you can see if a packet is deliverd through the router.
In the router go to: Status \ Internet Sessions
Here you can see if a packet is sent to you local x.x.x.127:9 address.

You can also start a ping to see if the PC is starting up: Tools \ System Check.
Works for me.
Good Luck

[cmos]

I can't get this to work at all on my 655. I have tried pretty much everything in this thread. I changed my subnet mask 10 10.0.0.255 (I'm on a 10.x.x.x network) and tried the broadcast address set to 10.0.0.127 and it didn't work. I've checked the connections on the router and it clearly shows an incoming connection on port 9 to the broadcast address but it doesn't wake the PC up. I've checked my BIOS and network card settings over and over and over and made sure all three checkboxes in the Power Management tab of my network card were checked and that it was configured to wake up and that it was set to magic packet. This used to work before on an earlier version of the firmware but does not work anymore and I'm on 1.32NA so I can't downgrade... I think I'm better off selling this thing on E-Bay and getting another with simultaneous dual-band N like a DIR-825 but that may even have the same issue...

Any help getting my 655 to work would be much appreciated!