Debian Bug report logs - #703888
Please add patch for wake on lan control

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michael Stapelberg <stapelberg@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Please add patch for wake on lan control

Date: Mon, 25 Mar 2013 13:10:35 +0100

[Message part 1 (text/plain, inline)]

Package: qcontrol
Version: 0.4.2+svn-r40-3
Severity: wishlist

Attached you can find a patch which allows the user to control the qnap
Wake on LAN functionality. Please add it to your next upload of
qcontrol.

Note that in order to use it, you also need a fairly recent kernel
including these two commits (likely to be included in Linux 3.10):

https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=42e836eb4527fb635cb799a701fe4c9fe741c03a
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=3871c3876f8084a2f40ba3c3fc20a6bb5754d88d

(you need to enable CONFIG_MARVELL_PHY in your .config and possibly
 patches in order to get poweroff to work¹)

Afterwards, run these commands to power off the qnap (tested with the
TS-119P II only, but qnap has a list of models²) in a way that you can
wake it up via the WOL magic packet afterwards:

  ethtool -s eth0 wol g
  qcontrol wakeonlan on
  poweroff

① http://thread.gmane.org/gmane.linux.debian.ports.arm/11933/focus=12060
② http://wiki.qnap.com/wiki/FAQs#Q.EF.BC.9AWake_on_LAN_support_models

[wakeonlan.patch (text/x-diff, attachment)]

Message #10 received at 703888@bugs.debian.org (full text, mbox, reply):

From: Ian Campbell <ijc@hellion.org.uk>

To: Michael Stapelberg <stapelberg@debian.org>, 703888@bugs.debian.org

Subject: Re: Bug#703888: Please add patch for wake on lan control

Date: Tue, 26 Mar 2013 03:18:38 +0000

On Mon, 2013-03-25 at 13:10 +0100, Michael Stapelberg wrote:
> Package: qcontrol
> Version: 0.4.2+svn-r40-3
> Severity: wishlist
> 
> Attached you can find a patch which allows the user to control the qnap
> Wake on LAN functionality. Please add it to your next upload of
> qcontrol.

Thanks for this. I'm travelling at the moment but I'll looking into this
properly when I return (which is mid April).

> Note that in order to use it, you also need a fairly recent kernel
> including these two commits (likely to be included in Linux 3.10):
> 
> https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=42e836eb4527fb635cb799a701fe4c9fe741c03a
> https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=3871c3876f8084a2f40ba3c3fc20a6bb5754d88d
> 
> (you need to enable CONFIG_MARVELL_PHY in your .config and possibly
>  patches in order to get poweroff to work¹)

CONFIG_MARVELL_PHY doesn't appear to be set in the Wheezy kernel (which
doesn't have the necessary patches in any case). I'll make a note to
check the Sid kernel config as I apply this.

BTW since Wheezy is now pretty deeply frozen and has 3.2 kernel I'm not
going to even bother trying to get any of this stuff into Wheezy I'm
afraid.

> Afterwards, run these commands to power off the qnap (tested with the
> TS-119P II only, but qnap has a list of models²) in a way that you can
> wake it up via the WOL magic packet afterwards:
> 
>   ethtool -s eth0 wol g
>   qcontrol wakeonlan on
>   poweroff

A few questions:

What is the eup stuff, i.e. what does it actually do and would a user
ever want to frob it directly rather than implicitly via the wol
command?

Do you know if there is some way to integrate the last two commands into
a standard "shutdown for WoL path" of some sort? Or can one run the
first two by and and then type halt(8) or poweroff(8) in the usual way
and have it just work?

Do you have a pointer to some docs on how to send a suitable WoL packet?

I'd probably s/wakeonlan/wol/ in the interface, because wol is a well
known acronym and I'm a lazy typist ;-)

Thanks,
Ian.

> 
> ① http://thread.gmane.org/gmane.linux.debian.ports.arm/11933/focus=12060
> ② http://wiki.qnap.com/wiki/FAQs#Q.EF.BC.9AWake_on_LAN_support_models

