Squeezeplay desktop over SSH tunnel - possible?

[jmbylsma]

I figured a workaround for this and posted a bunch of links at http://forums.slimdevices.com/showth...946#post696946. I hope people don't mind me posting this twice in the forums, but I hope this helps people struggling figure out their issues!

[dagordon]

Squeezeslave doesn't use/require UDP and with the port option (-P/--port) you can "punch" a hole through restrictive office firewalls and then use a port redirect on your home firewall to the SBS server port 3483. You don't even need to use ssh.

That doesn't help those of use who are trying to get physical players based on SqueezePlay working over SSH.

Anyway, SoftSqueeze works over SSH (in fact has a built-in client).

[ralphy]

Squeezeslave doesn't use/require UDP and with the port option (-P/--port) you can "punch" a hole through restrictive office firewalls and then use a port redirect on your home firewall to the SBS server port 3483. You don't even need to use ssh.

[iolaus]

I too, would like to request that the need for UDP in SqueezePlay be removed.

[dagordon]

Are there any plans to make SqueezePlay (and players based on it, like the Touch) able to work over an SSH tunnel?

Previous devices (Boom, SB3, etc.) are able to do this; it's really unfortunate that SqueezePlay breaks this functionality.

[zimmer62]

Bump.

[pvilliger]

I managed to setup a tunnel to with putty. The local ports 9000 and 3483 are forwarded to the squeezecenter (current nightly) running on ubuntu. It is possible to control the squeezecenter through the web interface and also connect the softsqueeze (version 3.7).

Trying to connect the squeezeplay to 127.0.0.1 (localhost) fails, but the squeezeplay is recognized by the squeezecenter. With the web interface it is possible to play music on squeezeplay, but without the ability to control the volume.

Any hints how to fix this?

Paul

[herbman]

Any updates on this? Still impossible to do?

[nathan_h]

I was using SoftSqueeze, but after a computer upgrade at work, and now upgrading my SqueezeCenter, I appear to have lost the ability to 1) use SoftSqueeze and 2) listen to my music via an SSH tunnel.

Please help!

Can you get to your server from other internet clients, but just not from your work computer / network?

[ronwr]

Interested in Squeezeplay + SSH Tunnel

I was using SoftSqueeze, but after a computer upgrade at work, and now upgrading my SqueezeCenter, I appear to have lost the ability to 1) use SoftSqueeze and 2) listen to my music via an SSH tunnel.

Please help!

[dagordon]

I'm interested in using SqueezePlay over an SSH tunnel too. Has there been any progress on this issue? Or is there any workaround? I'm using WinSSHD on my Windows server at home, and I'm using Tunnelier as the SSH client. I don't think there's any way of tunneling the UDP port 3483 with this setup, but maybe I'm missing something.

Thanks

[Punga]

Hi,

I'm interested into using SqueezePlay via SSH tunnel too...

As SSH can't forward udp but tcp only through it's common tunnel feature SqueezePlay/Controller will not work (unless this has changed very recently)

has there been any change to SqueezePlay so far - or is there any workaround?

Cheers
Punga

[schiegl]

Hi Richard - this was my understanding, but (see me other post) I've not been able to do so. I have always entered the IP address of the squeezecenter manually in the "Music Sources" menu, but it never worked until I opened UDP3483. And, strangely enough, UDP3483 was only needed ONCE. After the "SSH tunneled" squeezecenter has been "registered", I coudl close it, and it would still work after everything has been reset (controler, receiver & PC hoisting the squeezecenter) - Softsqueeze never showed this problem. I really think there is a "small bug" over here

For the sake of completeness - and to confirm you findings: Last week i took my Controller to another location which is connected to my SC using a VPN. The SBC couldn't connect until i allowed udp/3483 to pass the tunnel. Entering SC's IP address as additional music source didn't work.

So to access the Webinterface, use my SB3 and the SBC i need these protocols/ports:

tcp/3483 + tcp/9000
udp/3483

To get on-topic at last: As SSH can't forward udp but tcp only through it's common tunnel feature SqueezePlay/Controller will not work (unless this has changed very recently)

kind regards,
Markus

P.S. It was _no_ problem SC was hidden behind a NAT-address and therefore was not accessible through its real IP address.

[philippe_44]

Hi Richard - this was my understanding, but (see me other post) I've not been able to do so. I have always entered the IP address of the squeezecenter manually in the "Music Sources" menu, but it never worked until I opened UDP3483. And, strangely enough, UDP3483 was only needed ONCE. After the "SSH tunneled" squeezecenter has been "registered", I coudl close it, and it would still work after everything has been reset (controler, receiver & PC hoisting the squeezecenter) - Softsqueeze never showed this problem. I really think there is a "small bug" over here

[rtitmuss]

If you go to "Settings > Music Source > Other Server", you should be able to enter 127.0.0.1 and SqueezePlay will use the ssh tunnel. Normally it used udp 3843 to discover SqueezeCenters running on the local LAN.

Richard