ntpd on TCP Port 2000

General discussions about Little Snitch
Post Reply
jimwall
Posts: 3
Joined: Fri Oct 12, 2007 3:47 pm
Location: Brooklyn

ntpd on TCP Port 2000

Post by jimwall » Fri Oct 12, 2007 6:01 pm

Hi

LS keeps flagging ntpd using TCP port 2000 at startup. It never seems to call this again. Should I allow this?? I googled it and didn't find anything conclusive. Everything I can find just calls for port 123. I've read the man pages and don't see anything there.

Any help would me most appreciated


jimwall

Guest

Post by Guest » Mon Nov 05, 2007 10:56 pm

Network Time Protocol Daemon is my guess. Seems safe to allow forever.

jimwall
Posts: 3
Joined: Fri Oct 12, 2007 3:47 pm
Location: Brooklyn

Post by jimwall » Tue Nov 06, 2007 2:23 am

Thanks :D

mustbjones
Rank 2
Rank 2
Posts: 40
Joined: Tue Nov 06, 2007 7:42 pm

Post by mustbjones » Tue Nov 06, 2007 7:45 pm

A quote from the developer when I emailed the same question: The name of port 2000 was always CALLBOOK. The name is taken from the file /etc/services located at your startup disk. We have still no clue why ntpd wants connect to port 2000. Therefore I personally always deny this connection. Time synchronization seams to work fine also with blocking this callbook connection.

jimwall
Posts: 3
Joined: Fri Oct 12, 2007 3:47 pm
Location: Brooklyn

ntpd

Post by jimwall » Tue Nov 06, 2007 9:23 pm

Thanks again.

I found this


The findinterface() function in ntpd/ntp_io.c uses TCP port 2000
to find which interface to use to send packets to a given address.
This is a major problem for any system behind a firewall which has
not opened this port to outgoing TCP connections. An alternative
needs to be found to identify an outgoing interface.



on the ntp bugzilla site. I don't know what to make of it.

Post Reply