Message #15 received at 703888@bugs.debian.org (full text, mbox, reply):

From: Michael Stapelberg <stapelberg@debian.org>

To: Ian Campbell <ijc@hellion.org.uk>, 703888@bugs.debian.org

Subject: Re: Bug#703888: Please add patch for wake on lan control

Date: Tue, 26 Mar 2013 09:54:57 +0100

Hi Ian,

Ian Campbell <ijc@hellion.org.uk> writes:
> CONFIG_MARVELL_PHY doesn't appear to be set in the Wheezy kernel (which
> doesn't have the necessary patches in any case). I'll make a note to
> check the Sid kernel config as I apply this.
Yeah, it’s not set currently in the Debian 3.8 kernel. It might be
useful to file a wishlist bug against the 3.9 kernel as soon as it
becomes available.

> BTW since Wheezy is now pretty deeply frozen and has 3.2 kernel I'm not
> going to even bother trying to get any of this stuff into Wheezy I'm
> afraid.
I know ;-).

> What is the eup stuff, i.e. what does it actually do and would a user
> ever want to frob it directly rather than implicitly via the wol
> command?
Deep power saving. EUP = Energy-using Products, a EU directive for power
saving. When you enable EUP, your qnap sleeps so deep, it will not react
to the WOL magic packet. When deciding that you don’t need WOL and you
want to save some power, you might decide to enable EUP as a user.

> Do you know if there is some way to integrate the last two commands into
> a standard "shutdown for WoL path" of some sort? Or can one run the
> first two by and and then type halt(8) or poweroff(8) in the usual way
> and have it just work?
I use this systemd unit file to do that:

[Unit]
Description=Enable Wake on LAN on shutdown
# Just for having the correct order when shutting down.
After=qcontrold.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ethtool -s eth0 wol d
ExecStart=/usr/sbin/qcontrol wakeonlan off
ExecStop=/sbin/ethtool -s eth0 wol g
ExecStop=/usr/sbin/qcontrol wakeonlan on

[Install]
WantedBy=multi-user.target

I realize that systemd is a controversial topic in Debian, but I have no
interest in doing anything similar for sysvinit. Feel free to adopt the
idea if you want to.

> Do you have a pointer to some docs on how to send a suitable WoL
> packet?
Get the MAC address via “ip link show dev eth0” (the thing after
link/ether), then use “wakeonlan <mac-address” from another computer.

> I'd probably s/wakeonlan/wol/ in the interface, because wol is a well
> known acronym and I'm a lazy typist ;-)
I’d recommend against that because then the patch diverges from what
I’ve sent upstream and what I’m going to document soonish on my
website. I’d hate to say “with recent qcontrol versions, use qcontrol
wakeonlan on, but just on Debian, use qcontrol wol on for no good
reason” :-).

-- 
Best regards,
Michael

Message #20 received at 703888@bugs.debian.org (full text, mbox, reply):

From: Ian Campbell <ijc@hellion.org.uk>

To: Michael Stapelberg <stapelberg@debian.org>, 703888@bugs.debian.org

Subject: Re: Bug#703888: Please add patch for wake on lan control

Date: Tue, 26 Mar 2013 10:59:14 +0000

On Tue, 2013-03-26 at 09:54 +0100, Michael Stapelberg wrote:
> Hi Ian,
> 
> Ian Campbell <ijc@hellion.org.uk> writes:
> > CONFIG_MARVELL_PHY doesn't appear to be set in the Wheezy kernel (which
> > doesn't have the necessary patches in any case). I'll make a note to
> > check the Sid kernel config as I apply this.
> Yeah, it’s not set currently in the Debian 3.8 kernel. It might be
> useful to file a wishlist bug against the 3.9 kernel as soon as it
> becomes available.

Right, please prod me if I forget...

