Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
When in my Fedora 10 I power off the system, by using the gnome icon or even the command line "poweroff", it shut down the machine and power off it as expected - EVEN THE NIC. I can see its led is off !
This happens when I put the machine in hibernate mode too, but not in suspend mode.
When I power on and and power off it just after the POST messages, when grub is waiting a key to select an option, I can see the NIC's led is still blinking at each second or so.
When I power on the machine and select windows (dual boot system) and then power it off, it power off as expected, I mean, it leaves the NIC on - the led blinks even with the machine powered off.
As result, I can't wake up my machine remotely by using Wakeup-On-Lan since the NIC is powered off by Fedora.
There is a way to control this, or a work around ?
Do you think I must post a bug report on kernel list ?
Yes, it is not a kernel bug, but a "feature" of network driver.
Looks like the network driver does not check the BIOS information about WOL and always initialize the NIC with WOL disabled.
Not a big problem at all. A simple "ethtool eth0 -s wol g" at boot time enable wol again.
In fact, in Fedora 10, just putting ETHTOOL_OPTS="wol g" on /etc/sysconfig/network-scripts/ifcfg-eth0 would do the trick.
hello i have applied these changes and WOL is working fine when i used it to wake my machine from turn off mode....
But it is not working when i switches my machine to sleep mode. My machine is not responding to magic packet sent , if it is in sleep mode. Also this all happens with ubuntu only .....If i go to sleep mode through Windows 7 ultimate. Then my machine can detect the magic packet and resume all the state of machine as earlier.
Can WOL for sleep/suspend/hibernate is possible in ubuntu......if yes do we require some more changes and what are those changes required.