seems strange that all ports should be opened. I think there are
firewalls that do reply ports are opened when in fact they are 
blocking them. Or else, do you know what server(s) listen to all except
3484/udp?

I am generally bored with firewalls, I avoid them like plague on the
Lan. My recommendation, for testing, would be to stop and clear the
firewall, and see if the controller sees something. Then you'll know
for sure the problem is with the firewall.

BTW I currently have 2 servers, in 2 separate local lans. Right now,
because of the way my firewall is setup, I can see this in the log:
"(blocked) 172.31.200.10, port 3483 -> 255.255.255.255, port 3483       UDP".
This is my 2nd SC server trying to advertise its presence over the lan.
It sends broadcast packets over the 0.0.0.0 (=local) network. I am not
sure it does only this, or in addition to broadcasting to
172.31.255.255, the explicit broadcast address for the network it's in.
Nevertheless, my firewall (ipfw) doesn't seem to accept 255.255.255.255
as a local destination, so it blocks and logs. Perhaps your firewall
does the same ?


-- 
epoch1970

Daily dose delivered by: 2 SB Classic (fw 130), 1 SB Boom (fw 50) •
SqueezeCenter 7.3.4 (Debian 5.0) with plugins: ContextMenu,
SaverSwitcher by Peter Watkins • Server Power Control by Gordon Harris
•  WeatherTime by Martin Rehfeld • IRBlaster by Gwendesign (Felix) •
FindArt, CDplayer by bpa • BBC iPlayer, SwitchPlayer by Triode •
PowerSave by Jason Holtzapple • TrackStat by Erland Isaksson.
------------------------------------------------------------------------
epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711
View this thread: http://forums.slimdevices.com/showthread.php?t=77129

_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix

Reply via email to