> > What is the eup stuff, i.e. what does it actually do and would a user
> > ever want to frob it directly rather than implicitly via the wol
> > command?
> Deep power saving. EUP = Energy-using Products, a EU directive for power
> saving. When you enable EUP, your qnap sleeps so deep, it will not react
> to the WOL magic packet. When deciding that you don’t need WOL and you
> want to save some power, you might decide to enable EUP as a user.

OK, thanks.

> > Do you know if there is some way to integrate the last two commands into
> > a standard "shutdown for WoL path" of some sort? Or can one run the
> > first two by and and then type halt(8) or poweroff(8) in the usual way
> > and have it just work?
> I use this systemd unit file to do that:
> 
> [Unit]
> Description=Enable Wake on LAN on shutdown
> # Just for having the correct order when shutting down.
> After=qcontrold.service
> 
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> ExecStart=/sbin/ethtool -s eth0 wol d
> ExecStart=/usr/sbin/qcontrol wakeonlan off
> ExecStop=/sbin/ethtool -s eth0 wol g
> ExecStop=/usr/sbin/qcontrol wakeonlan on
> 
> [Install]
> WantedBy=multi-user.target
> 
> I realize that systemd is a controversial topic in Debian, but I have no
> interest in doing anything similar for sysvinit. Feel free to adopt the
> idea if you want to.

Understood, I'll see if I can figure out the sysv equivalent.

> > Do you have a pointer to some docs on how to send a suitable WoL
> > packet?
> Get the MAC address via “ip link show dev eth0” (the thing after
> link/ether), then use “wakeonlan <mac-address” from another computer.

As easy as that ;-) Thanks. AIUI WoL in general also supports a kind of
"password" magic number in the packet. I guess this isn't implemented
(I'm not too worried, I don't think it adds much actual security)

> > I'd probably s/wakeonlan/wol/ in the interface, because wol is a well
> > known acronym and I'm a lazy typist ;-)
> I’d recommend against that because then the patch diverges from what
> I’ve sent upstream and what I’m going to document soonish on my
> website. I’d hate to say “with recent qcontrol versions, use qcontrol
> wakeonlan on, but just on Debian, use qcontrol wol on for no good
> reason” :-).

Upstream has been unresponsive now for several years, one of the things
on my todo list is to consider taking over upstream too ;-)

If you do hear back from the current upstream please let me know.

Ian.

Message #27 received at 703888-close@bugs.debian.org (full text, mbox, reply):

From: Ian Campbell <ijc@hellion.org.uk>

To: 703888-close@bugs.debian.org

Subject: Bug#703888: fixed in qcontrol 0.5.1-1

Date: Sun, 12 May 2013 18:47:50 +0000

Source: qcontrol
Source-Version: 0.5.1-1

