I have used my mobile to connect remotely to LMS using ssh (using a public key exchange for security). I use Squeeze Commander and Squeeze Player for this, and it works well. Apart from the security and router set-up all I have to do is set up local ports 9000 and 3483 in ssh (using the -L parameter) on the mobile to route requests to those ports to my remote server's address.
I also managed to get this working using squeezelite and a web browser on my laptop using the same technique. Both are connected using (local) address 127.0.0.1 which is intercepted by ssh and forwarded to LMS. The full ssh syntax is:
I then tried to do this with squeezeplay on the same laptop. When I try to connect to 127.0.0.1 the playing side works OK (and can be controlled by a web browser on the laptop connected to port 9000). However, the squeezeplay control side fails to complete the connection and cannot be used. The 127.0.0.1 address reamins in the settings configuration, but cannot be used to control LMS.
I have tried to determine the reason for this but (so far) failed. I have tried using firewall logging to work out what is happening but sorting the wood from the trees has proved beyond me thus far. I have tried with both laptop and LMS firewalls off, just in case, and also with my LMS IP-based security switched off. Neither of these helped. LMS on the server see the requests as local (from 127.0.0.1) which is what the ssh server is using.
I have wondered whether an additional information exchange is needed with squeezeplay on one or more different ports for the control side which are not specified in my ssh command. This would explain why the playing side (on 3483) works but the control side fails to complete. However, I haven't been able to find out what this might be.
Has anyone else ever managed to get squeezeplay to work in a similar way?
I also managed to get this working using squeezelite and a web browser on my laptop using the same technique. Both are connected using (local) address 127.0.0.1 which is intercepted by ssh and forwarded to LMS. The full ssh syntax is:
Code:
ssh -L localhost:9000:LMS-local-IP-address:9000 -L localhost:3483:LMS-local-IP-address:3483 LMS-dns-addressI have tried to determine the reason for this but (so far) failed. I have tried using firewall logging to work out what is happening but sorting the wood from the trees has proved beyond me thus far. I have tried with both laptop and LMS firewalls off, just in case, and also with my LMS IP-based security switched off. Neither of these helped. LMS on the server see the requests as local (from 127.0.0.1) which is what the ssh server is using.
I have wondered whether an additional information exchange is needed with squeezeplay on one or more different ports for the control side which are not specified in my ssh command. This would explain why the playing side (on 3483) works but the control side fails to complete. However, I haven't been able to find out what this might be.
Has anyone else ever managed to get squeezeplay to work in a similar way?