Wake-on-LAN

[Timothy Murphy]

Has anyone experience with WOL under Fedora?
If so, how exactly do you put the machine to sleep,
and how exactly do you wake it up remotely?

I recently acquired an HP ML110 server (G5 Xeon 3065).
This is said to have Wake-on-LAN capability,
but when I suspend it to RAM I do not seem able
to wake it remotely.

Should one (or can one) suspend to disk for this purpose?


-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: [phone]
s-mail: School of Mathematics, Trinity College Dublin

[Konstantin Svist]

Timothy Murphy wrote:
>  Has anyone experience with WOL under Fedora?
>  If so, how exactly do you put the machine to sleep,
>  and how exactly do you wake it up remotely?
>
>  I recently acquired an HP ML110 server (G5 Xeon 3065).
>  This is said to have Wake-on-LAN capability,
>  but when I suspend it to RAM I do not seem able
>  to wake it remotely.
>
>  Should one (or can one) suspend to disk for this purpose?
>     
The OS doesn't need any support for WOL, all the settings are done in
the BIOS.
Sometimes it's a setting that only says "low power mode" - when it's
enabled, no power is sent to the network card while the computer is
asleep, so no wakeup is possible. A simple way to check is to look at
the NIC while your computer is in sleep - the ethernet connection
light(s) should be on

[Dave Feustel]

On Sun, Apr 05, 2009 at 10:29:30AM -0700, Konstantin Svist wrote:
>  Timothy Murphy wrote:
>  > Has anyone experience with WOL under Fedora?
>  > If so, how exactly do you put the machine to sleep,
>  > and how exactly do you wake it up remotely?
>  >
>  > I recently acquired an HP ML110 server (G5 Xeon 3065).
>  > This is said to have Wake-on-LAN capability,
>  > but when I suspend it to RAM I do not seem able
>  > to wake it remotely.
>  >
>  > Should one (or can one) suspend to disk for this purpose?
>  >   
>  
>  The OS doesn't need any support for WOL, all the settings are done in
>  the BIOS.
>  Sometimes it's a setting that only says "low power mode" - when it's
>  enabled, no power is sent to the network card while the computer is
>  asleep, so no wakeup is possible. A simple way to check is to look at
>  the NIC while your computer is in sleep - the ethernet connection
>  light(s) should be on
>   
Two very knowledgeable people unknown to each other have said that there
was a U.S. law passed in the 1990's that require all computers to
contain circuitry that permits the pc to be undetectedly accessed
remotely via network connections. One of them specifically mentioned
HP computers in this regard. Does anyone at all have any verifiable
info confirming this allegation?

(I know this sounds really paranoid and conspiratorial. Sorry about that.)

Thanks.

[Timothy Murphy]

Dave Feustel wrote:

>  Two very knowledgeable people unknown to each other have said that
> there
>  was a U.S. law passed in the 1990's that require all computers to
>  contain circuitry that permits the pc to be undetectedly accessed
>  remotely via network connections. One of them specifically mentioned
>  HP computers in this regard. Does anyone at all have any verifiable
>  info confirming this allegation? 
I hope this is true!
If the FBI can get into my HP remotely then hopefully so can I.

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: [phone]
s-mail: School of Mathematics, Trinity College Dublin

[Timothy Murphy]

Konstantin Svist wrote:

> > Has anyone experience with WOL under Fedora?
> > If so, how exactly do you put the machine to sleep,
> > and how exactly do you wake it up remotely?
> >
> > I recently acquired an HP ML110 server (G5 Xeon 3065).
> > This is said to have Wake-on-LAN capability,
> > but when I suspend it to RAM I do not seem able
> > to wake it remotely.
> >
> > Should one (or can one) suspend to disk for this purpose? 
>  The OS doesn't need any support for WOL, all the settings are
> done in
>  the BIOS.
>  Sometimes it's a setting that only says "low power mode" - when it's
>  enabled, no power is sent to the network card while the computer is
>  asleep, so no wakeup is possible. A simple way to check is to look at
>  the NIC while your computer is in sleep - the ethernet connection
>  light(s) should be on 
Thanks for the response.

Firstly, I have "Wake on LAN" enabled in the BIOS.

