** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ifupdown (Ubuntu)
Importance: Wishlist => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/44170
Tit
FYI, on my side I ensure the interface stays "awaken" (and not up, it
can not stay "up", in the Unix meaning of this term, once the system has
shut down) by putting these two lines in /etc/default/halt :
NETDOWN=no # to not shutdown the interfaces
ethtool -s eth0 wol g # to activate the wake-on-la
Ooo, thanks for posting this hack ("pre-down false"); it's much smaller
than mine (rewriting init scripts).
I'd add that ideally you should remove the -i option to halt in
/etc/init.d/halt - at the moment there is apparently a bug that stops
halt -i working on ubuntu, but it's supposed to shutdown
Sorry, duplicate was https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.10/+bug/26266
--
Wake on LAN: No safe way to keep interface up
https://bugs.launchpad.net/bugs/44170
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubu
After some tests, "pre-down false" is not a workaround for me. I still
have the problem even though ifupdown is not bringing down the
interface. The computer is deaf to wake on lan magic packet after ubuntu
shutdown.
I therefore suspect thet ifupdown may not be the (only) package
concerned.
FYI,
This is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/44170
I suggest importance to be raised since at my work, not being able to
turn on the PC remotely with wake on lan is a major problem.
--
Wake on LAN: No safe way to keep interface up
https://bugs.launchpad.net/bug
