Print

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

[dtalwar]

Has anyone been able to use WOL over the Internet with DIR-655 1.33NA? It used to work flawlessly for me with 1.21. Sending a packet to a broadcast address seems to be broken in 1.33NA. I would appreciate any suggestions or ideas that you all good folks in the forum may have to offer.

[cmosq]

I've been trying for a while too on the same 1.33NA FW with no luck. I'm on a 10.0.0.x subnet forwarding the UDP packets 7 and 9 to 10.0.0.255 in the virtual server page with no luck whatsoever. I'm very close to getting ticked off and selling the thing on ebay and get another router with "known working" WOL. It probably will NOT be a Dlink because I don't know if other units like the 855 will have the same problem as the 655...


Can someone please help?

[dirkpitt]

Sounds like you need an invite to:

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

[rlcronin]

So, go to the Virtual Servers section of the DIR-655's Advanced tab. Create an entry called Wake-On-LAN-9 (just to be descriptive, the actual name doesn't matter, call it Bob if you like). Assuming you use the subnet 192.168.0.xxx, specify 192.168.0.255 as the IP address. Set the public and private port to 9 and the port type to UDP. Make sure you put a checkmark in the checkbox to the left and the click Save Settings.

If you want to use port 7 instead, substitute 7 for 9 in the above description. I use 9 because that's what the WOL tool at BroadbandReports uses.

Also be sure to have enabled WOL in the properties of your network adapter. For Windows 7, go to ControlPanel->NetworkandInternet->NetworkandSharingCenter->ChangeAdapterSettings. Right click the icon for the primary network adapter and choose Properties. Click the Configure button. Select the PowerManagement tab and make sure there are checkmarks next to "Allow this device to wake the computer" and "Only allow a magic packet to wake the computer".

Then be sure that PC is sleeping and not totally off (although some systems support waking from a totally-off state, check your BIOS for such a setting if you want/need to do that).

Then use your web-based tool of choice to send the WOL signal to your public IP address (check what it is at whatismyip.com if you don't already know how to figure it out), specifying the MAC address of the PC that you want to wake up. You can determine that from the list of DHCP clients on the Network Setup section of the DIR-655's Setup tab. Or if it is a Windows box, just use ipconfig /all from a command prompt and copy down the value it lists for physical address of the primary network adapter.

This works fine for me with my DIR-655 A3 with FW 1.33NA.

If it is not working it can be helpful to turn on every type of log message on the Logs section of the DIR-655's Status tab. Send the WOL signal and if it does not work, check the logs to see if it was received or not, possibly blocked, etc. and take corrective action based on what you find. Do the same for any software firewall you might be running.

Best of luck to you.

[cmosq]

LOL on the invite. 

[cmosq]

I have previously done everything that you've stated below except that in my case, the subnet is 10.0.0.x so my broadcast address is 10.0.0.255... Let's eliminate the computer from the picture because I can get it to wake up remotely just fine when using just the dsl modem without the DIR-655 attached. I've take your comments to light and will enable the logs. I'll also try changing it to the 192.168.0.xxx subnet like pretty much everyone else here as well as trying to reset it to the factory config... Thanks for your help and if anyone else can chime in then great!

[dtalwar]

Ditto here ... have the same settings (as rlcronin describes), with A3 and 1.33NA, was not able to use WOL over the Internet to wake up the server. Went back to 1.21 and it is working again.

[cmosq]

I tried to downgrade but it didnt let me. How did you do it?

[dtalwar]

I followed the instructions as described in http://forums.dlink.com/index.php?topic=10668.0.

[cmosq]

Thanks I was able to downgrade. It's still not working so that is obviously not the case.  This used to work just fine some time ago when I first bought the 655 and was running an older version.

Quick question: will the magic packet get to the pc if the pc is not directly attached to one of the LAN ports on the router and is instead attached to a gigabit switch which is then attached to one of the LAN ports on the 655... See the diagram below:

netopia 2241vgn dsl modem > dir655 wan port
dir 655 LAN port > gigabit switch > pc

I'm certainly going to try this when I'm near the pc again.

 

[rlcronin]

As long as the target PC is on the same subnet, it should get there fine.

Have you enabled your logs and looked to see if the packet is arriving from the Internet and being blocked somehow?

[astehn]

Can anyone confirm which firmware versions will actually forward magic packets to the broadcast address?

I'm on 1.22b5 and I can see the magic packets show up using a WOL packet sniffer, provided that I set up a port forwarding rule to go directly to the IP address of the computer I'm trying to wake. More specifically:
Internet-->NAT (172.27.35.10:9)-->PC IP (192.168.10.103:9).
Obviously, this won't work as soon as the PC drops out of the ARP.

So if I change the forwarding rule to the broadcast address, like this:
Internet-->NAT (172.27.35.10:9)-->brodcast IP (192.168.10.255:9).
The activity still shows up in Internet Sessions, but my packet sniffer never shows the PC receiving the magic packet. So although it APPEARS that the firmware will allow a port forward to the broadcast address, it doesn't seem to actually pass the magic packet through.

[dtalwar]

I am on 1.21 (w/ H/W version A3) and it works fine for me. I have an entry in the Virtual Server page that forwards incoming packets on port 9 to the subnet broadcast address.

[cmosq]

Not for me. I tried 1.11, 1.21 and 1.33NA... Just so you all know if I connect the pc directly to the Ethernet port of my netopia 2241 dsl modem and the pc wakes just fine.

[dtalwar]

A couple of things to think about:

1) Are you able to wake up the computer over LAN?
2) Are you using your modem's WAN IP address when you send the magic packet over the Internet?
3) Did you try the 192.168.x.x instead of the 10.0.x.x?