I've followed your instructions but SqueezePlay still can't connect to
my remote LMS via the assorted ssh & udp plumbing.
I am running ssh and the 2 socats with verbose logging and I certainly
see a lot of activity from all 3 programs. When launched, SqueezePlay
displays "Connecting to 127.0.0.1" and spins for about 30 seconds, then
gives up with the message "We couldn't connect to 127.0.0.1". As
mentioned, during this time there is a lot of activity logging visible
from ssh and socat.
Doesn't the player/server discovery protocol use UDP broadcast packets?
If so, are the socats correctly relaying those? They seem to only be
relaying unicast UDP data on 3483 in one direction from the player to
the server side. Does LMS reply back using UDP 3483, or with UDP
broadcasts? If so, we might need another 2 instances of socat to provide
the UDP backchannel... ?
The only slight difference I can see in my configuration is that I am
running LMS on TCP port 9500 instead of 9000. Accordingly, my ssh local
forward argument for that port is
Code:
--------------------
localhost:9000:LMS-local-IP-address:9500
--------------------
Would that break anything? In any case I am not seeing any activity on
either ports 9500 or 9000...
Thanks.
------------------------------------------------------------------------
nico's Profile: http://forums.slimdevices.com/member.php?userid=672
View this thread: http://forums.slimdevices.com/showthread.php?t=108734
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
