I use Wake-on-LAN daily, to bring back my computer from sleep when I return home. A script detects when my phone becomes pingable on home WiFi, wakes the main PC and powers on the TV. Saves a few moments doing all that manually then waiting for everything to come back on.
If that's enough and does the job, then there's no reason for anything else. Plus, it's yours and you can modify it at will - which is a big plus in my books!
@@bitsundbolts perhaps the BIOS option WOL is just for sleep mode, and PME is for powered-off states. This way you could control which computers are able to be turned on by magic packets: only those in sleep, only those powered off, or both. Or none.
@@bitsundboltsnot sure, but the "On LAN" option may refer to PXE rather than WoL, especially that its in the "Boot" section. I would expect settings for WoL to be in the "Power" menu.
Nope. Fully irrelevant. The problem is that he is missing the bios chip from the card (the rectangular socket). If you don't have this, then the card has no brain to process the magic packet.
@@bitsundbolts I think it's because pme is the base system that WOL hooks into as an addon. I've used WOL a LOT to wake up workstations and have them update during the night. I also used it to turn on my workstation while riding public transport to my office as well as turning on my home pc on the ride back. That was the win2k/xp age where pc's could take a while to finish booting, especially office pc's that were already slow and had to load the network stack. edit: IIRC you also had to change a device setting INSIDE WINDOWS so the adapter remains powered on after shutdown. It's a device property in the adapter properties through network properties.
Fun fact: There are 2 types od PCI slots: 5 volt and 3.3 volt ones. If the key (notch) is at the back it is a 5 volt slot and if it is on the front it is a 3.3 volt slot. You can identify earlier PCI cards by having only the "original" back key signifying a 5 volt card. However soon after the new 3.3 volt standard was introduced manufacturers adapted fast and made "universal" cards that work on both 5 and 3.3 volt PCI slots and you can identify those by having 2 keys (notches): one in the back and one in the front.
In the late 90s and early 2000's we used this a lot at ISP's. For the machines that didn't support it we would use an AT power supply and hotwire the power switch to always be on and had a foxconn board with a bunch of solenoids that you could ssh into and type commands to click the solenoid off and on, so it would cycle the power and restart the server.
I have used WOL on new hardware, and I do network stuff for work so I am familiar with the frame format, but never knew about the three pin connector on old hardware. Very cool.
I hammered WOL back in the day when working at a school. I created two implementations: A VB program to use during the day, and a web site that I could access first thing in the morning before going to work (the school). When I got to work, I'd check the Symantec Ghost console to see which machines had 'checked in' (before school started). For those that did not check in, I'd hurry around every morning to inspect, and fix (undo petty PC vandalism by students) to ensure all the 360-odd PCs were ready for use at the start of the day! WOL was (and is) cool. In fact, one group of PCs had WOL on the motherboard, but was not enable-able in the BIOS. I contacted Award (the BIOS maker), gave them the motherboard details and the BIOS string, and they created a modified BIOS that supported the motherboard's WOL!
Pretty sure that the BIOS option right below "On LAN" also needs to be enabled in order for it to work -- "On PME" is short for "On Power Management Event" and that's part of the WoL stuff too. If you don't enable the Wake On PME, the Wake On LAN won't work, as far as I understand it!
@@matthewday7565 yeah, cause there is also ring-in Power ON, used on old PSTN lines, where you would call and the modem would send a PME and wakeup the board too!
On atx machines, there's no need to send to sleep or hibernate the computer. Mostly motherboards supports wake on lan power on. So you can power on the machine even is powered off. Just need to keep the power cable and lan cable connected.
I've gotten a similar experience like you, it only worked half the time, because it's really dependant on the BIOS of the board, the BIOS settings (WOL and PME events, ACPI states) and OS settings. Best luck I had was with a 3com card that had the 4 pin connector and later slot 1/socket 370 board. Weirdest I ever got it to work on was a socket 7 HP Vectra with a Pentium 1 non-mmx. It had some weird proprietary PSU which probably played a part in making this work.
Wake on LAN was present on my very first Network card that I got... A CNet Pro 200WL adapter. It was in an old Socket 7 that was AT based, so no chance of any wake on LAN feature, and the LANs I used it on was very rudimentary as well. We had hubs and had to assign IP addresses ourselves :D
I think your difficulties in getting the system to wake from the S5 or powered down state is one of a number of reasons why WOL isn't more widely known or used. In order for WOL to work from a S5 state the hardware & BIOS/UEFI also needs to implement wakeup on Power Management Event properly. Even so I found this video very interesting. WOL is a topic I haven't touched in years as in my IT career the only time I was in a situation where it was used was during a corporate Win 7 to Win 10 migration project in 2016.
having a network kvm attached or built in I guess is just so much simpler to configure and importantly for the users to grasp how it works rather than trying to grasp with the concepts of WOL and thinking what it works with and how and thinking of situations where it would even be useful.
I have used Wake on Lan on modern machines (2× Zen 2, 1× Coffe lake) and it works fine with integrated NIC. Soft power off or standby - it works either of those. Apple M1 (mac mini) - not tested yet. External PCI-e NIC - havent tried that.
I remember when WOL first came out, I struggled. On some of network cards, you had to change the driver settings under power management even more. I recall some cards wouldn't work until you DISABLED "allow the computer to turn off this device to save power". You are not trying to save power! If the NIC is shut off when windows tells the computer to power off, it won't respond to magic packets anymore. Try to uncheck this option, even if the "allow this device to bring the computer out of standby" is then grayed out.
Used WOL a bit at work back in the day but I also messed with it a bit waking up old HP Compaq laptops from firewalls I was testing back then for a bit of fun/curiosity. WOL is not used much these days since a typical office machine has very low idle power draw so things just get left on and you don't need it for servers as they typically have management cards (iLO, DRAC etc.) that you can remotely power them on with.
I remember using this at uni to turn my PC in in university accomodation Halls from uni when I need files from my pc or wanted to send files back to my PC it was rather useful before larger portable or cloud storage
I've never played with Wake on LAN but I've seen it in BIOS/UEFI settings relating to power management. Your video makes me want to play around with it for some experience considering I already know my PCs support it. But I haven't really had the need for it since I could always press the power button to turn on my PCs. Then there's my practice of always unplugging any PC I have when its not being used since the little idle draw the PSU's have matter in places where electricity is kinda expensive.
When the Nintendo Wii first came out, where I lived didn't have any high-speed internet access, and I configured a random computer is a router that would dial into the internet (and eventually got a Wi-Fi router to act as an access point), and when I hooked up my Wii that I got on launch day, I would find my computer/router would turn itself on randomly. I believe the Wii would send the magic WOL packet to the MAC address of the last known router it connected to if it was able to connect to Wi-Fi and buy wasn't getting an IP address.
Haha, same here! I've seen these small plastic connectors, but never bothered to even read what was written next to them. I found out that they connect to the network card while researching for this video.
@bitsundbolts In the case of the motherboard you are using you do need the 3 pin cable from MBI to Ethernet card to provide the WOL power to the card. This actually was normal. Things change over time, but since this was an add on card it had to have that stand by power providing on the card. You did a great job on the video. :) Would have been nice to also show some of the Linux and also macOS versions of sending the magic packet as well. :) Keep up the good job on your videos! :D
Thanks! 🙏 I wish I had enough time to look into other operating systems. But I don't have a lot of experience with MacOS and even less with Linux. I'll try to find an original WOL cable at the scrapyard. I'm sure I had many in my hand and never knew what they were for. Well, now I'm looking for them - of course, now I don't find any 😅
Interesting. I have several boards with WOL . I've never messed with network cards. I do have 4 towers wired to a switching box, via the vga and sound from each . So I only use one monitor , mouse and keyboard. I'd like to network them together at some point.
Hmmm... Interesting. I experimented with WOL years ago when it was relatively new and had a bad experience. It was activated (but not used) in the BIOS of one machine on my LAN. Some months later, my LAN went totally TU. The card in the machine with WOL activated started to jabber and I had a heck of a time figuring out who was the "bad boy". After disabling WOL, the jabbering stopped and I was able to continue using that card. The success stories in the comments here have encouraged me. I might give it another try. It would certainly simplify what I do now (a beaglebone black activates a relay wired into the target machine's power button)! 😅
I use WOL on my x79 system that I use as a server. It fires up even from completely off. I can even power it on from outside the home with tailscale. I use fing to send the packet when I'm at home, or the wakeonlan utility if i need to log in to another machine to do it. I think I only had to enable it in the BIOS to make it work iirc.
So before I even watch the video I'm going to share my story on this topic. I took a job in IT work back in 2006. It didn't take long before we realized none of the new computers we just bought could be turned off short of unplugging them from the wall. We couldn't figure it out at all. My friend (and superior) believed it was related to wake on lan. It was, but not in the way you might think. Eventually I had a computer that was having more serious issues. I started removing components to see if it helped. Then I discovered that removing the firewire card fixed the issue.......wait.......did it just power off? So I took another computer that was working just fine and yanked its firewire card. Does this turn off now? It sure does! The firewire card was forcing a WOL signal. To this day I have no idea why, but what I do know is we were able to get a refund on these cards and have them all replaced with a different model. I verified the new model didn't cause the problem. I had to get them installed in over 300 computers. lol It wasn't fun.
Well, it is possible to trigger WOL over PCI - so, technically, any PCI device can trigger a power-on event if it's enabled in the BIOS. Edit: But it's an interesting story! How long did it take you to fix all 300 computers? I guess you needed to test them after you replaced the FireWire card. Not for the WOL bug, but more like a test that they still turned on.
@@bitsundbolts The worst part was "Gary Lester....Tay's Valley" (his name and the school he was at). I had kids that couldn't even log in and he made a big deal about not being able to turn it off. I told him it was a low priority. I had a lot on my plate. That bastard told on me. My boss sided with him while talking to him and then sided with me. He said you're right, but you can't say things like that. I'm like bullshit. I tell it how it is. I'm not going to dance around egg shells for this guy. Meanwhile Gahanna (the high school I went to as a kid) got a new teacher. I was working on some stuff for him and he bought me lunch. Guess who got higher priority whenever tasks were deemed equal? lol
Ahh, dancing around eggshells to make sure not to hurt anyone's ego. You were right in prioritizing your tasks and finishing in order. If you give up this privilege of prioritizing your work, you'll end up with only high priority work - and we all know that that can't work.
I use WOL at home in my homelab setup. It's in my automated power failure management. Since I have a UPS, my servers and NAS are scripted to shutdown in an orderly fashion. Same thing on power restoration, servers need to restart in the right order because of the NAS. My scripts issues WOL to start the machines at the appropriate time during init script execution.
@@bitsundbolts Yes. I love power outages now ;-) I get to watch it all shutdown and come back automatically, all services starting up one by one. It's beautiful.
so in my experience WOL just plain worked. We used it for re-imaging entire computer labs. We also had software that could shut down all the computers as well. So WOL to 20+ computers, re-image, re-name, join the network, and then shut down........all automated.
Because must be configured to WoL. In this old PCs: boot windows -> driver configures card to WOL -> shutdown -> WOL works (shutdown is real, but functionality not survive power cut off). In moderm computers, bios or embedded firmware do this transparent (and more, I implemented sideband commutication on our mainboards via I2C on Intel NICs even when computer is powered off.
I had my experience with WOL during my 20s, where hardware from that era was already obsolete. However I went ahead to build my storage server with a Pentium 3 that I had lying around. But I had my fair share of struggles with the technology. I had to be very selective which hardware I chose because not every combination would work well. Even so I had to power it on manually the first time, only then (after the first time) that the magic packet would turn on the computer (have you tried this scenario?). It would be fine if it weren't for the case that the power goes out more often than you might think. I even wrote a small app to make it easier to cycle through powering on and off and checks in which state is in. Under the hood is uses the ether-wake command (or other similar, e.g. ethtool) to powering on and ssh for powering off. I don't remember digging into how the magic package was actually constructed, maybe I would have implemented directly in PHP if I knew it was that easy!
Yeah, WoL had a lot of issues for a surprisingly long time. Although I work in IT and have been performing sysadmin tasks on some scale since the days of coax networking, incredibly, it wasn't until a few years ago that I had my first scenario where WoL was the solution of choice AND ACTUALLY WORKS SUFFICIENTLY RELIABLE FOR A CHANGE. Mostly. I still don't know why it doesn't in the rare case that it doesn't. 😂 IPMI on the other hand...
I tinkered with WoL on my modern PC some time ago. I wanted to be able to turn on the PC if I needed to access it remotely. One day I turned the PC on remotely and the RCD tripped - so suddenly I was away and everything at home was without power, including the fridge! So I never felt so brave again but it was likely a faulty RCD as it happened again and then stopped when I replaced the RCD! 🙂 I found this video pretty interesting! Thanks for the deep dive on how the magic packet works. Why 16 times? PS: 3-2-1- go is my trademark!!!
I don't know why the Mac address of the target PC should be related 16 times. Maybe to fill the frame somehow? I really don't know. Ahm, I knew you were to comment on the 3-2-1-go 😂... I think I watched too many Tony359 videos!
@@bitsundbolts That makes sense, since Ethernet frames need to be a minimum of 64 bytes long per specification. It's there to help CSMA/CD. I have also heard before, that it was supposed to help for some NICs that would be "slow" in capturing the frame while in low power standby. Like some models might be able to synchronize on a later part of the frame.
Guess I always figured Wake-on-LAN always meant wake the system up from sleep... if it was for powered off systems you think they would have termed it Power-on-LAN.... .
I remember trying this back then, I had a 440BX MB, I got it working but it was unreliable, it would work fine for weeks and then fail, I then had to go to the actual machine to power it up and would then work ok for days or weeks and fail again, I never got it fully working and got around it by setting the bios wake up on power and cycled the power remotely instead.
It seems like I missed an option in the BIOS - apparently, there were two switches I should have enabled. But I did read that WOL was sometimes unreliable - and without a delivery confirmation, you never know if the packet was delivered.
I'm waking up my backup server with Wol. Main server wakes it up, makes backup of data, and shuts it down after that. Not standby, complete shutdown. Network card even has option to shut down lights in that state, so nothing points that it waits for WoL event. Doing backup once a week, no point keeping backup server up and running all the time. Of course i could do like just timed wakeup, but this way if I need to do unscheduled access to backup server, I could just wake it up through VPN, no need for physical access to power on machine.
As a suggestion, try hard power cycling the target system and try sending a WOL packet again. Maybe the OS or its NIC driver is leaving the card in an odd or disabled state. A fresh power cycle should reset anything like that. I assume the signal is just like an active low output? In which case maybe you can test by grounding the input to the board without a NIC etc. but I'd research first.
Interesting idea. I wouldn't be surprised if the signal pin somehow connects to the pin header of the board's power switch. But it must be controlled by the BIOS setting, so there must be something between.
Back at that time WOL is a mess. Most motherboard usually cannot wake from full power-off (S5) unless network adapter are powered via +5 VSB or +3.3 VSB (which some of the adapter provide separate cable to powered it on standby. 3.3VSB later added in PCI 2.0 with 3.3VSB and PME# + SMBUS support around 2000. So before that if Card it only support on on-board NIC which may already have standby power through ATX +5VSB. Even though, many BIOS and EC may not process PME# Event on the PCI bus that comes from slot, after PME# EC may need to communicate to PCI devices via SMBUS to find what is going on about the PME# Event to decide it should powered on or not, like it is LAN or ALARM or Keyboard, etc.
My retropc has one of those 3com NICs inside. Windows xp,me (and maybe 2000) support it out of the box but if you want to install it on NT or 98/95 you have to install the driver from the CD first, install the card turn PC back on and reinstall the driver 🙄 one of the strangest things i have ever seen in my computer experience,a PNP card defeating the whole idea of PNP.
It's also dependent on the os you use. I have never got it to work on windows despite multiple guides on it and setting the state on the network card but I have managed to get wol to work under Linux from complete shutdown without issue
I think later versions of Windows improve on the feature, but it should be possible to get it working. I put the board in storage for now, but I'll retry maybe with a different network card and BIOS options (seems I have missed another option in the BIOS based on comments I got from viewers).
Not regarding WOL, but the network configuration on obsolete OS (like windows 98). On my machines I set the IP address manually, without filling the gateway address. That way I have access to and from the machine, inside my network, but the machine itself is disconnected from the internet (due to the lack of deaignated gateway), avoiding external threats.
Hi, i used to do that, i would set secondary / segmented servers on ip 2 to 20 Then management pc's 50-99 Staff Pc's 99-200 Printers were 200+ At one stage ( late 90's due to hub and cableling costs, we used different subnets to keep sales away from accounts , all both of those away prom production
I think I'm gonna replace the network card on my retro computer with one that has a WOL connector, just so it connects to the 3 pin WOL connector on the board. Even if I don't use it, it just looks cool having a cable from the board to the LAN card :-)
@@bitsundbolts I had a WOL cable on my CD-ROM audio cables box! I also found 3x RTL8139 cards (A/D/D), a D-Link DFE-530TX and a SMC/Compaq branded card with WOL connector, so I'll play around with these to see which ones work with WOL correctly and which one has better transfer speeds on Windows 98 and 2000. The winner will have the privilege of staying on my RETRO-W98 machine 🙂
@@bitsundbolts So I managed to make it work from a powered off state. From the cards I mentioned, only the D-Link DFE-530TX immediately turns on the network lights the moment I turn on the power supply and before powering on the computer. Then, after powering on and shutting down Windows 98, the network card remains active and most probably retains the IP, so I used the WakeMeOnLan tool to power the computer on from the off state. It won't work if I turn the power supply off, because the network card will lose power and release the IP. So if you want to turn it on from an off state, you need a network card that has activity lights when the computer is powered off.
I'll try it again when I have the board set up. Maybe a different network card will work. Also, others mentioned that I should enable a second option in the BIOS
@@bitsundbolts I enabled "Resume On Ring/LAN" and "Resume on PME#". I just tested the Realtek 8139D cards and they also turn on the computer from off state even without any activity LEDs turned on. Only the SMC card didn't work. Realtek cards had the fastest transfers speeds so I'll keep one of those on the computer.
You could test if its the network card or the motherboard not doing its job when trying to wol from shutdown by connecting the signal pin to 5V. Please check if there is voltage between signal and ground on the board, if it is then the connection should be to gnd not 5Vsb. it should have the same effect as pressing the power button. it that doesnt work connect the signal pin to powerbutton on the frontpanel connector :) that should make your network card turn on the pc regardles of bios settings but still respect the checkbox in the networkadapter settings on windows. a modern pc needs to be booted once after power is connected for telling the network card to activate wol, maybe thats the same for old ones too.
routers do not take part in WoL. Routers works in L3 (IP). Switches and hubs works in L2 (ethernet frames). Magic packet is just special ethernet frame.
the wol protocol is porly implemented in some motherboards. some work if you activate the on modem power ring and the lan other have a opton in power manament (power on pci or some similar). i use for years (still use to power mi media center over mi phone) the wol sistem or works or not. .Energy-Efficient Ethernet must be disabled. Deep Sleep must be disabled in the BIOS if the option is present. The computer must be in S3, S4 or S5 state, this also depends on the computer model in windows advanced option of the network card enable the options sthut down wake on lan / wake on magic packet /wakeon magic patern /wol speed 10mb or similar
I use WoL with my smart home Home Assistant, to switch on my zigbee controllable power outlet and 5 seconds after that it sends a WOL. My PC is under my desk and I'm too lazy to bend down and push the power button, so I just start it via a shortcut on my phone.
I was playing with WOL on all PC I had with this feature back in time. But there was very poor source of information about it so never success. I remember network card 3COM C905-CX-TX-M with WOL very expensive so I move it everytime to newer PC I build from slightly used part and few new I bought. This card was with me for about 18years and meet 6 PC until I got motherboard with build in gigabite RJ45 but still have card somewhere at home. I can't wake up PC by WOL on pourpose but something does. I remember few of my PC's start randomly at night from sleep or standby it happen even when mouse in not powered USB by 5Vst but only when WOL allowed in bios. Don't know where magic packet came from or some fantom signal or card malfunction.
I use Wake-On-LAN on second PC and there is one problem. If PC had powerloss (electricity shut off and come back later), motherboard LAN do not work, doesn't matter what BIOS setting you are using, fact is, LAN chip do not work on motherboard when it get power first time. LAN chip work when you start PC first time and shutdown PC, and you not take power off. I solve this problem by using BIOS setting -> START PC WHEN POWER ON. And in Linux OS I put task to shutdown PC after 15minutes (I can cancel this by command or use wake-on-LAN later)
in power loss the ip in the network card is erased (lost the link) so no wol until windows start the lan (in some cases buid the lan in the router over MAC adress asigned the ip solve the problem)
@@yomismo2836 in my case, integrated LAN port not light even led lights when powered first time. I think it is design fault. And I guess, this can be modified by soldering power input somehwere else...
I've owned a few PCs, including my current one, that seem to keep the onboard LAN NIC active even when the machine is shut down, does this mean that my computer could be turned on via WOL even when shut down? I presume so.
Maybe. If you go into your BIOS, see if you find anything related to the power events, WOL, or similar. Disabling those features might turn off your network card when it's powered down.
Many years ago i had a pc with dial up modem 56, the pc was turned off, but it was turn on by it self, i thought its broken or some thing wrong with it, but i found that really now sure now, when ever my sister pick up the phone the pc turned on from the modem, and it was not in sleep mode or stand by, i never use this state only shutdown, to fix this i changed something in the bios, and its stoped turning on.
The broadcast address that should always work is 255.255.255.255, the Most Broadcast of them all 😁 Wake On LAN used to be a pain: on some machines it wouldn't work right. Sometimes if you started the OS and then shut down it would work, but after power was gone it would stop working until a power on-off cycle, no matter what was set in the BIOS. Somewhere in advanced adapter properties in Windows is an option to enable WoL (depending on driver?), if it is disabled there the opposite might be true. In Linux I used ethtool to enable WoL on the NIC, and then powertop --auto would disable it back, 'cause power saving…
I must have missed that one extra option in the BIOS. I'll try that again with both settings in the BIOS enabled. Regarding the ground pin - as far as I can tell, the ground pin isn't necessary to connect. It is already connected through the PCI slot. But, let me test it the way I showed in the video with that extra BIOS option enabled and see if it works without connecting the ground pin.
ha ha i dont know but my old k6 amd ga-5ax everytime the phone rang when the modem was adsl my PC would turn on - and i always wondered why that happened - sometimes i would get home my pc was on and im like "huh im sure i turned it off "
I have the same motherboard, but have never messed up with WOL - I have no purpose for it. And unfortunately I've upgraded it past bios P15 (to P17) and on these motherboards you can't downgrade the bios, so I can't have the same configuration as you.
I read about this issue! Luckily, the micron board doesn't have a newer bios than P15. I haven't checked the board yet with all its features, but it looks like a decent board as long as you have a newer model that supports Pentium III CPUs.
It's too bad they didn't make WOL have a shutdown packet or something similar. I have remote mining rigs that freeze or hangup sometimes and I don't have an expensive network PDU that can remotely power cycle devices
Ha, maybe spamming a system with magic packets will power it off - like the 5-second press on the power button. I doubt it'll work, but I understand your pain to not be able to power cycle the mining rigs remotely. But there should be solutions. Maybe something with power buttons and. Raspberry pi/Arduino
@@bitsundbolts i solved this issue on some rigs using a smart plug like kasa, but some rigs I have on 240V using c13 power only. Strange no one has come up with a solution to this yet, without expensive PDUs
I guess from a certain point forward, you're entering the field of data centers - and then there is just expensive equipment. The only route would be to engineer something yourself - but that's probably easier said than done.
WoL is still flaky even today. I use WoL daily for 2 of my PCs. One has MSI motherboard and the other one has Asus board. Both exhibit the same problem. As long they have been shut down using OS's shut down procedure everything works as expected. But if the machine shuts down because of power outage, or there is power outage when machine is already shut down, neither keyboard nor WoL is able to turn it on. If these were actual remote machines which I had no physical access to, that would be the most useless remote wake-up implementation ever.
That's what I heard as well. Others have said that a power outage renders WOL inoperable. Only after a physical start of the system will WOL work again.
I use Wake-on-LAN daily, to bring back my computer from sleep when I return home. A script detects when my phone becomes pingable on home WiFi, wakes the main PC and powers on the TV. Saves a few moments doing all that manually then waiting for everything to come back on.
Are you using Home Assistant for the automation?
@@bitsundbolts no, my own scripts and smart socket with Tasmota firmware and simple HTTP API.
If that's enough and does the job, then there's no reason for anything else. Plus, it's yours and you can modify it at will - which is a big plus in my books!
@@romanrm1 is that a cron job to detect your phone?
@@adammontgomery7980 Yes
In the bios, you have “on pme: stay off” set, maybe you want to turn that on to allow power management events…
Hm, I must have overlooked that option. Why would they have two options in the BIOS? Just so that I can have a master switch?
@@bitsundbolts perhaps the BIOS option WOL is just for sleep mode, and PME is for powered-off states. This way you could control which computers are able to be turned on by magic packets: only those in sleep, only those powered off, or both. Or none.
@@bitsundboltsnot sure, but the "On LAN" option may refer to PXE rather than WoL, especially that its in the "Boot" section. I would expect settings for WoL to be in the "Power" menu.
Nope. Fully irrelevant. The problem is that he is missing the bios chip from the card (the rectangular socket). If you don't have this, then the card has no brain to process the magic packet.
@@bitsundbolts I think it's because pme is the base system that WOL hooks into as an addon.
I've used WOL a LOT to wake up workstations and have them update during the night.
I also used it to turn on my workstation while riding public transport to my office as well as turning on my home pc on the ride back. That was the win2k/xp age where pc's could take a while to finish booting, especially office pc's that were already slow and had to load the network stack.
edit:
IIRC you also had to change a device setting INSIDE WINDOWS so the adapter remains powered on after shutdown. It's a device property in the adapter properties through network properties.
Fun fact: There are 2 types od PCI slots: 5 volt and 3.3 volt ones. If the key (notch) is at the back it is a 5 volt slot and if it is on the front it is a 3.3 volt slot. You can identify earlier PCI cards by having only the "original" back key signifying a 5 volt card. However soon after the new 3.3 volt standard was introduced manufacturers adapted fast and made "universal" cards that work on both 5 and 3.3 volt PCI slots and you can identify those by having 2 keys (notches): one in the back and one in the front.
Neat, I didn't know that!
In the late 90s and early 2000's we used this a lot at ISP's. For the machines that didn't support it we would use an AT power supply and hotwire the power switch to always be on and had a foxconn board with a bunch of solenoids that you could ssh into and type commands to click the solenoid off and on, so it would cycle the power and restart the server.
Nice integrated Sound on that Slot 1 board. :)
I have used WOL on new hardware, and I do network stuff for work so I am familiar with the frame format, but never knew about the three pin connector on old hardware. Very cool.
I hammered WOL back in the day when working at a school. I created two implementations: A VB program to use during the day, and a web site that I could access first thing in the morning before going to work (the school). When I got to work, I'd check the Symantec Ghost console to see which machines had 'checked in' (before school started). For those that did not check in, I'd hurry around every morning to inspect, and fix (undo petty PC vandalism by students) to ensure all the 360-odd PCs were ready for use at the start of the day! WOL was (and is) cool. In fact, one group of PCs had WOL on the motherboard, but was not enable-able in the BIOS. I contacted Award (the BIOS maker), gave them the motherboard details and the BIOS string, and they created a modified BIOS that supported the motherboard's WOL!
Wow! That is a big time saver! Very creative use of WOL and Magic Pakets. Also, very cool that Award prepared a BIOS for you!
Pretty sure that the BIOS option right below "On LAN" also needs to be enabled in order for it to work -- "On PME" is short for "On Power Management Event" and that's part of the WoL stuff too. If you don't enable the Wake On PME, the Wake On LAN won't work, as far as I understand it!
Thinking that too, WOL is likely a special case of PME
That's probably it. On my modern systems where I use it, the option is in power management and it says 'wake on PCI event'.
I'll try that! Thanks for the hint!
Did it work? @@bitsundbolts
@@matthewday7565 yeah, cause there is also ring-in Power ON, used on old PSTN lines, where you would call and the modem would send a PME and wakeup the board too!
I use WOL on my x64 based home made NASes its great to save power when the NAS is not in use and commonly needed data are cached on the home server.
On atx machines, there's no need to send to sleep or hibernate the computer.
Mostly motherboards supports wake on lan power on. So you can power on the machine even is powered off.
Just need to keep the power cable and lan cable connected.
I've gotten a similar experience like you, it only worked half the time, because it's really dependant on the BIOS of the board, the BIOS settings (WOL and PME events, ACPI states) and OS settings. Best luck I had was with a 3com card that had the 4 pin connector and later slot 1/socket 370 board. Weirdest I ever got it to work on was a socket 7 HP Vectra with a Pentium 1 non-mmx. It had some weird proprietary PSU which probably played a part in making this work.
Wake on LAN was present on my very first Network card that I got... A CNet Pro 200WL adapter.
It was in an old Socket 7 that was AT based, so no chance of any wake on LAN feature, and the LANs I used it on was very rudimentary as well.
We had hubs and had to assign IP addresses ourselves :D
I think your difficulties in getting the system to wake from the S5 or powered down state is one of a number of reasons why WOL isn't more widely known or used. In order for WOL to work from a S5 state the hardware & BIOS/UEFI also needs to implement wakeup on Power Management Event properly.
Even so I found this video very interesting. WOL is a topic I haven't touched in years as in my IT career the only time I was in a situation where it was used was during a corporate Win 7 to Win 10 migration project in 2016.
having a network kvm attached or built in I guess is just so much simpler to configure and importantly for the users to grasp how it works rather than trying to grasp with the concepts of WOL and thinking what it works with and how and thinking of situations where it would even be useful.
I used wol a lot around 15 years ago so I could patch user machines overnight from home. Since then I haven't used it much though.
I have used Wake on Lan on modern machines (2× Zen 2, 1× Coffe lake) and it works fine with integrated NIC. Soft power off or standby - it works either of those. Apple M1 (mac mini) - not tested yet.
External PCI-e NIC - havent tried that.
I remember when WOL first came out, I struggled. On some of network cards, you had to change the driver settings under power management even more. I recall some cards wouldn't work until you DISABLED "allow the computer to turn off this device to save power". You are not trying to save power! If the NIC is shut off when windows tells the computer to power off, it won't respond to magic packets anymore. Try to uncheck this option, even if the "allow this device to bring the computer out of standby" is then grayed out.
I'll try this option as you explained. Others have said that I might have missed a second option that needs to be enabled in the BIOS as well.
Used WOL a bit at work back in the day but I also messed with it a bit waking up old HP Compaq laptops from firewalls I was testing back then for a bit of fun/curiosity.
WOL is not used much these days since a typical office machine has very low idle power draw so things just get left on and you don't need it for servers as they typically have management cards (iLO, DRAC etc.) that you can remotely power them on with.
Love it =D Always fun to mix software and hardware, and you explained everything very well!
Thanks! I hope I'll find a better hardware implementation later and maybe also get my hands on a proper WOL cable.
I remember using this at uni to turn my PC in in university accomodation Halls from uni when I need files from my pc or wanted to send files back to my PC it was rather useful before larger portable or cloud storage
I've never played with Wake on LAN but I've seen it in BIOS/UEFI settings relating to power management. Your video makes me want to play around with it for some experience considering I already know my PCs support it.
But I haven't really had the need for it since I could always press the power button to turn on my PCs. Then there's my practice of always unplugging any PC I have when its not being used since the little idle draw the PSU's have matter in places where electricity is kinda expensive.
It's all about awakening curiosity 😊. That's how I ended up making this video. I also have never used WOL before.
When the Nintendo Wii first came out, where I lived didn't have any high-speed internet access, and I configured a random computer is a router that would dial into the internet (and eventually got a Wi-Fi router to act as an access point), and when I hooked up my Wii that I got on launch day, I would find my computer/router would turn itself on randomly. I believe the Wii would send the magic WOL packet to the MAC address of the last known router it connected to if it was able to connect to Wi-Fi and buy wasn't getting an IP address.
Thank you! Always wondered about these WOL/WOM connectors on motherboards, but never bothered to actually learn about it myself :D
Haha, same here! I've seen these small plastic connectors, but never bothered to even read what was written next to them. I found out that they connect to the network card while researching for this video.
@bitsundbolts
In the case of the motherboard you are using you do need the 3 pin cable from MBI to Ethernet card to provide the WOL power to the card. This actually was normal.
Things change over time, but since this was an add on card it had to have that stand by power providing on the card.
You did a great job on the video. :)
Would have been nice to also show some of the Linux and also macOS versions of sending the magic packet as well. :)
Keep up the good job on your videos! :D
Thanks! 🙏
I wish I had enough time to look into other operating systems. But I don't have a lot of experience with MacOS and even less with Linux.
I'll try to find an original WOL cable at the scrapyard. I'm sure I had many in my hand and never knew what they were for. Well, now I'm looking for them - of course, now I don't find any 😅
very interesting! never tried it, even on the main pc, but it's nice to know
Interesting. I have several boards with WOL . I've never messed with network cards. I do have 4 towers wired to a switching box, via the vga and sound from each . So I only use one monitor
, mouse and keyboard. I'd like to network them together at some point.
Networking is a very interesting topic. Good luck and I hope you'll try WOL on some of those boards
Hmmm... Interesting. I experimented with WOL years ago when it was relatively new and had a bad experience. It was activated (but not used) in the BIOS of one machine on my LAN. Some months later, my LAN went totally TU. The card in the machine with WOL activated started to jabber and I had a heck of a time figuring out who was the "bad boy". After disabling WOL, the jabbering stopped and I was able to continue using that card.
The success stories in the comments here have encouraged me. I might give it another try. It would certainly simplify what I do now (a beaglebone black activates a relay wired into the target machine's power button)! 😅
I use WOL on my x79 system that I use as a server. It fires up even from completely off. I can even power it on from outside the home with tailscale. I use fing to send the packet when I'm at home, or the wakeonlan utility if i need to log in to another machine to do it. I think I only had to enable it in the BIOS to make it work iirc.
I think I missed a second option in the BIOS I show in this video. but good that it works for you! Still a technology very much used today!
Damnit you uploaded when I’m supposed to clock in
Ah, sorry... Maybe you can watch it later
@@bitsundboltsnah it’s okay I totally did loo
So before I even watch the video I'm going to share my story on this topic. I took a job in IT work back in 2006. It didn't take long before we realized none of the new computers we just bought could be turned off short of unplugging them from the wall. We couldn't figure it out at all. My friend (and superior) believed it was related to wake on lan. It was, but not in the way you might think. Eventually I had a computer that was having more serious issues. I started removing components to see if it helped. Then I discovered that removing the firewire card fixed the issue.......wait.......did it just power off? So I took another computer that was working just fine and yanked its firewire card. Does this turn off now? It sure does! The firewire card was forcing a WOL signal. To this day I have no idea why, but what I do know is we were able to get a refund on these cards and have them all replaced with a different model. I verified the new model didn't cause the problem. I had to get them installed in over 300 computers. lol It wasn't fun.
hmm ironically these new PCs were HPs.
Well, it is possible to trigger WOL over PCI - so, technically, any PCI device can trigger a power-on event if it's enabled in the BIOS.
Edit: But it's an interesting story! How long did it take you to fix all 300 computers? I guess you needed to test them after you replaced the FireWire card. Not for the WOL bug, but more like a test that they still turned on.
@@bitsundbolts I don't know. I had help. A couple weeks maybe?
@@bitsundbolts The worst part was "Gary Lester....Tay's Valley" (his name and the school he was at). I had kids that couldn't even log in and he made a big deal about not being able to turn it off. I told him it was a low priority. I had a lot on my plate. That bastard told on me. My boss sided with him while talking to him and then sided with me. He said you're right, but you can't say things like that. I'm like bullshit. I tell it how it is. I'm not going to dance around egg shells for this guy. Meanwhile Gahanna (the high school I went to as a kid) got a new teacher. I was working on some stuff for him and he bought me lunch. Guess who got higher priority whenever tasks were deemed equal? lol
Ahh, dancing around eggshells to make sure not to hurt anyone's ego. You were right in prioritizing your tasks and finishing in order. If you give up this privilege of prioritizing your work, you'll end up with only high priority work - and we all know that that can't work.
I use WOL at home in my homelab setup. It's in my automated power failure management. Since I have a UPS, my servers and NAS are scripted to shutdown in an orderly fashion. Same thing on power restoration, servers need to restart in the right order because of the NAS. My scripts issues WOL to start the machines at the appropriate time during init script execution.
Nice! So, still a very useful technology!
@@bitsundbolts Yes. I love power outages now ;-) I get to watch it all shutdown and come back automatically, all services starting up one by one. It's beautiful.
I can imagine!
so in my experience WOL just plain worked. We used it for re-imaging entire computer labs. We also had software that could shut down all the computers as well. So WOL to 20+ computers, re-image, re-name, join the network, and then shut down........all automated.
Nice and efficient!
Because must be configured to WoL. In this old PCs: boot windows -> driver configures card to WOL -> shutdown -> WOL works (shutdown is real, but functionality not survive power cut off). In moderm computers, bios or embedded firmware do this transparent (and more, I implemented sideband commutication on our mainboards via I2C on Intel NICs even when computer is powered off.
I only hear Magic Mike Packet. 😂 Intrusive thoughts 😅
I had my experience with WOL during my 20s, where hardware from that era was already obsolete. However I went ahead to build my storage server with a Pentium 3 that I had lying around. But I had my fair share of struggles with the technology. I had to be very selective which hardware I chose because not every combination would work well. Even so I had to power it on manually the first time, only then (after the first time) that the magic packet would turn on the computer (have you tried this scenario?). It would be fine if it weren't for the case that the power goes out more often than you might think.
I even wrote a small app to make it easier to cycle through powering on and off and checks in which state is in. Under the hood is uses the ether-wake command (or other similar, e.g. ethtool) to powering on and ssh for powering off. I don't remember digging into how the magic package was actually constructed, maybe I would have implemented directly in PHP if I knew it was that easy!
I used WOL with my old DBox2 to power on my PC. I also integrated a shutdown option.
Yeah, WoL had a lot of issues for a surprisingly long time. Although I work in IT and have been performing sysadmin tasks on some scale since the days of coax networking, incredibly, it wasn't until a few years ago that I had my first scenario where WoL was the solution of choice AND ACTUALLY WORKS SUFFICIENTLY RELIABLE FOR A CHANGE. Mostly. I still don't know why it doesn't in the rare case that it doesn't. 😂 IPMI on the other hand...
I tinkered with WoL on my modern PC some time ago. I wanted to be able to turn on the PC if I needed to access it remotely. One day I turned the PC on remotely and the RCD tripped - so suddenly I was away and everything at home was without power, including the fridge! So I never felt so brave again but it was likely a faulty RCD as it happened again and then stopped when I replaced the RCD! 🙂
I found this video pretty interesting! Thanks for the deep dive on how the magic packet works. Why 16 times?
PS: 3-2-1- go is my trademark!!!
I don't know why the Mac address of the target PC should be related 16 times. Maybe to fill the frame somehow? I really don't know.
Ahm, I knew you were to comment on the 3-2-1-go 😂... I think I watched too many Tony359 videos!
@@bitsundbolts That makes sense, since Ethernet frames need to be a minimum of 64 bytes long per specification. It's there to help CSMA/CD.
I have also heard before, that it was supposed to help for some NICs that would be "slow" in capturing the frame while in low power standby. Like some models might be able to synchronize on a later part of the frame.
I had one college that had a PSU failure right after a wake on lan request. It was more like "wake on bang". Fun days 😂
Guess I always figured Wake-on-LAN always meant wake the system up from sleep... if it was for powered off systems you think they would have termed it Power-on-LAN.... .
You could try hooking up the middle pin on the 3 pin connector too se if that would help
I remember trying this back then, I had a 440BX MB, I got it working but it was unreliable, it would work fine for weeks and then fail, I then had to go to the actual machine to power it up and would then work ok for days or weeks and fail again, I never got it fully working and got around it by setting the bios wake up on power and cycled the power remotely instead.
It seems like I missed an option in the BIOS - apparently, there were two switches I should have enabled. But I did read that WOL was sometimes unreliable - and without a delivery confirmation, you never know if the packet was delivered.
I'm waking up my backup server with Wol. Main server wakes it up, makes backup of data, and shuts it down after that. Not standby, complete shutdown. Network card even has option to shut down lights in that state, so nothing points that it waits for WoL event. Doing backup once a week, no point keeping backup server up and running all the time. Of course i could do like just timed wakeup, but this way if I need to do unscheduled access to backup server, I could just wake it up through VPN, no need for physical access to power on machine.
Very nice use of WOL!
Cough, cough, “Magic Frame”. 😂
As a suggestion, try hard power cycling the target system and try sending a WOL packet again.
Maybe the OS or its NIC driver is leaving the card in an odd or disabled state.
A fresh power cycle should reset anything like that.
I assume the signal is just like an active low output? In which case maybe you can test by grounding the input to the board without a NIC etc. but I'd research first.
Interesting idea. I wouldn't be surprised if the signal pin somehow connects to the pin header of the board's power switch. But it must be controlled by the BIOS setting, so there must be something between.
Back at that time WOL is a mess.
Most motherboard usually cannot wake from full power-off (S5) unless network adapter are powered via +5 VSB or +3.3 VSB (which some of the adapter provide separate cable to powered it on standby. 3.3VSB later added in PCI 2.0 with 3.3VSB and PME# + SMBUS support around 2000.
So before that if Card it only support on on-board NIC which may already have standby power through ATX +5VSB.
Even though, many BIOS and EC may not process PME# Event on the PCI bus that comes from slot, after PME# EC may need to communicate to PCI devices via SMBUS to find what is going on about the PME# Event to decide it should powered on or not, like it is LAN or ALARM or Keyboard, etc.
My retropc has one of those 3com NICs inside. Windows xp,me (and maybe 2000) support it out of the box but if you want to install it on NT or 98/95 you have to install the driver from the CD first, install the card turn PC back on and reinstall the driver 🙄 one of the strangest things i have ever seen in my computer experience,a PNP card defeating the whole idea of PNP.
It's also dependent on the os you use. I have never got it to work on windows despite multiple guides on it and setting the state on the network card but I have managed to get wol to work under Linux from complete shutdown without issue
I think later versions of Windows improve on the feature, but it should be possible to get it working. I put the board in storage for now, but I'll retry maybe with a different network card and BIOS options (seems I have missed another option in the BIOS based on comments I got from viewers).
Not regarding WOL, but the network configuration on obsolete OS (like windows 98).
On my machines I set the IP address manually, without filling the gateway address. That way I have access to and from the machine, inside my network, but the machine itself is disconnected from the internet (due to the lack of deaignated gateway), avoiding external threats.
Hi, i used to do that, i would set secondary / segmented servers on ip 2 to 20
Then management pc's 50-99
Staff Pc's 99-200
Printers were 200+
At one stage ( late 90's due to hub and cableling costs, we used different subnets to keep sales away from accounts , all both of those away prom production
Hi @@georgemaragos2378, that was a smart procedure :)
I think I'm gonna replace the network card on my retro computer with one that has a WOL connector, just so it connects to the 3 pin WOL connector on the board. Even if I don't use it, it just looks cool having a cable from the board to the LAN card :-)
It should be easy to come by those WOL cables. I just didn't happen to have one.
@@bitsundbolts I had a WOL cable on my CD-ROM audio cables box! I also found 3x RTL8139 cards (A/D/D), a D-Link DFE-530TX and a SMC/Compaq branded card with WOL connector, so I'll play around with these to see which ones work with WOL correctly and which one has better transfer speeds on Windows 98 and 2000. The winner will have the privilege of staying on my RETRO-W98 machine 🙂
@@bitsundbolts So I managed to make it work from a powered off state. From the cards I mentioned, only the D-Link DFE-530TX immediately turns on the network lights the moment I turn on the power supply and before powering on the computer. Then, after powering on and shutting down Windows 98, the network card remains active and most probably retains the IP, so I used the WakeMeOnLan tool to power the computer on from the off state. It won't work if I turn the power supply off, because the network card will lose power and release the IP. So if you want to turn it on from an off state, you need a network card that has activity lights when the computer is powered off.
I'll try it again when I have the board set up. Maybe a different network card will work. Also, others mentioned that I should enable a second option in the BIOS
@@bitsundbolts I enabled "Resume On Ring/LAN" and "Resume on PME#". I just tested the Realtek 8139D cards and they also turn on the computer from off state even without any activity LEDs turned on. Only the SMC card didn't work. Realtek cards had the fastest transfers speeds so I'll keep one of those on the computer.
You could test if its the network card or the motherboard not doing its job when trying to wol from shutdown by connecting the signal pin to 5V. Please check if there is voltage between signal and ground on the board, if it is then the connection should be to gnd not 5Vsb. it should have the same effect as pressing the power button. it that doesnt work connect the signal pin to powerbutton on the frontpanel connector :) that should make your network card turn on the pc regardles of bios settings but still respect the checkbox in the networkadapter settings on windows. a modern pc needs to be booted once after power is connected for telling the network card to activate wol, maybe thats the same for old ones too.
That sounds like a nice afternoon of experimenting with different options! Nice!
routers do not take part in WoL. Routers works in L3 (IP). Switches and hubs works in L2 (ethernet frames). Magic packet is just special ethernet frame.
I'm not an expert in networking. But wouldn't the router still be involved in sending the packet to all connected clients?
@@bitsundbolts router can have switch and it will take part. But it is diffrent network level. For not network expert just saying router is fine. :D
All the way to Windows 11 24H2 Microsoft in their infinite wisdom defaults to wake the PC with any packet, not only a magic packet.
I didn't check how modern operating systems are set up by default. But that would be a bad way to configure the network adapter out of the box.
@@bitsundbolts It does result in the system randomly waking up.
the wol protocol is porly implemented in some motherboards.
some work if you activate the on modem power ring and the lan other have a opton in power manament (power on pci or some similar).
i use for years (still use to power mi media center over mi phone)
the wol sistem or works or not. .Energy-Efficient Ethernet must be disabled.
Deep Sleep must be disabled in the BIOS if the option is present.
The computer must be in S3, S4 or S5 state, this also depends on the computer model
in windows advanced option of the network card enable the options sthut down wake on lan / wake on magic packet /wakeon magic patern /wol speed 10mb or similar
Interesting!
Try it with connecting the ground regardless as it wouldn’t be there if not needed
I would love to see some Forsaken game play!
You saw that icon on the desktop.. I tried, eh, I'm not good at that game at all 😂
Never managed to get this to work on any board I've had up to 2022.
It requires quite a bit of configuration and then the correct magic packet. It's not so easy to get everything right.
12:40 ipconfig /all would probably also have the MAC address revealed.
Yes you will. It's called physical address.
I use WoL with my smart home Home Assistant, to switch on my zigbee controllable power outlet and 5 seconds after that it sends a WOL. My PC is under my desk and I'm too lazy to bend down and push the power button, so I just start it via a shortcut on my phone.
Haha, really? The power button on your PC must be in a very inconvenient location! But still a nice feature to set up with home assistant.
I think this would have been way easier if you had used scapy to generate the traffic.
But then you wouldn't see the structure of the magic packet, would you?
I was playing with WOL on all PC I had with this feature back in time. But there was very poor source of information about it so never success. I remember network card 3COM C905-CX-TX-M with WOL very expensive so I move it everytime to newer PC I build from slightly used part and few new I bought. This card was with me for about 18years and meet 6 PC until I got motherboard with build in gigabite RJ45 but still have card somewhere at home. I can't wake up PC by WOL on pourpose but something does. I remember few of my PC's start randomly at night from sleep or standby it happen even when mouse in not powered USB by 5Vst but only when WOL allowed in bios. Don't know where magic packet came from or some fantom signal or card malfunction.
I use Wake-On-LAN on second PC and there is one problem.
If PC had powerloss (electricity shut off and come back later), motherboard LAN do not work, doesn't matter what BIOS setting you are using, fact is, LAN chip do not work on motherboard when it get power first time. LAN chip work when you start PC first time and shutdown PC, and you not take power off.
I solve this problem by using BIOS setting -> START PC WHEN POWER ON. And in Linux OS I put task to shutdown PC after 15minutes (I can cancel this by command or use wake-on-LAN later)
in power loss the ip in the network card is erased (lost the link) so no wol until windows start the lan (in some cases buid the lan in the router over MAC adress asigned the ip solve the problem)
@@yomismo2836 in my case, integrated LAN port not light even led lights when powered first time. I think it is design fault. And I guess, this can be modified by soldering power input somehwere else...
Sadly most companies tell employees to leave their computers on 24/7 for security scanning. So so wasteful.
What happens if you short the signal wire to the standby power? Or to Gnd?
Through a 10k resistor perhaps, for safety :)
Hehe, I don't know. I don't want to try 😅
@@bitsundbolts it should be OK through a 10k, but yeah, it's your kit not mine 😆
I've owned a few PCs, including my current one, that seem to keep the onboard LAN NIC active even when the machine is shut down, does this mean that my computer could be turned on via WOL even when shut down? I presume so.
Maybe. If you go into your BIOS, see if you find anything related to the power events, WOL, or similar. Disabling those features might turn off your network card when it's powered down.
Many years ago i had a pc with dial up modem 56, the pc was turned off, but it was turn on by it self, i thought its broken or some thing wrong with it, but i found that really now sure now, when ever my sister pick up the phone the pc turned on from the modem, and it was not in sleep mode or stand by, i never use this state only shutdown, to fix this i changed something in the bios, and its stoped turning on.
There is a feature called wake-on-ring or similar for modems if I'm not mistaken. Might have been that - maybe it was active.
The broadcast address that should always work is 255.255.255.255, the Most Broadcast of them all 😁 Wake On LAN used to be a pain: on some machines it wouldn't work right. Sometimes if you started the OS and then shut down it would work, but after power was gone it would stop working until a power on-off cycle, no matter what was set in the BIOS. Somewhere in advanced adapter properties in Windows is an option to enable WoL (depending on driver?), if it is disabled there the opposite might be true. In Linux I used ethtool to enable WoL on the NIC, and then powertop --auto would disable it back, 'cause power saving…
you NEED to connect the GROUND PIN!!!!! it will not work without it then you need to set the on pme: stay off to on pme: to on in the bios!!!!
I must have missed that one extra option in the BIOS. I'll try that again with both settings in the BIOS enabled.
Regarding the ground pin - as far as I can tell, the ground pin isn't necessary to connect. It is already connected through the PCI slot. But, let me test it the way I showed in the video with that extra BIOS option enabled and see if it works without connecting the ground pin.
9:25 i see, u have cheat (Forsaken) :D
ha ha i dont know but my old k6 amd ga-5ax everytime the phone rang when the modem was adsl my PC would turn on - and i always wondered why that happened - sometimes i would get home my pc was on and im like "huh im sure i turned it off "
There was something called wake-on-ring. It was for modems and similar to wake-on-lan. It might have been the reason why your PC turned itself on.
I have the same motherboard, but have never messed up with WOL - I have no purpose for it. And unfortunately I've upgraded it past bios P15 (to P17) and on these motherboards you can't downgrade the bios, so I can't have the same configuration as you.
I read about this issue! Luckily, the micron board doesn't have a newer bios than P15. I haven't checked the board yet with all its features, but it looks like a decent board as long as you have a newer model that supports Pentium III CPUs.
It's too bad they didn't make WOL have a shutdown packet or something similar. I have remote mining rigs that freeze or hangup sometimes and I don't have an expensive network PDU that can remotely power cycle devices
Ha, maybe spamming a system with magic packets will power it off - like the 5-second press on the power button. I doubt it'll work, but I understand your pain to not be able to power cycle the mining rigs remotely. But there should be solutions. Maybe something with power buttons and. Raspberry pi/Arduino
@@bitsundbolts i solved this issue on some rigs using a smart plug like kasa, but some rigs I have on 240V using c13 power only. Strange no one has come up with a solution to this yet, without expensive PDUs
I guess from a certain point forward, you're entering the field of data centers - and then there is just expensive equipment. The only route would be to engineer something yourself - but that's probably easier said than done.
WoL is still flaky even today. I use WoL daily for 2 of my PCs. One has MSI motherboard and the other one has Asus board. Both exhibit the same problem. As long they have been shut down using OS's shut down procedure everything works as expected. But if the machine shuts down because of power outage, or there is power outage when machine is already shut down, neither keyboard nor WoL is able to turn it on. If these were actual remote machines which I had no physical access to, that would be the most useless remote wake-up implementation ever.
That's what I heard as well. Others have said that a power outage renders WOL inoperable. Only after a physical start of the system will WOL work again.
Are you the "bub" that wolverine keeps referring to?
(it's a joke pls don't shoot me)
It can make your PC woke.
Awake not woke! 🙂