Matthew Bailey wrote:
> Is it possible to get Wake On Lan to work through a netgear DG834
> router connected to the internet via ADSL?
>
> I can successfull send "Magic Packets" to the computer from another PC
> on my lan, but I can't get them to go through the router.
>
> I have tried different different options with regards to port
> forwarding on the router, but it doesn't do anything.
>
> Done anyone have this working?
Not as such -- I don't need to, as I can make a VPN connection to my
router, make a VNC connection to a machine which is always on, and run a
waker-upper on it awake any other machine.
I did investigate, and came to a few conclusions and made a few notes.
Whether you can WOL a NATted machine over the Internet depends amongst
other things on the hardware used. I append some details for some
routers.
Some of the Draytek Vigor routers with latest firmware, in particular,
support WOL in two ways. You must set up the router so you can Telnet to
it; then use a Telnet command to wake up a NIC with a specified MAC
address. If you had a Vigor router I would recommend you look on the
support forums.
From my notes (which may have been edited, I don't remember):
http://www.dslreports.com/faq/6790
Notes:
- the approach discussed here can work only if the router supports
directed broadcasts
("Subnet Directed Broadcast", "directed enabled", "forward Directed
Broadcast")
- WOL won't work on a computer which hasn't been booted since it was
plugged in.
Q: WoL (Wake on LAN) through NAT (#6790)
A: This text assumes the reader will be using a computer
(motherboard and BIOS) and NIC (network card) that are compatible with
WoL technology and that the hardware is properly set up to do so. Some
network cards must be placed into a special PCI slot on the motherboard
in order work properly while others must be tethered to the motherboard
by a special cable which plugs into a particular place on both the
motherboard and the NIC. A general WoL FAQ can be located here. This
text was written mainly to indicate how to forward the proper port
through a Linksys router in order to utilize WoL technology through the
router.
In order to use WoL (Wake on LAN, aka: RWU or remote wake up) to
wake up a computer from over the Internet the appropriate port needs to
be forwarded from the WAN side to the LAN side of the router. Since a
computer that is not turned on doesn't have an IP address, the packet
sent to wake the computer needs to be forwarded to all computers on the
LAN side of the router in order to ensure it gets to the computer it is
destined for. This "magic packet," which can be sent using software
available from different sources, contains a special string designed to
work with WoL as well as the MAC address of the network card in the
computer which should wake up. Because the MAC address of the correct
machine is included in the packet, only the machine that is supposed to
wake up actually will.
To set up port forwarding in the router go here (default). The
port that needs to be forwarded will vary depending on what software
you're using to send the magic packet, but the normal port used for WoL
is 9. UDP is the protocol that needs to be forwarded; it is not
necessary to forward the TCP protocol. The IP address that the packet
needs to be forwarded to will change depending on the network mask you
are using on your LAN. The default network mask is 255.255.255.0. If you
are using this mask, you should forward traffic destined to your WoL
port to xxx.xxx.xxx.255. If you are using the default settings in the
router, this address would probably be 192.168.1.255. The 255 in the
address, using the default network mask, signifies that the router
should forward any information sent to the indicated port to all
computers on the LAN side. If you are using the router's default
settings with a program that sends the "magic packet" to port 9,
basically just forward all UDP traffic on port 9 to 192.168.1.255. If
there is an option for external and internal ports, the same port number
should be used for both external and internal.
WoL tool allows you to wake a computer remotely over the Internet
through a browser. On this page they indicate UDP port 9 is what the
tool uses, but as of this writing the magic packet is actually sent
through UDP port 32767. So, if you're using this tool be sure to forward
port 32767 through the router.
While it is possible to locate software that will send WoL "magic
packets" via a quick search in your favorite search engine, a couple of
sites offering such software are:
Depicus (also provides info on WoL)
AMD (also provides info on WoL)
by Gork edited by Lanik
---------------------------------------------------------------
From: glen herrmannsfeldt ((E-Mail Removed))
Subject: Re: WOL Magic Packet fails over VPN
Newsgroups: comp.dcom.lans.ethernet, comp.protocols.tcp-ip
Date: 2004-02-02 11:46:35 PST
Fernando Gont wrote:
>>It might work if you send a subnet broadcast packet with the
appropriate
>>MAC address in the data portion of the packet. That is, the ethernet
>>destination will be a broadcast address, but the packet contents will
>>have the desired MAC address to be matched by the NIC.
> Sorry?
Directed broadcast are a questionable feature of IP, which is why
I added the tcp-ip group onto the list. It is especially
complicated if you are using NAT.
If your host is addressed a.b.c.d, and subnet mask 255.255.255.0, then
the subnet broadcast address is a.b.c.255. A packet sent to that
address should come out of the last router as an ethernet broadcast.
For a NAT implementation, it might be that you can add the subnet
broadcast address and appropriate port to the incoming port forward
list, though I don't know how many NAT implementations will do that.
It might be easier to find something that will do static ARP.
You could even have one machine on the net with a static published
ARP entry for the ethernet broadcast address.
If you randomly choose the port forwarding port number you reduce the
chance of an attack on your net by someone guessing the port.
-- glen
================================================== ===========
From: Steven Kan ((E-Mail Removed))
Subject: Re: Airport wake-on-lan - UDP trouble
Newsgroups: comp.sys.mac.system
Date: 2002-07-12 17:53:59 PST
I have done this through my Linksys BEFSR41 router with port forwarding.
The trick for me was forwarding external UDP port 2304 to the internal
broadcast address 255.255.255.255. Works great!
If the ABS doesn't support UDP forwarding, you may have to go with a
different router.
HTH,
--
Michael Salem
Similar Threads
Linear Mode
