Bug 1640 - Can Softsqueeze open remote port 9000 as a local port?
: Can Softsqueeze open remote port 9000 as a local port?
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Softsqueeze
: 6.1.0
: All Windows (legacy)
: P2 enhancement (vote)
: ---
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-06 16:43 UTC by Nestor
Modified: 2008-09-15 14:37 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nestor 2005-06-06 16:43:19 UTC
Sometimes is useful to change the Maximum bit rate for Softsqueeze player.
Depending on the network being used at the time one may need to go from 196 or
128kbs to 64kbs. 
Usually I use putty to connect with SSH to the server running Slimserver, and
make  ports 9000 and 3482 available as local ports in my laptop, so i can
connect with a browser to http://localhost:9000  to the server and change
remotely any configuration I need.
Is it possible to have Softsqueeze put the 9000 port as a local port on the
laptop (a la putty) so theres no need to use anything else besides softsqueeze
and a browser for configuring remotely Slimserver?
Comment 1 Michael Herger 2005-06-07 00:56:51 UTC
When I use the softsqueeze built-in ssh client to connect to my server, the necessary ports are tunnelled 
automatically. I can connect to localhot:9000 without additional manipulation. See softsqueeze's network 
settings.
Comment 2 Nestor 2005-06-07 05:04:04 UTC
Are you saying I should have checked network settings first????
:-)

For sure, it works perfectly using the "Forward additional ports" = 9000...

Im pretty sure I tried this before, some time ago, maybe I was having another
issue and it didnt work, and I was left with the impression that Softsqueeze was
not prepared for this... 

Closing the bug... Thanks Michael!!
Comment 3 KDF 2005-06-07 14:34:18 UTC
*** Bug 1638 has been marked as a duplicate of this bug. ***
Comment 4 Chris Owens 2006-06-16 14:42:32 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.