Differences between version 2 and previous revision of WakeOnLanNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Wednesday, September 15, 2004 3:25:04 pm | by AristotlePagaltzis | Revert |
| Older page: | version 1 | Last edited on Saturday, September 4, 2004 10:33:35 pm | by DanielLawson | Revert |
@@ -1,43 +1,49 @@
+Prerequisites for WakeOnLan:
-For
WakeOnLan to work, you need
the following items:
+* A motherboard aware of resume on ring events
+* A [NIC] with
WakeOnLan support
+* Possibly a cable connecting the [NIC]
to the [WOL] header on your motherboard (unless it's an onboard [NIC])
-* A motherboard which supports resume on ring events
-* A network card which suppots WakeOnLan
-* Possibly a cable connecting your network card
to the WOL header on your motherboard (unless it
's an onboard
NIC)
+You will need
to enable WakeOnLan in
the machine
's [BIOS], and you will need to know the [
NIC]'s [MAC] address.
-You will need to enable WOL in the
machine's BIOS, and
you will need
to know
the ethernet card's
[MAC
] address.
+From another
machine you can then use [ether-wake | http://www.scyld.com/wakeonlan.html]
to send
the special
[Ethernet
] frame:
-Then, (from another machine) you can use the
ether-wake package to send the special ethernet frame.
-On debian: apt-get -u install etherwake.
+<pre>
+$
ether-wake ''$[MAC]ADDRESS''
+</pre>
-Then from the command line,
you can do
- $ ether-wake
<macaddress
>
+If
you add an entry mapping [MAC] addresses to hostnames to
<tt
>/etc/ethers</tt>, you will also be able to simply say
-Or you can add an entry to /etc/ethers with macaddress to hostname entries and just do
- $ ether-wake <hostname>
-(Note that the version of etherwake in [Debian] [Woody] doesn't seem to support this)
+<pre>
+$ ether-wake <hostname>
+</pre>
-----
+Pre
-compiled packages of <tt>ether
-wake</tt> exist for most LinuxDistribution~s. In [Debian], it's called <tt>etherwake</tt>, but the version available in [Woody] doesn't seem to support <tt>/etc/ethers</tt>.
-Some network card
drivers seem to disable the WOL ability
of a
network card. If you can use WOL just
after you've booted
into Windows, but not at all after you've booted
into Linux, this
probably applies
.
+Some [Linux] [NIC]
drivers seem to disable the WakeOnLan function
of the
network card. If you can use WakeOnLan
after booting
into Windows, but not at all after booting
into Linux, your driver is
probably one of them
. [ethtool | http://gkernel.sf.net/] allows you to change this. An initial query of an interface's properties will look something like this:
-There is a program called [
ethtool|http
://gkernel
.sf.net/] which you
can use to fix
this. It'll need to be applied every boot, so stick it in rc.local or somewhere.
+<verbatim>
+$
ethtool eth0
+Settings for eth0
:
+ Supports Wake-on: g
+ Wake-on: d
+ Link detected: yes
+<
/verbatim>
+
+Here, MagicPacket (type g) WakeOnLan support is available but disabled (Wake-on: d)
. You
can change
this with a swift
<verbatim>
-
ethtool eth0
- Settings for eth0:
- Supports Wake-on:
g
- Wake-on: d
- Link detected: yes
+$
ethtool -s
eth0 wol
g
</verbatim>
-This shows that it supports MagicPacket WakeOnLan (type g)
, but it is disabled at
the moment (Wake-on: d). You can fix
this by running
+This time
, a query to confirm
the result should produce something like
this output:
<verbatim>
- ethtool -s eth0 wol g
-
ethtool eth0
- Settings for eth0:
-
Supports Wake-on: g
-
Wake-on: g
-
Link detected: yes
+$
ethtool eth0
+Settings for eth0:
+
Supports Wake-on: g
+
Wake-on: g
+
Link detected: yes
</verbatim>
+
+Note that you'll need to change the setting anew on every boot, so stick the command in <tt>rc.local</tt> or whichever boot script is applicable.
