I installed windows on a separate HDD , and now WOL doesnt work over lan, or from the internet( im behind a router, with port 9 forwarded to machine)

I do sudo wakeonlan -i ROUTER IP 00:d4:XX:XX:4f:XX
earlier it used to work , now it doesnt.

I had installed WOL using this :

https://www.cyberciti.biz/tips/linux...c-packets.html

I am running debian 8

The Windows driver for your Ethernet card has probably disabled WoL. In that case, WoL won't work once you've booted into Windows and then shut the system down, unless you turn your computer manually back on again and let the BIOS POST reset the settings (which completely defeats the purpose of WoL).

Many Windows drivers can be told explicitly to leave WoL enabled. Take a look at the NIC driver in Device Manager, and see if you can find any WoL related settings on the "Advanced" tab. On my Atheros NIC it's called "Wake Up Capabilities", but each vendor seems to use their own terminology.

1 members found this post helpful.

Windows does NOT DISABLE wol unless you ask it to. WOL is a bios function anyway.

So you think it is still working?

If it was and isn't now it is not a Windows problem.
WOL is handled by the hardware and all it does is send a start signal to the CPU the same as pressing the ON button.

Unless disabled by Windows. It appears to have been working until Windows was booted...

It could easily be a Windows default that hasn't been changed.

1 members found this post helpful.

It is NOT a Windows function. It may have been disabled USING Windows but not BY Windows. It is NOT a Windows default to change it at all. It is purely to do with the power on settings in the card. The card does not know or care what OS is installed when it sends the signal.

Sorry, but it appears you're not reading what's being said here. The first reply, post #2, by Ser Olmy said specifically:
They never said it was by 'default', or anything else...no one else has either. The facts as stated by the OP support all of this because:

• WOL was working, until...
• ...they booted into Windows, and...
• ...it STOPPED working afterwards

As Ser Olmy said initially...if the Windows driver turned off that feature, it won't work until you manually power off/back on the system, which sets thing back to what BIOS says it should be. No one said it was by default, but stated (correctly) that it *CAN BE* disabled.

And I am saying that the Windows driver will NOT have turned it off unless asked to do so.

Right...which it obviously did.

IT wouldn't ask itself to do so!!

It may be that he installed some other software that turned it off, but Windows will not do it without being told to do so.

Right..who is saying that it will do it by default, besides you?

It could very well be the OP turned it off, or that the driver they're using is an older one where it WAS disabled by default. They said "Windows"...for all we know, it's Windows Vista or XP, before that feature was even implemented in the driver they're using.

You did??

Once again, you appear to not be reading (or understanding) what's been written, either purposefully or through inattention/trolling. You said:
...to which I *REPLIED* "Right...which it obviously did." The meaning of this answer in a longer sentence (for you) is "Yes, the Windows driver turned off that feature, either due to it being an old driver, or by the user asking the driver to disable that particular feature". Does that make you happier???

Again/still: either it's an old driver, or it was turned off IN the driver intentionally. Why is this hard to grasp? NO ONE is now, or has been, saying Windows will by default turn that off. We ARE saying it CAN be turned off, and point to the obvious fact that it WAS, basing it on what the OP posted.

And you or other people keep blaming or implying blame by Windows when that is not the case.