Cable Forum - View Single Post

sniper007 · 30-12-2011, 00:35

I just want to use the superhub and have WOL work locally. Do not even care for wake on wan events. I personally find that I can get WOL to work locally but my client I want to wake drops off the trusted devices list sometimes which prevents me from waking it. I do not find I need to port forward or anything. It just works...only when it is on trusted device list. If I use a static IP set manually on the client it drops off the trusted device list instantly when turned off. Atleast with superhub reserved IP it stays on there for sometime after being turned off. Would a longer DHCP lease help this do you think or should it be nothing to do with appearing on trusted device list?

Thanks kiwi

---------- Post added at 23:14 ---------- Previous post was at 22:51 ----------

EDIT:

Ok I am confused.

The tool I was using I think I was using it wrongly. I had been using a windows magic packet sending tool called "WOL - Magic Packet Sender" to wake my client LOCALLY on my LAN which gives the following options:

HOSTNAME
SUBNET MASK
MAC ADRESS
PROTOCOL
PORT

I had been using:

HOSTNAME: <my client hostname>
SUBNET MASK: 255.255.255.0
MAC ADRESS: <my client mac address>
PROTOCOL: UDP
PORT: 9

And this had failed each time the client hostname did not show up in trusted devices on superhub IP/MAC filter with it's reserved IP address. I changed to using the actual IP instead of the hostname in the hostname field and it started working. I thought magic packet was only dependent on the MAC used and IP was irrelevant given that when offline it won't be contactable via an IP. I'm confused.

---------- Post added 30-12-2011 at 00:09 ---------- Previous post was 29-12-2011 at 23:14 ----------

I think I had been over complicating it. Anyway... locally it works ok now, but over internet it only works when device is still cached in the trusted device list. So does appear to be when the arp cache is cleared as discussed on community forums.

---------- Post added at 01:35 ---------- Previous post was at 00:09 ----------

I tested some more tonight and even changed my subnet mask to 255.255.255.128 so I could have a broadcast address of 192.168.0.127. The reason is so that the superhub can be told to forward port 9 UDP to the broadcast address on the local network. It does not let you add 192.168.0.255 when you have a subnet of 255.255.255.0 as gives an invalid IP error. With a subnet of 255.255.255.128 you can add 192.168.0.127 and it will let you do this. This is the broadcast address so should give it every chance of working. It still does not.

The only way I can get it working over the internet is by having port 9 UDP forwarded AND the destination client machine to be woken up to appear in the trusted device list on the superhub.

30-12-2011, 00:35	#6
sniper007 Inactive Join Date: Mar 2005 Posts: 480	Re: Superhub Wake on WAN help! I just want to use the superhub and have WOL work locally. Do not even care for wake on wan events. I personally find that I can get WOL to work locally but my client I want to wake drops off the trusted devices list sometimes which prevents me from waking it. I do not find I need to port forward or anything. It just works...only when it is on trusted device list. If I use a static IP set manually on the client it drops off the trusted device list instantly when turned off. Atleast with superhub reserved IP it stays on there for sometime after being turned off. Would a longer DHCP lease help this do you think or should it be nothing to do with appearing on trusted device list? Thanks kiwi ---------- Post added at 23:14 ---------- Previous post was at 22:51 ---------- EDIT: Ok I am confused. The tool I was using I think I was using it wrongly. I had been using a windows magic packet sending tool called "WOL - Magic Packet Sender" to wake my client LOCALLY on my LAN which gives the following options: HOSTNAME SUBNET MASK MAC ADRESS PROTOCOL PORT I had been using: HOSTNAME: <my client hostname> SUBNET MASK: 255.255.255.0 MAC ADRESS: <my client mac address> PROTOCOL: UDP PORT: 9 And this had failed each time the client hostname did not show up in trusted devices on superhub IP/MAC filter with it's reserved IP address. I changed to using the actual IP instead of the hostname in the hostname field and it started working. I thought magic packet was only dependent on the MAC used and IP was irrelevant given that when offline it won't be contactable via an IP. I'm confused. ---------- Post added 30-12-2011 at 00:09 ---------- Previous post was 29-12-2011 at 23:14 ---------- I think I had been over complicating it. Anyway... locally it works ok now, but over internet it only works when device is still cached in the trusted device list. So does appear to be when the arp cache is cleared as discussed on community forums. ---------- Post added at 01:35 ---------- Previous post was at 00:09 ---------- I tested some more tonight and even changed my subnet mask to 255.255.255.128 so I could have a broadcast address of 192.168.0.127. The reason is so that the superhub can be told to forward port 9 UDP to the broadcast address on the local network. It does not let you add 192.168.0.255 when you have a subnet of 255.255.255.0 as gives an invalid IP error. With a subnet of 255.255.255.128 you can add 192.168.0.127 and it will let you do this. This is the broadcast address so should give it every chance of working. It still does not. The only way I can get it working over the internet is by having port 9 UDP forwarded AND the destination client machine to be woken up to appear in the trusted device list on the superhub.