We believe that the bug you reported is fixed in the latest version of
qcontrol, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 703888@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ian Campbell <ijc@hellion.org.uk> (supplier of updated qcontrol package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 12 May 2013 19:25:57 +0100
Source: qcontrol
Binary: qcontrol qcontrol-udeb
Architecture: source armel
Version: 0.5.1-1
Distribution: sid
Urgency: low
Maintainer: Ian Campbell <ijc@hellion.org.uk>
Changed-By: Ian Campbell <ijc@hellion.org.uk>
Description: 
 qcontrol   - hardware control for QNAP Turbo Station devices
 qcontrol-udeb - hardware control for QNAP Turbo Station devices (udeb)
Closes: 697574 703888 703894
Changes: 
 qcontrol (0.5.1-1) unstable; urgency=low
 .
   * New upstream release.
     - Wake-on-Lan support. (Closes: #703888)
     - Support for qcontrol.d directories. (Closes: #697574)
     - Disable buffering when stdout/err is not a tty. (Closes: #703894)
     - Patches merged upstream.
   * Only require event-modules udeb on armel.
   * Add /etc/qcontrol.d include to config files and package the directory
Checksums-Sha1: 
 7e75d241d3eaa4b1f85bc684702a903dd97e23e2 1935 qcontrol_0.5.1-1.dsc
 880f1b8a36e93f5d729cff50719a55f1b1be2594 21920 qcontrol_0.5.1.orig.tar.xz
 0ced78b8e4bf9d3ea80929a1505ed1d5409a2466 11543 qcontrol_0.5.1-1.debian.tar.gz
 822430e9eff095c6be2dccc7c8cd10447baf96aa 24992 qcontrol_0.5.1-1_armel.deb
 c1066bc38d05f9a156dac1e8fc48f7ad5fc81be6 61094 qcontrol-udeb_0.5.1-1_armel.udeb
Checksums-Sha256: 
 c852a35f5bb08b51db9f2c9a54461fd13b3a86725c1d4e8337e188ec0784704f 1935 qcontrol_0.5.1-1.dsc
 2023ca8c4eebfb85cb26583ae1674bb2d92fedce93af4a469c113f2e4ef1adf4 21920 qcontrol_0.5.1.orig.tar.xz
 1aa892639ba45ae8a9648b25868b3e636c5f1eb18bc5905636947f07a50b4d80 11543 qcontrol_0.5.1-1.debian.tar.gz
 d3dbece50ea93360413b2dd0dc9352e3b36ba80e96c881978dc3df2173a17245 24992 qcontrol_0.5.1-1_armel.deb
 e92c18cad306fed0808cbbe9436b26c08494f9e0ce310f6c5a82f8b90ba9fd53 61094 qcontrol-udeb_0.5.1-1_armel.udeb
Files: 
 fc4173a4af9d7c921a20f67d99942000 1935 utils optional qcontrol_0.5.1-1.dsc
 b66598c724a1bd2f7fb24aa975011755 21920 utils optional qcontrol_0.5.1.orig.tar.xz
 d4a2f8220ed46ea5396485087956f7bd 11543 utils optional qcontrol_0.5.1-1.debian.tar.gz
 d52cd9d78881e8df3ddc7abdad24563b 24992 utils optional qcontrol_0.5.1-1_armel.deb
 7c74397988ff52d5c1203befa8d16ca4 61094 debian-installer optional qcontrol-udeb_0.5.1-1_armel.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRj+GJAAoJECouJZ9pWkbGK9UP/RZu964lFEPDLthH9ZRCbYrh
5TXGSNv8jZegEUbyeBmsjhs2c1TpcDjEsy75iLWY9sx9LLgsmcqIDVa63jpUZG50
cy5LajEp0ZihN3QEnPnxJFBRlGEUEIdT453O7N8HM7WOPSUpeElczy6QF/FjR/nJ
7vSLeMHCFFYM7HyvMEA73I5opo3WAsJU96c0tkkjY5OWScLgb7BSPMXoMhvgjXkz
ZwPYIm3QP7ySuJAJpUnLk5CJyEbjnDa7Veje9WAbLja/kY4FxdBF63om20ORGkSs
ZlpdCjCU6jpgK4WmUvSC6UMZt1VL8B4ZEnrtIJ6gS5bD6MYggOofA/NDHxxY7rZ0
je/vcx180C6/qOHK6TR/uCs2jkAzfZsBeQeJ8Auvz115QNVV7BOq98yztkb+Z3tF
RkxCIDPPnBiyQagAe+Vp/+LJfbhwvFn6UdZy1a5IVE1AVs1NkAgAQVAlH42HJCxb
6qH2Li2sn/dFJwuim25DUqAn8jPXmMNHnOckFAcZVgN1N4UDceCj3VFcIoh4wCsL
qT2KayeVtucicCmPmCZ3Qp9jocRDoRHhlcm1N73hG+6Yc/rrCNZ/BpgmeQB63iVW
aulVbkQ2DWhYwW7xJuqVDwQ/kTRy/N7d7Q6bHkapwem42/5G9qE/Zl0lDDjkTAGh
fiGqmFf83fPCu1Tj8TCP
=eHGc
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.