maweber wrote:
> do you think this is fine so far?
Can't say.
The response from LMS server to a broadcast packet will be a UDP packet.
The IP address of the server which sent the packet is a standard part
of UDP header (i.e. source address) - it is NOT in the body..
bpa wrote:
>
> See gotTLVrequest in Discovery.pm file
> https://github.com/Logitech/slimserver/blob/public/7.9/Slim/Networking/Discovery.pm
>
I think LMS does just send back a confirmation of some sort, but not its
IP?
So as this is a NAT, the Radio should think it got an OK from the VPN
bpa wrote:
> Nope - it's just each player on startup sends a UDP broadcast message on
> port 3483 and any LMS server who hears the packet sends back a reply
> indicating its name (IP address of LMS server is part of the packet
> header) and a few other bits of info if requested.
>
> See
Its often even simpler disabled UDP broadcast firewall on port 3483 and
9000 .
If thats not possible keep the server at a fixed IP or both for most
stable setup .( Yeah keep both players and server a static IP )
You must a have complex network . A campus network ? or something . Set
up your own
maweber wrote:
> I suspect LMS to use a protocol that is so old that its name is long
> forgotten... ;-)
Nope - it's just each player on startup sends a UDP broadcast message on
port 3483 and any LMS server who hears the packet sends back a reply
indicating its name (IP address of LMS server is
maweber wrote:
> Hi
> Does somebody know how to manually advertise an LMS by use of avahi or
> something alike?
> Thanks!
> Best
> Manu
What do you want to advertise? The whole music collection? A player
stream?
"To try to judge the real from the false will always be hard. In this
Hi
Does somebody know how to manually advertise an LMS by use of avahi or
something alike?
Thanks!
Best
Manu
maweber's Profile: http://forums.slimdevices.com/member.php?userid=64980
View this thread:
