Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
NTP is a UDP-based protocol. I'm not aware of any implementations of NTP over TCP. The reason is that NTP submits one query and gets one response. That is very quick with UDP, but if you were to do that with TCP it would have to setup a whole connection just to send two packets, not very effecient...
Hi,
"netstat -an" on my NT-box displays listeners both on UPD/123 and TCP/123. The same command list only UPD/123 on my Linux-box.
"cat /etc/services | grep ntp" on my linux-box lists:
ntp 123/tcp
ntp 123/upd
I don't regard this definitions being humbug. There should be a way to enable this. I need this to enable DTSS under VMS to synchronize to my linux-box.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
From /usr/local/share/doc/ntp/debug.html:26:
Quote:
Note that NTP does not use TCP in any form.
From /usr/local/share/doc/ntp/debug.html:158:
Quote:
NTP is specifically designed to use UDP and does not respond to TCP.
Just because /etc/services has reserved both UDP and TCP does not mean they're both actually used. Many services reserve the same port on both protocols, but only use one of them (they're both reserved to avoid confusion). For instance Windows runs NetBIOS over UDP and NetBIOS over TCP, but they used different port numbers. Even though they used different port numbers, each of them reserves both UDP and TCP, although only one is used in practice.
Even though your Windows box is bound to both ports, I seriously doubt TCP is used. Run Ethereal on the Windows box while you syncronize time and you'll see this is true.
Having NTP on TCP makes no sense from my point of view (and by all means, someone correct me if I'm wrong!!!). TCP provides error correction whilst UDP doesn't... imagine some packets are lost along the way... why would you want to have a time information resent??? It would have no use anyway...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.