On 2025-11-14 10:36:32 +0100, Eric Valette wrote: > On Thu, 13 Nov 2025 15:36:50 +0200 Adrian Bunk <[email protected]> wrote: > > On Sun, Aug 31, 2025 at 03:41:28PM +0200, Eric Valette wrote: > > > When was the last time it worked? > > When was the first time it did no longer work? > > Just tested today after your message to be sure. It works again!!! > No clue what change on my system corrected it (except I update my system > everyday and change the upstream kernel for the last longterm one).
FYI, the wakeonlan script hasn't changed since at least bookworm (and this may be much more longer, as the script says 2005, though I'm wondering whether this is up-to-date). > I do not suspect kernel as etherwake was working at the same time > wakeonlan was not. I've noticed at my lab that packets seem to be sometimes randomly filtered or ignored. So it may be just luck that etherwake was working at that time. Unless the difference of behavior is reproducible, you cannot deduce anything. And if you can reproduce this, you should look at the differences with wireshark. Otherwise I think that this bug should be closed and the wakeonlan package should reenter testing (it has just been removed from testing). -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
