| View previous topic :: View next topic |
| Author |
Message |
guttersnipe
n00b
Joined: 28 Jun 2007
Posts: 35
|
 Posted: Sun Mar 02, 2008 10:42 am Post subject: WOL over WAN (port forwarding ?) [SOLVED] |
 |
|
Alright, so I've setup my box with WOL. If I run:
| Code: |
guttersnipe@trinity:~$ wakeonlan -i 192.168.1.255 -p 9 00:E0:29:9D:0C:70
Sending magic packet to 192.168.1.255:9 with 00:E0:29:9D:0C:70
|
--OR--
| Code: |
guttersnipe@trinity:~$ wakeonlan -i 192.168.1.0 -p 9 00:E0:29:9D:0C:70
Sending magic packet to 192.168.1.0:9 with 00:E0:29:9D:0C:70
|
...my server turns on. This works great internally, but I don't need WOL because I'm lazy; I need it when I'm off site (ie. I need WOW [wake on wan?])
This is more of a router-related question than a Gentoo question, but I need to forward UDP port 9 to the broadcast. However, my router will only allow me to enter 1-254 in the last octet of the port forward. How do I overcome this obstacle?
FYI, I'm using the eHome EH100 Hardware Version:A1 Firmware Version:1.00
Last edited by guttersnipe on Mon Mar 03, 2008 4:36 am; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Watchman
Joined: 06 Mar 2007
Posts: 6828
|
| Posted: Sun Mar 02, 2008 5:51 pm Post subject: |
|
|
| As an alternative to a Wake-on-WAN approach, could you configure the router so that you can ssh to trinity from a remote location and use that shell to run the wakeonlan command on trinity? |
|
| Back to top |
|
|
guttersnipe
n00b
Joined: 28 Jun 2007
Posts: 35
|
| Posted: Sun Mar 02, 2008 11:31 pm Post subject: |
|
|
Thanks for the response.
| Quote: |
As an alternative to a Wake-on-WAN approach, could you configure the router so that you can ssh to trinity from a remote location and use that shell to run the wakeonlan command on trinity?
|
That's a good idea, but trinity is my laptop. It comes with me. My server is the only computer on that LAN.
Any other ideas? Most computers and NICs have the WOL feature. I can't imagine that routers didn't consider the ability to forward to broadcasts :-/. |
|
| Back to top |
|
|
guttersnipe
n00b
Joined: 28 Jun 2007
Posts: 35
|
| Posted: Mon Mar 03, 2008 4:22 am Post subject: solution |
|
|
http://www.dslreports.com/forum/remark,9624635~mode=flat
It turns out this was just a poor programming call by dLink (the makers of eHome). I changed the subnet mask from <255.255.255.0> to <255.255.255.128>. This effectively changed the gateway from <192.168.1.255> to <192.168.1.127>. I then made the router forward UDP packets over port 9 to the "IP Address" of <192.168.1.127>, and it works beautifully (or shall I say, magically  ).
So, now, I use http://www.remotewakeup.com/en/index.php to remotely turn my computer on from anywhere in the world. I enter the domain name (thank you dyndns), the mac address (yes, you better make sure you've written that down somewhere [gmail]), and the port number (9), and it sends the magic packet to my router, and my router sends it to the broadcast, my server hears the request, and the server boots up.
Hope this helps someone else who runs into this issue. Note to self: don't buy dLink in the future. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
