bpa wrote:
> All LMS servers who "hear" the broadcast will respond - this way player
> is told of all available LMS servers and IP address - user can then pick
> on player which LMS to connect.
Could be getting warm here. By what means does the Player get the
response(s) from the LMS(s) ?
If that is also occurring over UDP, then we need to set up another pair
of socats to complete a fully symmetric UDP bridge (ie, UDP datagrams
transmitted by the Player on the local LAN get relayed to the remote
server's LAN with one pair of socats, and UDP datagrams transmitted by
LMS on the remote LAN are relayed to the local LAN so they can be
received by the Player). As it stands now, we are only relaying UDP
packets from the Player to the LMS. I believe we would need to kick off
2 more, as follows:
On player LAN:
Code:
--------------------
socat tcp4-listen:34831,reuseaddr,fork UDP:localhost:3483
--------------------
On LMS LAN:
Code:
--------------------
socat -v -T3600 udp4-recvfrom:3483,reuseaddr,fork tcp:localhost:34831
--------------------
Well, I will try this and report back.
> If player is not on same segment as LMS then LMS will not hear the
> broadcast.
I think in our situation this isn't the case, based on verbose output
I'm seeing from ssh and the socats. As soon as SqueezePlay starts, I see
activity that the local socat has seen a UDP packet on 3483 and has
relayed it to TCP 34831; immediately ssh reports seeing data on TCP
34831 and relays that to the remote server side; and finally the remote
socat reports seeing data on TCP 34831 and relays that to UDP 3483.
Therefore, in the Player > LMS direction, I think things are working as
expected.
> Player can always choose which LMS server to use (even if not on same
> LAn segment) by defining the LMS IP address.
That's why this discovery protocol seems strange to me in this case. We
don't need discovery, because we have explicitly specified a Remote
Library with the IP address of the LMS (127.0.0.1), and ensuring TCP
ports 9000 and 3483 are relayed. SqueezePlay should "believe" these
settings and just connect to LMS. Why does it need to go through the UDP
discovery process when we have defined the LMS IP address?
Anyway... probably should just run Wireshark on the LMS LAN and capture
the entire network dialog between SqueezePlay and LMS on every port :)
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
