I've found the reason and a workaround to my problems
- The controler will always use UDP3483 when required to access a new
SqueezeCenter, even if the IP address of the squeeze center is manually
enterer
- But it requires to do this only once, I guess for getting some
parameters. Once it is done,
This is what I've done : setting the IP address of the server in the
"Music Source" option of the menu. But it seems that the controller
insist on starting with a first UDP packet to this IP address and will
not proceed until he gets a response - see the log attached below (the
.100 is the control
As radish says you shouldn't need UDP. It will try to discover servers
using UDP, but if you define the server manually in the music source menu,
you should be fine without.
Michael
___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.
I saw this using ethereal when I was trying to analyze what was going
wrong. You might be very right that it is just used for discovery, the
problem is that I even cannot pass this stage because once I did enter
the IP address of my PuTTY client as the squeezecenter ID, the first
thing the control
What UDP traffic are you seeing? I was under the impression UDP was only
used for the discovery protocol, which is optional.
--
radish
radish's Profile: http://forums.slimdevices.com/member.php?userid=77
View this thread:
Hi - I want a duet to use my squeezecenter server from a remote
location. This is working fine by opening ports 9000 and 3483 in my
router, but I don't like having open ports like this.
Basically I always access my network through SSH.
Unfortunately, it seems that the controller is using UDP to
