-
HOWTO: Set your system up for Wake On LAN (WOL)
This is really common, but I haven't seen a ubuntu howto for it, people more or less peice it together from posts and blog entries and the like.
So, here it goes. First off, make sure your system supports WakeOnLAN (WOL), if you know your system well, you already know if it does or doesn't.
--
Automatic way:
This script does everything described in the Manual way, for you, except step 1 and step 4.
------------------------
The automatic method is super dialup friendly! thanks to gzip compression the filesize is a mere 1.5kb! almost half the extracted size of 3.4kb! :wink:
1. If you havent already, go to your BIOS, and turn on WakeOnLAN (it varies, look for it.) If your network card is onboard, your set for step 2, otherwise there is probably a cable that should go from your network card to your motherboard, though this is not always the case.
Before continuing, note the interface you want to do this to. Most people know how to do this, if you do not, look at step 2a of the manual method.
2. Download and extract this: You can do it with the GUI and run the extracted program in a terminal by double clicking it, or open a terminal and do the following:
**** Removed dead link ****
3. As the exit of the program notes, now you just need to get/use a wake on lan sending program, like wakeonlan.
4. Sit on your lazy *** and have fun :)
--
Manual way:
------------------------
1. If you havent already, go to your BIOS, and turn on WakeOnLAN (it varies, look for it.) If your network card is onboard, your set for step 2, otherwise there is probably a cable that should go from your network card to your motherboard, though this is not always the case.
2. Back in ubuntu, kubuntu, xubuntu, w/e, we now need to make a script that will run every time the computer is started, because this command only lasts until the computer is turned on again once.
2a. Find out what network device you want to have the computer wake-able from, usually all, which is just one. If you have more network devices in your system, 9 chances out of 10, you already know what they are called.
You can NOT wake up a laptop or computer that is only connected via wireless with wake-on-lan, unless the bios has a method for this, this is very rare, and I do not garuntee this howto will work in such cases.
In your terminal, type:
You'll get something like: (I have removed my mac address for security)
Code:
eth0 Link encap:Ethernet HWaddr 01:23:45:67:89:ab
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:f2ff:fe6f:3487/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:71495 errors:0 dropped:0 overruns:0 frame:0
TX packets:76190 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23164212 (22.0 MiB) TX bytes:7625016 (7.2 MiB)
Interrupt:217 Base address:0xd400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1290 errors:0 dropped:0 overruns:0 frame:0
TX packets:1290 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:161182 (157.4 KiB) TX bytes:161182 (157.4 KiB)
So, I want this system to be wake-able from eth0.
2b. Now we create the script.
Note: you must be an administrator on the system you are doing this to.
Enter your password at the prompt.
Change to the startup script directory and start editing a new file:
Code:
cd /etc/init.d/
pico wakeonlanconfig
Paste, or type this into the file, replacing eth0 with your network device, repeat the ethtool line as many times for your devices before the exit line:
Code:
#!/bin/bash
ethtool -s eth0 wol g
exit
Set the permissions of the file:
Code:
chmod a+x wakeonlanconfig
Make the script run on startup:
Code:
update-rc.d -f wakeonlanconfig defaults
You should see something like:
Code:
Adding system startup for /etc/init.d/wakeonlanconfig ...
/etc/rc0.d/K20wakeonlanconfig -> ../init.d/wakeonlanconfig
/etc/rc1.d/K20wakeonlanconfig -> ../init.d/wakeonlanconfig
/etc/rc6.d/K20wakeonlanconfig -> ../init.d/wakeonlanconfig
/etc/rc2.d/S20wakeonlanconfig -> ../init.d/wakeonlanconfig
/etc/rc3.d/S20wakeonlanconfig -> ../init.d/wakeonlanconfig
/etc/rc4.d/S20wakeonlanconfig -> ../init.d/wakeonlanconfig
/etc/rc5.d/S20wakeonlanconfig -> ../init.d/wakeonlanconfig
Now we finish by running it, and making sure there are no errors.
Code:
/etc/init.d/wakeonlanconfig
This should produce no output and put you right back at the prompt you started at.
3. Use it. you'll need something to send wake-on-lan packets with, "wakeonlan" is in the repos. And you'll need the mac address of the system.
To get your MAC address, on the same system you just enabled WOL on, type:
its the thing that looks like 01:23:45:67:89:ab , write it down.
turn off that system:
if your using wakeonlan from the repos, and you are on the same network as the computer your tying to wake up, replace 01:23:45:67:89:ab with your mac address and do, from another computer:
Code:
wakeonlan 01:23:45:67:89:ab
In MOST cases, you CAN SEND wake on lan packets from a wireless connected computer.
If that doesnt work, its likely the port on the system your trying to wake up isnt the default (9), try 7, or if your BIOS settings or book told you one, use that one.
Code:
wakeonlan -p 7 01:23:45:67:89:ab
If that STILL doesnt work, make sure wakeonlan is enabled in your bios and your hardware supports it.
*Note: It has been said that you need to disable -i from halt, however I have never had to do this, nor do I know how.
4. Sit on your lazy *** and have fun :)
Feel free to post any questions, suggestions, problems and I will tend to them ASAP.
Added notes:
* For this to work, most systems must be shut down properly, ie: with the power button or halt, or any of the ways to shut down. Unclean power-offs (like a power outage or holding the power button for 5s) seem to stop WOL from working untill the system is powered on and shut down properly. Though, there my be a few exceptions. This is a hardware issue with the BIOS. In my opinion, WOL should work regardless of how the system is powered off, but thats not the case. I suggest, if you have frequent power outages, that you have your BIOS set to Power ON after a power failure, most new systems allow this.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Many Thanks Chris, for this clear explanation. It saved me a lot of time.. I am very new to Linux, and already found how that the ethtool wol settings aren't persisted, but I didn't figure out yet how to make my system remember them.
The only problem I now have is: my computer wakes up within a minute after shutting down. Something wakes it up (which gives me hope that WOL *is* actually working on my system) but I want it to start up only if *I* send a magic package of course! I did set the wol setting to: g.
Do you have any idea what could be causing this? In the mean time, I am going to check my bios settings..
Cheers
Hans
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Yep! It works! The problem was in the BIOS settings. I set the Wake on PCI Card setting to Yes, and disabled the Wake on PCI Master (which was probably causing the computer to start up too soon)
BTW I start my Ubuntu box from a Windows XP system using the Magic Packet Sender utility (http://magicpacket.free.fr/) that's connected via a wireless network. It works like a charm.
Thanks again,
Hans
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hm, the wake on pci thing could be what puzzled me about some systems i came across before.... i thought there was a wakeonlan thing going on, because within 1 hour, about 3 computers in a lab where i worked would randomly turn on if you turned them off... puzzled the hell out of me.
thanks, and have fun being lazy ;P
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Automated script now available. Currently only supports 1 interface, more means manual. Version 1.0 of the script should be up within 48 hours that supports multiple interfaces.
enjoy :D
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
How do I wake on WAN my pc? I've tried wakeonlan within my network, but I can't access it outside my network.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
if you use the command "wakeonlan" without the -p option, then use your router to forward port 9 UDP to the computer on the internal network... not sure how well this works with a router, as when a computer is off, it doesnt have an IP to forward to! after that, you'll need a utility that sends the packets over the internet to an ip.
I havent done any research into this precise aspect of wake on lan, At least one of my systems is on at any given time, and they all have custom SSH ports forwarded. All I have to do when waking from the internet, is find a system thats on, ssh in, and send my packets through that....
if you get it working from the WAN, post what you had to do, so that I can add it to the guide!
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Just a quick question as I am not familiar with the uses of WoL.
What it useful for?
Security?
Convenience?
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Its not really useful for security, more convienience.
for instance if you have a computer say, in your basement, that you dont always use, and you turn it off. Before you go there you want it to be on and ready, and your near a computer on the 2nd above ground floor. You can wake it up before you head there.
etc, its more or less useless elsewise, because of bios-specific limitations (such as if the power goes out, most systems wont wake up untill powered on and properly shut down)
But, if you can imagine a need to turn on a computer without touching it, WOL is the solution to that need.
My personal main and only use is remote administration while still living at my parents (this need will be gone in 3 days, as i am moving, so i no longer have a use for WOL) Their PC is in the living room, and i usually do most maintance tasks (updates/installs) from my terminal in my room via VNC and ssh. rather than going to turn on the system and come back, i simply use WOL.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Quote:
Originally Posted by
sonny
How do I wake on WAN my pc? I've tried wakeonlan within my network, but I can't access it outside my network.
This wiki may help http://www.dd-wrt.com/wiki/index.php/WOL
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
hm...I still have problems with this wol-stuff.
I followed the HOWTO and I did set the wol setting to 'g'.
But it don't wanna work.
By the way, if I shut down WinXP, it WORKS!, just when I worked with Kubuntu before, even if the wol setting is set correctly, I can't wake up the computer.
I tried to do this via ssh from my Asus wl-500g Premium.
Any ideas?
thx!!
Thassilo
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Thassilo,
Have you tried the other flags? Do you have proper support for your card in linux?
$ sudo ethtool ethX
In my case I have a realtek card which supports WOL in windows, but not in linux. (Even with the latest r1000 module) I've already contacted realtek. They acknowledged the problem and said they would work on it, but this is the kind of thing that requires a lot of people requesting.
incubus
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi,
first off, thanks for helping educate the masses (including myself) about the intricacies of wol...
Here's where I am with trying to get it going: I have Kubuntu 6.06 Drakey-whatsit on a Dell Optiplex with a 3Com 3c905 NIC. Last night I successfully executed one remote wake up on my LAN but I did it by turning on the Kubuntu PC and turning it off about two seconds later. I noted at that point that the LED at the back of the NIC was still lit. Then I sent a magic packet from my other PC and lo and behold the Kubuntu machine turned on.
Now, the problem is that when I shut down Kubuntu (properly or otherwise), the LED on the NIC goes out and consequently WOL doesn't work.
I tried your script and I tried manually issuing the command
% sudo ethtool -s eth0 wol g
but it gives the following error:
Cannot get current wake-on-lan settings: Operation not supported
not setting wol
So, I know the hardware supports WOL and it is enabled in the BIOS but for some reason, Linux does not shut down to the correct power state and the ethtool does not seem to work with my NIC.
Any help would be greatly appreciated,
Eugene
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hey wheatear,
I got the same problem. In my case, the linux module doesn't support WOL. It works in windows.
What do you get from:
$ sudo ethtool eth0
And what is your network card, by the way?
incubus
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi Incubus.
Thanks for the reply. The command you asked about produces the following for me:
---------------------------------------
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Full
100baseT/Full
Advertised auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 24
Transceiver: internal
Auto-negotiation: on
Current message level: 0x00000001 (1)
Link detected: yes
---------------------------------------
As I mentioned earlier, I have a 3Com 3c905 network card.
By the way, have you come across this yet:
http://www.linuxquestions.org/questi...d.php?t=444793
The guy there seems to have overcome the same problem by installing some alternative network driver... Haven't looked into that yet myself.
Thanks again,
wheatear
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi wheatear,
I see good and bad news.
The bad news is that, as you already noticed, your current netcard module (for this specific linux distribution) doesn't support WOL. You can see that you don't have the lines like the other guy has:
Quote:
....
Supports Wake-on: g
Wake-on: g
Now the good news: from what you said and from the other forum thread, you can compile a module for your network card that does support WOL. That's huge. And it's not so complicated. I would:
$ sudo apt-get install build-essential checkinstall linux-headers-`uname -r`
Then at your gunzipped module directory:
$ ./configure
$ sudo checkinstall -D
Note that this doesn't work for me. I don't have an option except for waiting the Realtek guys to sit down, have mercy, and make the module for linux that supports WOL.
Let us know if you're gonna try to compile it and need help.
best,
incubus
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi
I also have problems with the wake on LAN function on my system, I have tried following the guide, but with no luck.
But when I power off just after start(mechanical, using poweroff button) or from windows. I can get it started with magic packages.
I have tried both etherwake and wakeonlan.
ethtool gives me.
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Link detected: yes
So looks like it supports WOL with magic packeges, could it be the power state my system goes into on Halt. As far as I know it should be soft-off.
Hviid
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I found the answer for my problem.
http://www.nvnews.net/vbulletin/showthread.php?t=70384
Last reply.
;) Hviid
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Thank you Chris for this description. I have one important question: what is a purpose for that script that was added to the description? As far as I know WON (Wake On Lan) mechanism is fully based on hardware and is OS (operating system) independent. If you want to use WON you need just a motherboard with BIOS enabled feature of WON and NIC with WON enabled future. That is all. If you are able to boot up a PC remotely that you are able to load any OS. Did I miss something?
Kind regards,
Maciej
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
@mslonik
I assumed the same until I had to use it practically.
Now I think it is like this:
When wol is enabled and the computer is powered down, not all components of the computer are shutdown: for example I suppose that at least the ethernet port has to remain active in order to process the wol magic packet.
I suppose that the script configures the computer to keep the ethernet active.
Moreover, I have discovered the following with my hardware: if I pull the power supply plug from my computer and connect it again, the wol does not work any more. I have to start the computer with the poweron button. Afterwards wol works again.
frafu
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
This script was not working, and I saw that the LED in my router corresponding to the computer I wanted to wake was going off when I powered off the computer.
So I decided to try to remove -i from halt as suggested, and it worked!!!
This is what I did (I'm running Edgy), I warn you that I am not an expert so I don't know if it's OK to do this:
- Make a backup of the /etc/init.d/halt script
- edit the /etc/init.d/halt script
- Locate the line where the halt command is invoked:
Code:
halt -d -f -i $poweroff $hddown
- Remove the -i
That's it. Hope it works for you!!
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Some general remarks on Wake on Lan. First, after some trials on hardware and careful examining all former answers I found the following procedure useful for testing if hardware compoments are ready (compliant) with this technology.
Hardware components:
1. BIOS / motherboard.
2. NIC (Network Interface Card) or Netword Adapter.
Procedure:
1. In BIOS of your motherboard enable WOL functionality (typically in Power Management Setup branch of BIOS options). Is your motherboard compliant to PCI 2.1 standard?
YES | NO
2. Check if for sure your NIC is WOL compatible. Is your NIC compliant to PCI 2.1 standard?
YES | NO
3. Check if your power supply is ATX compliant:
YES | NO
If answer to this question is NO than sorry, you can not use WOL functionality.
3. If answers to questions 1. and 2. are YES than you don't need WOL cable. If any answer to questions 1. and 2. is NO than you need WOL cable. Connect your NIC with motherboard with special WOL cable. See your hardware manuals if any doubts.
4. Experiment. Set your BIOS function WOL enabled and PC in shutdown state. Check if diode on the switch that your NIC is connected to is lit or flashes.
YES | NO
Remark: If NO than there is a problem. Try to boot up your PC and correctly shut it down. Check again.
Remark: Sometimes NIC vendors add a diode for constant monitoring of LAN activity. If BIOS function of WOL is enabled than also diode on your NIC flashes together with diode on a switch. Check your NIC manual if any doubts about diodes functionality.
5. Experiment. Set your BIOS function WOL enabled and PC in shutdown state. From the other computer on the same LAN send MP (Magic Packet) to your PC. Does it awake your PC?
YES | NO
Remark: It should wake it up. Try to boot up your PC and correctly shut it down. Check again.
6. Experiment. Set your BIOS function WOL enabled and PC in shutdown state. Switch off a power supply for at least 10 seconds. Observe if a LED on a switch lights off. Now switch on a power supply. From the other computer on the same LAN send MP (Magic Packet) to your PC. Does it awake your PC?
YES | NO
Remark: My computer does not. Perhaps some people will find their hardware working on these conditions. Please report on that. In my opinion this is one of the weakest points of the whole WOL idea. If there is power loss in your home than your computer can not be awaken remotely. It should be this way, but it seems that most of the NICs do not fulfil this requirement. This fact is very seldomly reported. All I was able to find was honest report of one vendor here:
http://www-307.ibm.com/pc/support/si...cid=SF06-D0035
Such a feature as remote wake up after power loss just should work.
7. Experiment. Set your BIOS function WOL enabled and PC in shutdown state. Wake it up with MP (Magic Packet) send from another PC on your LAN. As soon as it starts to boot and beeps single (end of POST procedures) press power button on a chassis and turn it off again. Now send MP again. Does it wake up your PC?
YES | NO
Remarks. Again, it should wake up your PC. If it doesn't than some problems may occure with your system and "clear shutdown".
Answers to above quiz on my hardware:
1. YES. Motherboard: Abit SA6R. Tweaked BIOS (self made) basing on 7X version.
2. YES. Compaq PCI 10/100 WOL, MPX EN 5038 B. Hard to say what piece of hardware it really is. I used to have 3COM 905C TX-M. Unfortunately this one wasn't working with WOL at all on Linux or even Windows. Strange, but true.
4. YES.
5. YES.
6. NO.
7. YES.
Now, the software part of WOL mechanism:
1. OS (Operating System), especially so called "halt scripts".
2. NIC driver.
Remarks: People in this thread reports that special script is required or at least some tweaks with halt script to enable OS clear shutdown with NIC still powered after shutdown. If your hardware passed the above procedure in similar to my than likely you don't need any special script. Nevertheless I've never tried wake on states different from S5 (ACPI). Perhaps such a script is required for S4 (hybernate state).
Remark: I don't feel comfortable with Linux drivers, so please get me right if I'm wrong but driver for NIC is a standard part of a kernel and there is not much to do, at least with standard kernel that comes with distro. Your NIC should work out of a box.
Remark: The rule of a thumb no. 1. If WON works on Windows, it should so on Linux. If your NIC doesn't work on Linux (or you suppose a problem) take it off your PC and put into another one managed by Windows. Check if it works there.
Remark: The rule of a thumb no. 2. NIC 100 Mbit cards are very cheap nowadays. Borrow one that works with WON from your friend. Now check if yours works with your friend's hardware. Try to exchange with your friend on the NICs.
I hope that this short summary will be of any help to somebody. Good luck!
mslonik (Maciej)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Has anyone had any luck with the broadcom b44 network drivers and wake on lan with Edgy? It doesn't seem b44 supports it as ethtool shows nothing.
I cannot get the bcm4400 drivers to compile either. Wake on Lan works on my machine both in windows and in slackware. Cannot get it working with edgy
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
mslonik, thanks for your very good reply, but I still need some help
my NIC is a DFE-528TX, wich is said to support WOL and PCI 2.1, see dlink page, my rather old motherboard is QDI KuDoz 7, if I look at the page and manual, I don't see any evidence that the motherboard supports PCI 2.1, moreover it has a WOL connector on it.. wich leads me to think it does only support WOL trough the cable, is that the case in your opinion??? If so, either I change mobo or NIC :(
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hm... As far as I investigated issue of WOL cable connector, many motherboards producers add it for the purpose of compatibility with old NICs. So even if you have modern motherboard (PCI 2.1 compliant) still you can find WOL cable connector. Nowadays it should be fairly easy to find such a cable in a second hand shops or on ebay. I'm not sure from when PCI 2.1 is a standard. You can try to check if your motherboard was produced after.
I hope that this explanation is of any help. Merry Christmas!
mslonik (Maciej)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Does anyone know how I can check to see if a computer doesn't have wake-on-lan functionality?
I have two older Gateway brand computers, one bought in 1999 and one bought in 2001. I'm working with the newer 2001 one and I just updated the BIOS and there is no mention of wake-on-lan in the BIOS menu options at startup. There is mention of reboot after power outtage.
Does this mean that this computer cannot wake on lan?
The reason I'm asking is that the older Gateway computer (1999) does have the wake-on-lan in the BIOS menu options and I'm a bit confused.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Missed Hviid's post the first time through... basically, due to a driver bug, nForce4 boards need the MAC address reversed to successfully wake. So instead of wakeonlan 00:01:02:03:04:05, use wakeonlan 05:04:03:02:01:00.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
3com 3c905c users may benefit my solution here:
http://www.ubuntuforums.org/showpost...97&postcount=5
There's how I got it to work for my dapper install.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Now I run Edgy Eft (Kubuntu 6.10) on my machine. I've checked your way for WOL on 3c905x. It does not work for me.
Kind regards,
Maciej (mslonik)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Quote:
Originally Posted by
Hviid
Thanks a lot.
You saved my life!
It is working, finaly!
Thanks again to all that submit these great ideas to forum and share them with the rest of the world.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
thanks Jalonsom! removing the -i from the halt script finally worked for me!
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
mslonik, in Wikipedia it is told that "systems supporting the PCI 2.2 standard coupled with a PCI 2.2 compliant network adapter typically do not require a WoL cable as the required standby power is relayed through the PCI bus." So maybe PCI 2.1 is not enough.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I wonder, if it is any disadvantage to use the WOL cable, if the system can wake up without? I did not find the setting for wake on LAN in my computer's BIOS setup, but there is setting where you can enable or disable PME wakeup events. Well, there is some information about PME vs. WOL in Intel's site. Don't they tell that you should enable the WOL setting in BIOS, if you want to use the WOL cable for remote wake up? Anyway, when I have it connected and poweroff by the power button, I've got the light there in the Ethernet card of the computer. I don't have the light, if I don't have the cable there, even if I have enabled the PME Wakeup Events in BIOS. Anyway, sending the magic packet (by wakeonlan) won't wake up the computer. If I shut down by ubuntu, the light goes off, even if '-i' is removed from /etc/init.d/halt. I have not tried other tweaks in ubuntu with this system so far.
Computer specifications:
Compaq Deskpro EP series Pentium III (500MHz); I suppose it is PCI 2.1 compliant.
Ethernet controller: 3Com Corporation 3c905C-TX-M
lspci output:
Code:
0000:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
0000:00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
0000:00:0d.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
0000:00:0d.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
0000:00:0d.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
0000:00:0e.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
0000:00:0e.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 06)
0000:00:0f.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
0000:00:10.0 Communication controller: Conexant: Unknown device 10b6 (rev 89)
0000:00:14.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:14.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:14.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
0000:00:14.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
0000:01:00.0 VGA compatible controller: Matrox Graphics, Inc. G400/G450 (rev 82)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Do you have to use some other method than sendig a magic packet to create a PME wakeup event? Or should I disable PME wakeup events when using the WOL cable and run wakeonlan in another computer? (I still cannot find a "Wake on LAN" settion in BIOS. When I use the cable, I can get the NIC light on after reconnecting the power plug or using the power button twice, but not by 'sudo shutdown -h now'. Magic packets don't work at all with this computer. When the same kind of ethernet controller was in another machine, I could wake it up, if the NIC (i.e. ethernet controller) light was on.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
How can you cancel the changes made to your system when following the instructions in the first post?
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
i have a problem with wol. i tried to set it up using "ethtool -s eth0 wol g" and it gives no error back. but when i'm using ethtool eth0 after this, it still shows wake-on: d... wol is activated in bios. acording to ethtool the card supports wol. anyone an idea?
edit: it seems, that the card doesn't work right... other card, works fine.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I also cannot get WOL to work - ethtool listed below;
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
Machine is a Dell Optiplex GX260 - bios has WOL set to on - and low power mode disabled. Cannot get any wol program to send a packet - tried about 5. Also tried removing the -i from the halt script.
Any ideas?
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Well, can't help - the config works perfectly for me.
The only problem was with the n-force chipset, where I had to send the MAC address in reverse order, e.g. instead of 00:01:02:03:04:05 I had to send 05:04:03:02:01:00 - some bug in the net card, or so, did not investigate any further.
Let us know if you will be able to fix the problem.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
is it possible to use this function to turn OFF the computer?
Wake-on-lan is working beautifully but I would like to be able to power down my server remotely too
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Quote:
Originally Posted by
zeigerpuppy
is it possible to use this function to turn OFF the computer?
Wake-on-lan is working beautifully but I would like to be able to power down my server remotely too
Is there some problem to login and run init 0 command? Simple openssh-server will do the trick...
Basicaly, as it is server, I prefer not to shutdown, just use some disk powersaving using hdparm.
And, you still can use powersaving to turn off the whole machine if not used for an hour or so.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Also, this can be adapted to work over an always-on internet connection. This method can also be used to turn on a computer from a WAN or over the internet (perhaps its most useful application). Assuming you're using a router, the procedure is as follows:
1. Set up WoL within you LAN, as above, and check that this all works.
2. Set up a port forward on your router. Exactly how you do this depends on the make of router. Typpically, you would forward port 9 from the external connection to port 9 on your LAN - though which port you use on you LAN actually doesn't matter, since the machine listens on all ports. Most remote applications allow you to set the port as well.
Since the machine won't have an IP address (as its switched off), you have to forward the port to a broadcast address on you local network. There are three methods to try for this:
a. The simplest is to use the limited broadcast address 255.255.255.255; however, most routers won't do this for security reasons.
b. Use your local network broadcast address. This is found from your address and subnet mask - for example, if your IP addresses are like 10.0.0.x and your subnet mask is 255.255.255.0, the broadcast address will be 10.0.0.255; again, some routers won't allow this.
c. If neither of the above works, try changing the subnet mask to e,g, 255.255.255.128; (this gives you 126 possible IP addresses). Then your broadcast address will be e.g. 10.0.0.127; this should hopefully work.
3. Then test it! From a remote machine, you can either use a program such as wakeonlan in the repos or one of a number of websites that sends the magic packet to your specified address. If your computer turns on, success!
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi!
I am trying to use WOL using the script provided.my problem is that whenever I enable "wake on pci card" in the BIOS my computer won't shut down, it goes as if I am doing a normal restart.in the BIOS in the power management menu there is also an option "PCI master" which I do not entirely understand, but it doesn't have the same effect.
My hardware:A Realtek RTL8139D NIC on an Elitegroup PM800-M2 motherboard.
Any help will be much appreciated.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
First off thank you for the handy little script! I knew what was happening (the wol setting is lost on powerdown) but didn't have the linux knowledge to yet implement a fix! I can also confirm this has worked on my Feisty install!
In regards to waking up PC's over the internet the method I use is going via my router - I have a Linksys WRT54G running DD-WRT, which allows for SSH management and with some tunneling I can access the router setup pages and use the built in WOL function :-)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I just registered to say thank you for the post, everything worked perfectly.
The forum registration was painful, FF2, wouldn't let me escape the modal box regarding the PM on initial registration to allow pop ups for one sec, page autorefreshed before I could even move a mouse there and hit allow, after I allowed, it just reloading until I closed the tab and came back. Strange.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hello, thank for HOWTO. There was no problem to set it up. But I still have one weird problem. Maybe it will be CHALLENGE for somebody. I have automatically installed via rhine 2 driver module for my ethernet card. When I want to wake the computer up, it wakes up....but only once!!! After magic packet starts computer, my sytem normally boot up. After that I halt computer back and try one more time WOL but second time it does not work. I experienced that after pulling power cord out from PC(or after upgrade to higher version of system) for a moment, boot up and halt it works....but again only once. Maybe something what cut off power from NIC can help but I don't know how to do it. Or something what "reload" completely card, it's configuration and drivers, but modprobe via_rhine -r and modprobe via_rhine -i does not work. THANK YOU for your advices.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I have a Linksys 10/100 Etherfast NIC and Wake on Lan is enabled in the BIOS.
After manually creating the script per the tutorial, and attempting to test the functionality via:
sudo /etc/init.d/wakeonlanconfig,
the following is returned:
Cannot get current wake-on-lan settings: Operation not supported
not setting wol
Furthermore, sudo ethtool eth0 returns:
Settings for eth0:
No data available
From what I had read, I thought this card supported Wake on Lan in both Linux and Windows. It seems strange to me that no information is being returned via ethtool.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I do power ON/OFF my PC from remote locations using browser and this card:
https://ool-43537bf6.dyn.optonline.n...b%20Button.htm
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
i just set up deluge web UI which is super cool
was wondering, can i set up WOL so i can wake it from anywhere. was thinking all i'd need to do is forward the correct port on my router. i already have a dynDNS account... this could be something very cool.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi, I followed these steps successfully a few weeks ago when I initially set up my ubuntu system. To start with I was using the onboard nic (eth0).
I've just added a PCI-E gigabit card that supports a wider range of wake on lan functions (umb and g) and I need to perform this step again for eth1 (eth0 now disabled).
However, I cannot do this until I undo what I did for eth0, but I can't figure this out. How do I reverse the eth0 additions to the startup scripts? Thanks :)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi all,
before all thanks for all the information.
I have an issue... in my case the wol runs but not always.
If I power off a machine (sudo halt) and then send the magic packet, the machine power on.
But If I power off today that machine and tomorrow morning I send the magic packet, the machine doesn´t power on.
Someone could know why it happens?
Thanks a lot.
Juanto.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
It's probably down to the way you shutdown your machine.
Sudo halt for me kills all processes and doesn't allow WOL, but just hitting the power button is OK.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi,
the problem is that if I do "sudo halt" and next I send the wakeonlan the machine power on.
But if I send the wakeonlan after serveral hours, the machine cannot power on.
¿?:)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
What hardware do you have? Onboard NIC or PCI/PCI-E card?
I have to install the latest Intel drivers for my NIC to enable all functionality (e.g. increasing MTU) even though it is recognised by the kernel.
Are there updated drivers available for your NIC?
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi,
my computer is a Dell GX280, it has an onboard NIC.
The issue is that I don´t understan why in some cases wakeonlan runs and in others it doesn´t work.
Case in which always it runs:
Send the wakeonlan subsequently you have power off the machine.
Case in which always it doesn´t run:
Send the wakeonlan after several hours.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
It sounds like a driver issue to be honest or maybe even an ACPI issue.
Your BIOS (via ACPI) may cut power to your MB a specified time after shutdown, hence you can WOL shortly after shutting down, but not several hours later (I'll admit to clutching at straws with that one!).
A driver issue is more likely. As you're using an onboard NIC, try to determine the driver it's using and then search for help on that specifically.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hello,
I've gotten this to work perfectly over the LAN but from the internet i'm not having much luck. I did all the steps from an earlier post by Big_Croc7 that suggested changing settings at the router if it doesn't work right away.
I'll list my setup here in the hope that one you could see a wrong setting somewhere that might be the reason why it's not working. I'd be happy to try anything you can think of, so please, all suggestions are welcome :).
So: from the LAN, no problem at all. Wakes up nicely to the magic packet. From the internet, doesn't work. So the MAC address and Ubuntu settings, BIOS etc. are fine, it's tested plenty of times from within the LAN.
The router is a "TelewWell TW-EA510 ADSL Firewall Router". I have my computer connected through cable at 192.168.0.7. All local addresses are 192.168.0.X.
At the router I have set the following
Code:
SubNetmask 255.255.255.128
Virtual server rule: Forward ports 9 and 7 (UDP & TCP) to 192.168.0.127
This doesn't work. Did I get the broadcast address right for a LAN of 192.168.0.X? I've also tried simply forwarding 9 and 7 to the correct IP address (192.168.0.7) and that doesn't do it either (the internal IP stays the same so I thought it might, but it doesn't).
Any ideas? I'd really like to get this going so I don't mind trying whatever you can think of. Also, please let me know if I left out some important detail about the setup. Since it works from within the LAN, it seems like the problem is the router.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hmm... the settings seem ok... what did you use to send the packet? A page I've used in the past is http://www.depicus.com/wake-on-lan/woli.aspx , though there are lots of others. One thing to note, is that using this, you should set the subnet mask on the web page to 255.255.255.255 (with your external IP address - it uses these to decide where on the internet to send the packet to, so the subnet mask you enter here is different from your local network mask).
The settings for your router seem ok, and yes, that's the right broadcast address. Is that the address that you used for testing within your LAN?
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Quote:
Big_Croc7;3972585 One thing to note, is that using this, you should set the subnet mask on the web page to 255.255.255.255 (with your external IP address - it uses these to decide where on the internet to send the packet to, so the subnet mask you enter here is different from your local network mask).
Thanks for the quick reply. OK, I've been using the same web page to try this but I wasn't setting the subnet mask to all 255's. So that sounded like a great idea, and I tried that now - but unfortunately still no go.
From within the LAN, I've been using my laptop to send either this:
Code:
wakeonlan -i 192.168.0.127 00:50:8D:9A:73:5D
or simply
Code:
wakeonlan 00:50:8D:9A:73:5D
Both seem to do it just fine so I don't actually know if naming the broadcast address does much there, seems like it's the default somehow when I try it from within the LAN.
I did notice something though: the web page seems to have dashes instead of colons for the MAC address (like 00-XX-...). I tried both ways but was unsure which one is the correct for that page. Which ones do you use for that page?
I've also been trying to use the laptop to send that same terminal command to the external ip, and it won't wake up.
The router's config page has the following for each rule:
Protocol (BOTH selected for TCP and UDP)
Public start port 7
Public end port 7
Mapped Private IP Address 192.168.0.127
Mapped Private Port 7
The page says "Leave blank or input 0 indicating Virtual Server Service" at the final field, and I've also tried leaving it blank.
I'm starting to think that this router just doesn't handle this broadcast address thing for some weird reason. Could that be the case? I do hope I'm missing something really obvious here...
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
It does sound like something weird is happening with your router; can you check the logs on the router, and see if that tells you anything? It would be useful to know if the router is getting the packet and dropping it, or it's not getting there at all. You could try forwarding a higher-numbered port, just in case there is something happening with those ports (the magic packet can be on any port at all, it should still work).
As an aside, I think the default for wakeonlan is to send to the IP address 255.255.255.255.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I've just had another idea. You can set the card to wake up the PC from a variety of different packets. In the howto at the start of this thread, there is a line that says "ethtool -s eth0 wol g"; you could try replacing this with "ethtool -s eth0 wol gumb" - this sets it to wake up on other, different messages. I'm not sure why this would work in this situation but it might be worth a try in the absence of a better idea (man ethtool for more info on what exactly the difference is).
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
OK, a quick update: this router really is strange. I just looked at the logs and did all sorts of connections to machines within the LAN from both within and outside (ssh'd into a work computer, used it to launch ftp and ssh's back here to make sure connections come from outside) and the log here really records NOTHING. There's a system log that says the normal DHCP stuff, and a security log that I'd expect to say things about allowed and blocked connections. But nothing gets written into it. Couldn't find anything to change logging options either. So that's pretty much useless.
I also gave using a big port number and forwarding that to the broadcast IP a shot. Didn't work.
More strangeness: the router has 4 LAN ports (and WLAN). Pretty basic. However, I switched some cables around to see what that would do, and noticed that 2 of these 4 ports are actually "outside" of the LAN's firewall and settings. So they get assigned an "outside" IP address, not one of the 192.168... but they get their own from the ADSL line. Haven't seen this before. Anyway, so I of course proceeded to keeping my cable plugged to one of these other ports for a while, wrote down the new IP and shut it down and gave wake-up a try. Worked. So it clearly is an issue with the router not allowing the packet to go through to the local network.
Unfortunately using one of these other LAN ports is not an option for me as they also block me from my local network which I need access to . But this might be a way to devise some sort of a backup plan with another network card that's plugged into another port and only used for wakeups from outside...but I'm not ready to go find a new card just yet for that, I'll keep trying this for a while longer.
Changing the ethtool settings sounds like a good idea. I read the man page and it does sound good to try all those other multicast etc. messages as well. I'll try that next.
To be continued...:)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I tested the "ethtool -s eth0 wol gumb" method now too.
That won't work, it wakes up too easy. I barely had time to shutdown the machine and it woke up. I tried with "gm" but that was too sensitve too, didn't even have time to get to the laptop before it was up again. So I guess my network has enough things flying around that I do need to get the magic packet to work, waking up to any network activity will just make it boot too often.
Another network card attached to one of those other LAN ports would of course do the trick. I guess that's what I'll have to do.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hmm, how strange! At least you've managed to narrow it down. It sounds like you might have what's called a DMZ enabled on the router, though I'm not sure. If it remembers IP addresses after powering down then maybe ethtool gu (for unicast packets only) might work without waking it up too often, but I'm at the limit of my experience with it now I'm afraid. Let us know if you solve it without a second network card :-)
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
another very easy method (for dd-wrt users) is to turn on WOL settings in your BIOS and add the MAC of the computer you want to invoke WOL to the DD-WRT Services panel. Invoking WOL is now as easy as logging into your DD-WRT panel and hitting the right button.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Sounds good, I'll give "ethtool gu" a try still when I get the chance. Might be a few days until I have time to play with this thing next, I'm posting this from work and getting mighty busy with holiday stuff at home.
DMZs I wasn't even thinking about, but actually that might be another way of doing it without another card. Perhaps if I get a DMZ setup that exposes that computer completely it might start receiving the packets fine regardless of whether the router believes them worth relaying or not. I'm not even sure if the router will allow that (a truly exposed internal machine), but I'll look into it. I'm running firestarter to setup firewall rules and denyhosts to slam the door on dictionary attacks to ssh, so should be safe enough, maybe change ssh port to be sure. Anyway, I'll try that one too - thanks again for the tips. I love these forums :)
And oh, foureight84, if I had a DD-WRT capable router I'd be a very happy camper, I'm sure - those things look really nice. I guess part of this whole problem is being too stubborn to give up: I know there's plenty of routers that would let me use wol fine but I'm not about to admit defeat and buy one without a fight, heh. Although I've been keeping an eye out for used Linksys routers that would support DD-WRT, but it looks like whoever has one of those old gems in their possession is not about to give them up easily.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I have a Dimension 9100 and there doesn't seem to be any WOL settings in the BIOS. However, when I do "sudo ethtool eth0" I get the following:
Code:
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
This seems to me to imply that WOL should work. However, it does not. I'm not sure how ethtool works so is it possible that the driver I have supports WOL but the NIC doesn't?
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
It supports wake on lan "g" so you can do:
Code:
ethtool -s eth0 wol g
you can't however use the other options such as multicast (u) or broadcast (b) wake up. However as seen in the posts above, that would mean your pc waking up every time your router pinged it anyway.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Hi all,
I wrote some time ago... about a problem with wakeonlan (you can find it in this threat).
The wakeonlan that I sent it was to a machine placed in another subnet, my machine is 10.161.14.134 and the another machine is 10.161.16.230.
If pass the enough time, the ip 10.161.16.230 is deleted in the routing tables of the router, in this case, the magic packet is not sent in broadcast in that subnet.
If I send the magic packet from a machine, ex: 10.161.16.229, the 16.230 wake up without problems.
Regards,
Juanto.
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Quote:
Hi all,
I wrote some time ago... about a problem with wakeonlan (you can find it in this threat).
Juanto-
I seem to be having the same problem as you. My WOL works fine if i try to do it within an hour (or so) of shutting down the computer. However, if I wait for a longer time, it mysteriously stops working. However, I think all of my computers are on the same subnet (192.168.1.xxx). Could please elaborate on what you did to make WOL work all the time?
Thanks,
Bryan
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Bryan -
I also have the same problem. Have been at it for 2 days and haven't come close to a solution.
What I learnt is that the system should shut down to a G2 (s5) state (see http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface to learn about ACPI) however seems to do so for a short amount of time, maybe for about half hour or so. Then totally shuts down.
I have a onboard Realtek RTL8101E 10/100.
I get the following results:
Code:
$ acpitool -w
Device S-state Status Sysfs node
---------------------------------------
1. P0P2 S4 disabled
2. P0P1 S4 disabled pci:0000:00:1e.0
3. PS2K S4 disabled pnp:00:0d
4. UAR1 S4 disabled pnp:00:0e
5. EUSB S4 disabled pci:0000:00:1d.7
6. MC97 S4 disabled
7. HDAC S4 disabled pci:0000:00:1b.0
8. P0P4 S4 disabled pci:0000:00:1c.0
9. P0P5 S4 disabled pci:0000:00:1c.1
10. P0P6 S4 disabled
11. P0P7 S4 disabled
12. P0P8 S4 disabled
13. P0P9 S4 disabled
14. USB0 S4 disabled pci:0000:00:1d.0
15. USB1 S4 disabled pci:0000:00:1d.1
16. USB2 S4 disabled pci:0000:00:1d.2
17. USB3 S4 disabled pci:0000:00:1d.3
Code:
$ ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
Link detected: yes
Now I figure it is either hardware related or there is someway to configure the shutdown process to do what we want.
I haven't found any info yet on how that possibly could be done. Maybe it requires patching the kernel but that is beyond my "relatively recent move to Linux" capabilities. I'm still looking.
Dave
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Quote:
Originally Posted by
Waste
Just a quick question as I am not familiar with the uses of WoL.
What it useful for?
Security?
Convenience?
When your server is in a location you can not access easily, this saves a lot of time. Zhen the server is in the attic for example, you don't need to run upstairs to put the server on. Yo uwake on lan, then you ssh for all the rest and shut him down through command line. It's convenient.
br,
Walter
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
New to the WOL idea, went through all the setup steps described by OP.
To turn on/off the server from my Windows box I installed http://magicpacket.free.fr/ so I can send a magic packet. The mac address from my server is xx:xx:xx:xx:xx:xx but when I put that into the WOL Magic packet sender it says it must be 12 characters ans shows xx-xx-xx-xx-xx-xx as an example. Changing to use - rather than : does not show a message but does not turn on my server. Any thoughts?
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
Has anyone got WOL working frin the Internet with a BT Home Hub router? I'm having difficulty and the 'Big_Croc' method isnt helping. The BT Home Hub is pretty configurable so I'm hoping someone has worked out how to do it
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
works fine on ecs 741-gxm motherboard with SIS chipset. (Found in fry's $100 pc) and Ubuntu Gutsy 7.10
BTW I am using etherwake gui on ipcop firewall.
:KS
Thank you chris AKA Kai
-
Re: HOWTO: Set your system up for Wake On LAN (WOL)
I'm trying to set this up on an Intel Mac Mini that's running Gutsy. The script seems to run fine, but when I shut down the Mini it loses link with the router and won't wake up.
Any idea what to do to fix this?
Thanks.