Bug 14592 - Don't send Wake On LAN magic packets at power-on
: Don't send Wake On LAN magic packets at power-on
Status: NEW
Product: SqueezePlay
Classification: Unclassified
Component: Networking
: 7.4.x
: PC Windows XP
: P2 normal with 2 votes (vote)
: ---
Assigned To: Felix Mueller
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-05 14:18 UTC by Philip Meyer
Modified: 2011-01-14 00:30 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2009-10-05 14:18:30 UTC
I don't think this is too clever at the moment.

I turned my Touch off, whilst it was connected to my local server (or at least the last thing I played on it was some local music).
I hibernated my PC.

My PC needed to be offline for some time, so I decided to play some internet radio.

I turned on the Touch.  This must have sent a Wake-On-LAN magic packet, because my server turned on.

This is not good - there's no way to attempt to use Touch without causing the local server to power on.

On Classic players, it only sends a WOL when attempting to connect/switch to a music source.  It is possible to get to the setup screen (via left-arrow) whilst not connected, to select an alternative source (eg. MySqueezebox.com), without sending a WOL to the local music source.

Now that music library source switching is meant to be transparent on Touch/Radio, I don't think the WOL magic packet should be sent automatically when pressing the power button, because there isn't the same obvious concept of being currently connected to a particular server.  I think that only when attempting to play something (or use a facility) from a music source should it send the WOL packet.  i.e. only after the "Switch to music source" dialog comes up and the user selects to do the switch.
Comment 1 James Richardson 2009-10-05 16:59:36 UTC
I noticed the same thing happens sometimes with Baby and Controller now.
Comment 2 KDF 2009-12-30 13:12:25 UTC
*** Bug 14919 has been marked as a duplicate of this bug. ***
Comment 3 Chris Owens 2010-03-15 18:05:04 UTC
7.4.x milestone is in the past
Comment 4 Felix Mueller 2011-01-13 09:05:17 UTC
I cannot reproduce this.