Print

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

[seipher]

Hey fellow nerds,

So I just picked this unit up a day or 2 ago and it seems to be working quite well so far. I was interested in being able to use the wake on lan feature that my PC has. I am able to get it up under LAN but not WAN. Another words when I am connected to the router with another PC I can send a magic packet and wake up my gaming PC. However, if I connect to a different network I can not seem to send the packet through my router and turn on my PC.

I have spent pretty much the entire afternoon working with settings. I know that my PC is ready to be woke up or I wouldn't be able to do it localy. I just can't seem to figure out how to send the Magic Packet through the router's firewall. I have tried using "virtual server" settings with port 9 and "Gaming" (Port Forwarding) settings using port 9.

Has anyone successfuly got this to work?

Thanks,

Seipher

[HankRiker]

So I just picked this unit up a day or 2 ago and it seems to be working quite well so far. I was interested in being able to use the wake on lan feature that my PC has. I am able to get it up under LAN but not WAN. Another words when I am connected to the router with another PC I can send a magic packet and wake up my gaming PC. However, if I connect to a different network I can not seem to send the packet through my router and turn on my PC.

I have spent pretty much the entire afternoon working with settings. I know that my PC is ready to be woke up or I wouldn't be able to do it locally. I just can't seem to figure out how to send the Magic Packet through the router's firewall. I have tried using "virtual server" settings with port 9 and "Gaming" (Port Forwarding) settings using port 9.

Has anyone successfully got this to work?

If by WAN you mean the Internet, it's possible, but in my experience it's very unreliable. The problem is getting the magic packet to arrive intact so as to trigger the Waking process.

If you're saying that you are using several subnets, other than a properly configured bridge, I don't see any easy way of communicating the WOL packet to the machine you want to wake.

I use WOL across my network, with a number of machines with no issue. Even with machines on different subnets. It's just that the Magic packet needs to be sent from a machine on the same subnet as the machine you're trying to wake. It is possible to directly send a packet from one subnet to another, but I don't have any experience doing so... Maybe someone else here does?

Either way, tell us more about your configuration. It might help.

Hank

[seipher]

I did use WAN (Wide area network) for internet as that is my understanding of what it means. Simply put, I would like to send the magic packet from work to home and wake up my PC at home so I can log into it remotely. This way I don't have to leave it on all day long while I am at work. So it would be sent from 1 subnet to another as you put it. This should be very possible as it is an option on most all of the WOL magic packet sender softwares you download or use. It is also an option under the D-Link 4500 if you look at Advanced > Virtual Server >... You can chose Wake On Lan and it will automaticaly fill the public and local ports 9 for you. I aslo set up a DynDNS so that I can use that to always find my location.

So from outside of my network I should be able to enter:

Host / IP =  xxxxxxxx.homedns.org
Mac = xx.xx.xx.xx.xx
Port = 9


and get my PC to kick on. Doesn't work though.

[HankRiker]

I did use WAN (Wide area network) for internet as that is my understanding of what it means. Simply put, I would like to send the magic packet from work to home and wake up my PC at home so I can log into it remotely. This way I don't have to leave it on all day long while I am at work. So it would be sent from 1 subnet to another as you put it. This should be very possible as it is an option on most all of the WOL magic packet sender softwares you download or use. It is also an option under the D-Link 4500 if you look at Advanced > Virtual Server >... You can chose Wake On Lan and it will automaticaly fill the public and local ports 9 for you. I aslo set up a DynDNS so that I can use that to always find my location.

So from outside of my network I should be able to enter:

Host / IP =  xxxxxxxx.homedns.org
Mac = xx.xx.xx.xx.xx
Port = 9


and get my PC to kick on. Doesn't work though.

What are you using to transmit the Magic packet?

I've not tried it, but there is this available:
http://www.depicus.com/wake-on-lan/woli.aspx

http://www.ezlan.net/WOL.html

Subnet issues usually refer to dealing with different subnets locally, so that's not your issue. It could be a packet loss issue though, one thing I saw recommended was to repeat the Magic Packet sending at a high rate, with the idea that eventually the whole packet will get thru and trigger the process.

Some other interesting info to consider:
http://www.dslreports.com/faq/6790

I just thought of something else. Could your office or home ISP be blocking traffic over port 9? If so, you can pick a random high-number port, then have it translate in the router from that port, to port 9 internally. Also, you only need UDP, not TCP.

Hope this helps,
Hank

[MoToR]

Hi all.

I'm facing difficulties with DGL-4500 and WOL as well.

I've recently added a NAS to my home network and I'm trying to gain a capability to turn it on and off remotely.

At this moment I can wake the NAS up from anywhere within my LAN which includes bridged virtual network (i.e. from VMware guest OSes), but I can't wake it up over the internet.

For testing purposes my laptop is connected to a neighbour public WiFi and runs both mc-wol tool (port 65535) and WakeOnLANGUI tool (port 9, configurable).

The best result I got was seing a message "Wake-on-LAN ALG rejected packet from X.X.X.X:X to X.X.X.X:65535" in the log of my DGL-4500. This happens when I use Advanced->Virtual Server page to create a forwarding rule. If I disable this rule and create one on the Advanced->Gaming page - the log shows nothing and yet the NAS doesn't wake up.

Assuming the packets arrive to DGL-4500 from outside, please suggest how should I configure my router in order to have my NAS receive the WOL packets and wake up?

