Bugzilla – Bug 10191
WOL while connected to Squeezenetwork
Last modified: 2009-12-07 09:23:43 UTC
A customer is requesting that the Duet should be able to wake a computer on your local network from sleep/off while its connected to Squeezenetwork. Currently, the SB Classic, Transporter, and Squeezebox Boom can do this, but the Duet cannot.
I'm confused by this. If connected to SN, there PC isn't involved at all. Can you elaborate, Julius?
I did some testing, and found that the IP3K players are not really 'waking' the PC when they switch from SN to SC. The behavior is that they time out first, then when you 'press right to try again' that is when the WOL packet is sent and the target PC is woken. Behavior with IP3K player ========================= Connect a boom to local SC Switch boom to SN Put local PC to sleep using Boom UI, switch to SC Watch boom attempt to connect and time out Click 'right to continue' which will then send the WOL packet Watch PC wake and boom connect to local SC The Duet does not have the same behavior ======================================== Connect Duet to local SC Switch duet to SN Put local PC to sleep Using SBC UI, switch to SC NOTE: at this point, the last SC attached is not listed, as the SBC is doing real time network scanning and since the PC is 'sleeping' SC is not broadcasting that it is available to be 'woken' and connected to.
*** Bug 10695 has been marked as a duplicate of this bug. ***
As I proposed in 10695, I think that the easiest solution would be to send a WOL magic packet whenever, from SN, one tries to connect to Squeezecenter. Even if the server was awake there shouldn't be ill effects (at least, I see none when the same happens everytime I turn on my HTPC and the server is already awake). Cheers and thanks for an ever great product!
I'm finding (with SC 7.3.3 24866 and SBC firmware r3856) that after switching to SN the SBC will remember the SC server(s) by name for about 1 minute after the server goes into the suspend state. During that minute it is possible to use the SBC to change to the server as Music Source, and it will wake the server. After around 1 minute the SBC loses the SC server names, and the choices for music source are SN, Other Server, and the IP address of the server to which it was previously connected. But it won't send the magic packet to the server when I specify the IP address -- perhaps it has forgotten the corresponding MAC address? As an additional note, I *am* able to WOL the server reliably with the SBC using the WOL applet (http://wiki.slimdevices.com/uploads/5/55/WOL.zip). Configuring the WOL applet requires the user to give the display name and MAC address for the server.
*** Bug 15259 has been marked as a duplicate of this bug. ***
Controller still does this in 7.5 it does not WOL the server on return from SN +1 vote