Bugzilla – Bug 5033
Stopping Rhapsody station still consumes bandwidth
Last modified: 2008-11-05 12:51:52 UTC
When using the Rhapsody service via SqueezeNetwork to listen to stations, stopping the SqueezeBox via web interface or remote stops the stream, but bandwidth continues to be used at the rate of about 128k until the SqueezeBox is actually powered off via either web interface or remote. This issue exists for both SB series 2 and 3.
there is some bandwidth required in order to control the display. the squeezebox has no ability on it's own, not even the clock; that is delivered by squeezenetwork or slimserver.
I understand that there is overhead for clock, etc. But with the power on and the station stopped (and no music playing), it uses 128k. When I turn the power off (via the red button on the remote or the web interface), bandwidth consumption drops to near-zero, but the clock continues. I still think this is a bug.
if turning back on, does the usage go up to 128k again? Is the display scrolling?
Created attachment 1985 [details] SNMP router bandwidth usage
I will take a look at this tomorrow.
When you are stopping the stream, are you just pausing it, or fully stopping it by holding pause? Can your firewall display the states of connections? After stopping, do you see any open connections from your player to either secure-direct.rhapsody.com (207.188.5.19) or a web server on port 80?
I am stopping the stream by hitting the Stop button in the UI. The graph I attached was from SNMP, which does not look at connection states.
OK, well I can't reproduce this, so I was hoping you could see if there were any open connections left after you pressed stop. For me, the HTTP connection to the audio file is closed as soon as stop is pressed.
Will review the outstanding SN bugs after 7.0 ships.