The funny thing is I saw the WOL option in ALG section of Advanced->Firewall page of DIR-655 firmware. I stumbled upon it during gooling for a solution to my problem. ALG section is said to take care of the "special" packets, why does DGL-4500's firmware lacks WOL on it's Advanced->Firewall page? Is there another way it (DGL-4500) handles WOL magic packets?

Any help/ideas will be highly appreciated.

Thanks in advance,
MoToR.

[HankRiker]

Hi all.

I'm facing difficulties with DGL-4500 and WOL as well.

I've recently added a NAS to my home network and I'm trying to gain a capability to turn it on and off remotely.

...cut...

Any help/ideas will be highly appreciated.

Thanks in advance,
MoToR.

Hello MoToR,

I decided to sit down and test this out for myself.

This post is assuming that you've testing the NAS locally, to insure you can wake it. Heh.

Go into the DGL-4500 Advanced / Virtual Server page.

Click the "Application Name" listbox and choose Wake-On-LAN. Click "Computer Name" and choose the computer you want to wake. Check enable, and click Add.

Give it a minute and you should see a new rule.

In your WOL application, add your IP address as the host name. Enter a subnet mask of 0.0.0.0. Enter the MAC address of the NAS. Choose UDP as your protocol. Make sure you're using port 9. Hit the send button. Your NAS should wake.

I was able to do this successfully with both: http://magicpacket.free.fr/ and ezShare http://itunes.apple.com/us/app/ezshare-pro/id301589535?mt=8 for the iPhone. The former is free, and there is a free version of the latter, but I didn't test it, just the paid version.

I tested this twice (once from each) to make certain it was working correctly.

Hope this helps,
Hank

[MoToR]

HankRiker, thanks for your reply and for your help,

I made some progress since my last post, but the problem stays partly unresolved. I succeeded to wake my NAS up over the internet only via Port 9 and using Advanced->Virtual Server->WOL rule, but I had to enter the broadcasting address there to make it work. The specific NAS IP didn't do the job, only the X.X.X.255 did.

What is still unresolved:

- Why should the rule be broadcasting on the local network, why doesn't specific IP rule work?
- Advanced->Gaming page forwarding rules doesn't seem to work with WOL for my NAS, any ideas what's different in this kind of forwarding?
- Changing the port to 65535 at the Advanced->Virtual Server page causes router to reject the magic packets denying the use of mc-wol command line tool, which is the only way I know to wake up the NAS with a double-click.

[HankRiker]

HankRiker, thanks for your reply and for your help,

You're quite welcome. I've been curious about the process myself, and I have worked to make all of the hardware in my network capable of being woken from power-off and then being put back to sleep after I'm done with the devices.

I made some progress since my last post, but the problem stays partly unresolved. I succeeded to wake my NAS up over the internet only via Port 9 and using Advanced->Virtual Server->WOL rule, but I had to enter the broadcasting address there to make it work. The specific NAS IP didn't do the job, only the X.X.X.255 did.

What is still unresolved:

- Why should the rule be broadcasting on the local network, why doesn't specific IP rule work?
- Advanced->Gaming page forwarding rules doesn't seem to work with WOL for my NAS, any ideas what's different in this kind of forwarding?
- Changing the port to 65535 at the Advanced->Virtual Server page causes router to reject the magic packets denying the use of mc-wol command line tool, which is the only way I know to wake up the NAS with a double-click.

It can be confusing, but each tab has it's own purpose.

Things like WOL need the listen server model, so you use the Virtual Server tab. If you just need to open ports to a specific machine for input and output, where your machine initiates the connection, then you use the Gaming tab.

As far as your other questions, perhaps re-read my last posting? I tried to be very clear on the process. You need to use a Virtual Server entry, to forward the packets coming to port 9 to the IP address of your NAS. If you're saying something other than that, I think I'm mis-understanding what you're saying.

Hope that helps,
Hank

[MoToR]

Hi, thanks again for your reply,
I'm away from home at this moment and I feel like I need to do some more tests in order to understand exactly what works and what doesn't.

What I know from my previous test is that I could wake up my NAS only if I created a Wake-on-LAN rule using Advanced->Virtual Server tab with Port 9 and IP 192.168.1.255, which is a broadcasting IP. The specific NAS IP didn't work. Any port other than the default 9 didn't work.

I'll continue testing and write back when I have a more complete picture.

[HankRiker]

Hi, thanks again for your reply,
I'm away from home at this moment and I feel like I need to do some more tests in order to understand exactly what works and what doesn't.

What I know from my previous test is that I could wake up my NAS only if I created a Wake-on-LAN rule using Advanced->Virtual Server tab with Port 9 and IP 192.168.1.255, which is a broadcasting IP. The specific NAS IP didn't work. Any port other than the default 9 didn't work.

Well, you would need to configure what port your NAS was listening for, which it may not allow you to do. UDP port 9 as well as occasionally 7 or 0 seem to be the industry standard, so I don't see why you'd need to change that, but if you have SSH access on the device and are comfortable with appliance hacking, you could change the necessary configuration files.

As far as the NAS IP address not working? That's very odd. So, you are pointing the Virtual Server entry at 192.168.1.255, and the device is actually at another IP address, and it's waking? So for the sake of argument say the device is at 192.168.1.200? That really shouldn't work unless 192.168.1.255 is your "broadcast address".

If 192.168.1.255 is configured as a broadcast address, then that makes sense, as all traffic directed to a broadcast address should be echoed to all of the addresses on a subnet, although I haven't tested that.

Hank