Secondly, rather to my surprise the ethernet light goes off
when I "Hibernate" (I should confess at this point
that I am running Centos-5.3 on this machine,
but thought that I was more likely to get a helpful response
on the Fedora list!)
but stays on when I shutdown.

In neither case does ping or (attempted) ssh have any effect.
How exactly is one meant to "wake from LAN".



-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: [phone]
s-mail: School of Mathematics, Trinity College Dublin

[Sam Sharpe]

2009/4/5 Timothy Murphy <gayleard(a)eircom.net&gt;:
>  Thanks for the response.
>
>  Firstly, I have "Wake on LAN" enabled in the BIOS.
>
>  Secondly, rather to my surprise the ethernet light goes off
>  when I "Hibernate" (I should confess at this point
>  that I am running Centos-5.3 on this machine,
>  but thought that I was more likely to get a helpful response
>  on the Fedora list!)
>  but stays on when I shutdown.
>
>  In neither case does ping or (attempted) ssh have any effect.
>  How exactly is one meant to "wake from LAN". 
One uses Magic Packets.
http://en.wikipedia.org/wiki/Wake-on-LAN

To do this, first install a wol client on another machine to broadcast
the wakeup:
# yum -y install wol

Then read about the options:
http://linux.die.net/man/1/wol

Then one wakes the target machine...

-- 
Sam

[Paulo Cavalcanti]

On Sun, Apr 5, 2009 at 4:39 PM, Sharpe, Sam J <
sam.sharpe+lists.redhat(a)gmail.com <sam.sharpe%2Blists.redhat(a)gmail.com&gt;&gt;wrote:

>  2009/4/5 Timothy Murphy <gayleard(a)eircom.net&gt;:
>  > Thanks for the response.
>  >
>  > Firstly, I have "Wake on LAN" enabled in the BIOS.
>  >
>  > Secondly, rather to my surprise the ethernet light goes off
>  > when I "Hibernate" (I should confess at this point
>  > that I am running Centos-5.3 on this machine,
>  > but thought that I was more likely to get a helpful response
>  > on the Fedora list!)
>  > but stays on when I shutdown.
>  >
>  > In neither case does ping or (attempted) ssh have any effect.
>  > How exactly is one meant to "wake from LAN".
>
>  One uses Magic Packets.
>  http://en.wikipedia.org/wiki/Wake-on-LAN
>
>  To do this, first install a wol client on another machine to broadcast
>  the wakeup:
>  # yum -y install wol
>
>  Then read about the options:
>  http://linux.die.net/man/1/wol
>
>  Then one wakes the target machine...
>
>  
All my Intel mobos with onboard network can be waked up (no need to install
anything, but net-tools):

sudo /sbin/ether-wake ip-addr (wakes computer with ip-addr)

Then, in /etc/ethers, I have the mac addresses associated to IP addresses:

# see man ethers for syntax
# andromeda
XX:XX:XX:XX:XX:XX ip-addr


Never tried with suspend or hibernate. Only when the computer power is off.


-- 
Paulo Roma Cavalcanti
LCG - UFRJ

[Timothy Murphy]

Sharpe, Sam J wrote:

> > How exactly is one meant to "wake from LAN". 
>  One uses Magic Packets.
>  http://en.wikipedia.org/wiki/Wake-on-LAN
>  
>  To do this, first install a wol client on another machine to broadcast
>  the wakeup:
>  # yum -y install wol
>  
>  Then read about the options:
>  http://linux.die.net/man/1/wol
>  
>  Then one wakes the target machine... 
Thanks very much.
That worked perfectly:
----------------------------------------
[tim@mary Download]$ sudo wol 00:24:81:b2:9a:e8
Waking up 00:24:81:b2:9a:e8...
[tim@mary Download]$ ping althea
PING althea (192.168.2.8) 56(84) bytes of data.
64 bytes from althea (192.168.2.8): icmp_seq=1 ttl=64 time=4.72 ms
----------------------------------------

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: [phone]
s-mail: School of Mathematics, Trinity College Dublin

[Tom Horsley]

On Sun, 05 Apr 2009 17:59:57 +0100
Timothy Murphy wrote:

>  Has anyone experience with WOL under Fedora?
>  If so, how exactly do you put the machine to sleep,
>  and how exactly do you wake it up remotely? 
I've never used it to wake from sleep, but I've
found it works fine to power up the system after
a shutdown, with one limitation: Absolutely no
NIC I've ever used that claimed WOL support
has actually worked except for linksys brand
NICs. I have no idea what is different about
linksys and all the others.

