Bugzilla – Bug 773
Split service ports for webserver and streaming music
Last modified: 2011-11-06 23:24:15 UTC
Basically.... right now if I want to listen to my streaming music over the Internet (or give out to friends to listen to what I am streaming).... it has to run on the same port that my webserver listens for me to configure playlists, etc...... bad. I would love to see two seperate fields making it possible for me to choose which ports listen for each of the service individually... Example: stream media over 80 (only allow that port to reach the stream.mp3 or whatever you can implement) but the webserver for music management only listens on 8080 -Both fields should be user defined and unrestricted. -Awareness information about security issues would be helpful when selecting ports.
I'm not quite following you on this. What situation requires the ports to be different? Do you want to stream to some but disallow access to the web interface? Or is it the other way around? Or am I missing it altogether?
Sorry for the confusion... You had it right the first time. I really want to be able to stream music for people, but not give them access to the web interface. I want to be able to tell friends to connect to http://10.1.1.1/stream.mp3 to listen to what I am streaming but give them no control over what they want to listen to using the interface.... I can't find a default player setting to provide this... I would want it so each person that connects to me gets the default playlist right away, unless I give them access (re: multiple account bug that is already submitted) Hope this helps clarify. Thanks!
if I'm understanding this correctly, I think it is important to note that each player as it connects is given its own client id with its own blank playlist (or its previous playlist if it has one from before). you'd have to add a playlist to each new client and start playback from the web interface for them. Slimserver does not provide a single stream to multiple clients.
I think you hit it right there. I guess my true request is to allow one stream for many unknown clients. The ability to create a playlist that could allow any IP to connect to and listen to a defined playlist, with or without authentication. They would only be able to listen, no controls over the playlist. Justification. To be able to provide a link on a personal website that says, click here to stream what I am listening to these days. I think this would be a huge advancement for the software and increase the usage big time. I believe people would love and drool over the fact that they could site up their own mini-radio stations for friends, etc, but still having all of the other features of the software! Loads of ways that this could be implemented and hopefully could be pretty easy? I would love to be able to create a default player with playlist for anyone that connects to stream2.mp3.... this way it wouldn't affect all the other functionality that everyone loves. But just expand to be able to allow random people to listen in easily without configuration and being able to force them to listen to a defined playlist! Definitely high on my list! =) What do you think? Thanks for reading and being open to feedback. I am very pleased with my Squeezebox but would be able to recommend it much easier if people could stream to many people such as poorly described above.
This is a good idea. The way to do this is to allow a second port to be open for streaming-only connections.
Marking items that aren't going to be addressed immediately in 6.1 as future. Please update if this is in error or the bug has already been addressed.
Has not be addressed yet. Still have my fingers crossed that this will get bumped up soon! Thanks!
Any idea when we might be able to get this in a release? =) Thanks!
keep alive! =)
Dean doesn't work here any more :)
Unassigned bugs cannot have a priority.