Hi,

I couldn't find any instructions how to use e.g. ether-wake to wake up my server over the internet. The command expects only a MAC address.

Any ideas?

Thanks,
Matthias

Hi

ether-wake and others need a MAC address cause this must appear in the "magic packet" they will send, i think you can find more info about this on wikipedia (search for WakeOnLan & WakeOnWan)

to find out what's the MAC address of your server, take a look over its network config (with a "ifconfig eth0", for example)

be aware that if connect your server via a router, you cannot wake your server over the internet unless your router can be a WOL proxy. This means that your router must be configured to automatically forward the magic packet to your server, otherwise your server will not wake over the internet (but this will work inside your LAN, if you have one)

hope this helps,
if my explications aren't clear, so don't hesitate to tell me.

Hi,

a friend of mine sent me this link: http://www.dslreports.com/faq/6790

To use WOL over the internet, you will have to forward UDP port 9 to the broadcast address of your local subnet. Because any requests incoming on port 9 are broadcasted, each client in the network (including the server) will receive the UDP packet and inspect the ARP frame it is wrapping. The MAC in the ARP packet then only matches that of the server, and the server's NIC can interpret the WOL request.

This is how it's supposed to work. However, I am not sure if my router allows me to forward ports to a broadcast address. Gotta check that out when I'm back home.

Oh and, of course you need a tool other than ether-wake, because ether-wake cannot send the WOL magic packet as a UDP packet to a designated host. It's ethernet-only. There are programs, scripts and even website that do this however (e.g. http://www.dslreports.com/wakeup).

i can see you know the drill

can't remember properly of ether-wake, but there are programs (like wake-on-lan), which create directly the UDP magic packet
or, as you said, there are websites that allow people to send this packet

the port 9 is a standard for this use, however you can choose any which is more comfortable for you (the port number is only used by the OS, and at this state, there is no OS running yet). So in conclusion what you have to check is if your router support WOW...

mine, for example, doesn't () because it considers that for a packet to be forwarded, there must be a service running behind the scene, listenning to the port the packet is designed to. In the WOW case, there isn't such a service cause there isn't any software running behind the router (this is the point of Wake On Wan, after all)...so even if i can make a rule that forwards packets from port 9 to local broadcast, the router doesn't forward the packet cause it can't see any service listening to this port (dummy thing...)

good luck with yours