[Roberto Ragusa]

Timothy Murphy wrote:
>  Has anyone experience with WOL under Fedora?
>  If so, how exactly do you put the machine to sleep,
>  and how exactly do you wake it up remotely?
>  
>  I recently acquired an HP ML110 server (G5 Xeon 3065).
>  This is said to have Wake-on-LAN capability,
>  but when I suspend it to RAM I do not seem able
>  to wake it remotely.
>  
>  Should one (or can one) suspend to disk for this purpose? 
Wake On LAN should actually be able to wake a system up
from power off state, so it should reasonably work
for suspended systems too.

As a first thing, the NIC LED (or the LED on the ethernet switch)
should be on; it will be on even when the system is switched off,
if WOL is active.

Then WOL has to be enabled. You can trust the BIOS
or, better, run

  ethtool eth0

and you will get something like

  Supports Wake-on: pumbag
  Wake-on: g

which (according to the man page) means WOL on my machine will
respond only on a specific kind of packet.

Last step is sending a proper WOL packet to the machine you want
to wake up (use wol or wakelan). Be sure to use the correct
interface on the waking machine and also try to write the MAC
address with reversed bytes (that is try 11:22:33:44:55:66
and 66:55:44:33:22:11); don't ask me why, but I have two
machines where only the inverted MAC works.

Best regards.
-- 
   Roberto Ragusa    mail at robertoragusa.it

[Timothy Murphy]

Roberto Ragusa wrote:

Thanks very much.

>  Wake On LAN should actually be able to wake a system up
>  from power off state, so it should reasonably work
>  for suspended systems too.
>  
>  As a first thing, the NIC LED (or the LED on the ethernet switch)
>  should be on; it will be on even when the system is switched off,
>  if WOL is active. 
Surprisingly, it is on when I "shutdown -h" the machine,
but off when I set the machine to hibernate.

>  Then WOL has to be enabled. You can trust the BIOS
>  or, better, run
>  
>    ethtool eth0
>  
>  and you will get something like
>  
>    Supports Wake-on: pumbag
>    Wake-on: g 
I had forgotten about ethtool.
I do indeed get "Wake-on: g"
which I see means "Wake on MagicPacket".

So I must see if and hopefully how
I can send the machine a "MagicPacket".

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: [phone]
s-mail: School of Mathematics, Trinity College Dublin

[Anders Rayner-Karlsson]

* Timothy Murphy <gayleard(a)eircom.net&gt; [20090405 22:46]:
>  Roberto Ragusa wrote:
>  
>  Thanks very much.
>  
>  > Wake On LAN should actually be able to wake a system up
>  > from power off state, so it should reasonably work
>  > for suspended systems too.
>  > 
>  > As a first thing, the NIC LED (or the LED on the ethernet switch)
>  > should be on; it will be on even when the system is switched off,
>  > if WOL is active.
>  
>  Surprisingly, it is on when I "shutdown -h" the machine,
>  but off when I set the machine to hibernate. 
That's because the drivers deal with ACPI states S3 and S4 different
to S5.

You *can* wake the system up from S3/S4, but you need to issue a
command first.

# echo -n LAN > /proc/acpi/wakeup

Once you have done this, then you can suspend/hibernate and WOL the
system. The patch for this should be in CentOS 5.3.

Also, different drivers may behave differently in this respect. I only
know of e1000/e1000e behaving correctly with this as I've not tested
it on other hardware.

>  > Then WOL has to be enabled. You can trust the BIOS
>  > or, better, run
>  > 
>  >   ethtool eth0
>  > 
>  > and you will get something like
>  > 
>  >   Supports Wake-on: pumbag
>  >   Wake-on: g
>  
>  I had forgotten about ethtool.
>  I do indeed get "Wake-on: g"
>  which I see means "Wake on MagicPacket".
>  
>  So I must see if and hopefully how
>  I can send the machine a "MagicPacket". 
ether-wake <MAC> is what I used when I did all the testing on
this. It's a tool that generates the exact packet needed.

-- 
Anders Rayner-Karlsson <anders(a)trudheim.co.uk&gt;
All-Round Linux Tinkerer, RHCE and PITA DeLuxe