Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The ntpd daemon dropped incoming NTP packets if their source port was lower than 123 (the NTP port). As a consequence, clients behind Network Address Translation (NAT) were unable to synchronize with the server if their source port was translated to ports below 123. With this update, ntpd no longer checks the source port number, and clients behind NAT are now able to correctly synchronize with the server.
Description of problem:
If NTP requests goes through NAT, NAT changes srcport of packet to something random. Sometimes it's below 123 and ntp drops it without any logging.
Source code says (ntpd/ntp_proto.c):
332 /*
333 * Bogus port check is before anything, since it probably
334 * reveals a clogging attack.
335 */
336 sys_received++;
337 if (SRCPORT(&rbufp->recv_srcadr) < NTP_PORT) {
338 sys_badlength++;
339 return; /* bogus port */
340 }
Version-Release number of selected component (if applicable):
ntp-4.2.6p5-1.el6.centos.x86_64
...but srcrpm for centos7 shows, that it's version have the same problem (ntp-4.2.6p5-18.el7.centos.src.rpm)
How reproducible:
Always when packet srcport is lower than NTP_PORT (123).
For testing purposes you can create NAT that changes srcport to - for example - 121.
Steps to Reproduce:
1. Install NTP server on server-host and client on client-host
2. Configure NAT for client-host so NTP will exit host with srcport lower than 123. (or you can use simple python ntp client found here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691412)
3. Run `ntpq -p` on client-host. NTP is always in state .INIT. cause server dropped all requests. No logs at all in syslog. No debuglogs even with debuglevel=10.
Actual results:
NTP drops requests without any logging.
Expected results:
Packets are not dropped, or this option is configurable and should log something. Took me few weeks to debug why some servers have problems with ntp :(
Additional info:
http://lists.ntp.org/pipermail/hackers/2009-December/004758.htmlhttp://bugs.ntp.org/show_bug.cgi?id=2174
Debian already fixed that:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691412
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-1459.html
Description of problem: If NTP requests goes through NAT, NAT changes srcport of packet to something random. Sometimes it's below 123 and ntp drops it without any logging. Source code says (ntpd/ntp_proto.c): 332 /* 333 * Bogus port check is before anything, since it probably 334 * reveals a clogging attack. 335 */ 336 sys_received++; 337 if (SRCPORT(&rbufp->recv_srcadr) < NTP_PORT) { 338 sys_badlength++; 339 return; /* bogus port */ 340 } Version-Release number of selected component (if applicable): ntp-4.2.6p5-1.el6.centos.x86_64 ...but srcrpm for centos7 shows, that it's version have the same problem (ntp-4.2.6p5-18.el7.centos.src.rpm) How reproducible: Always when packet srcport is lower than NTP_PORT (123). For testing purposes you can create NAT that changes srcport to - for example - 121. Steps to Reproduce: 1. Install NTP server on server-host and client on client-host 2. Configure NAT for client-host so NTP will exit host with srcport lower than 123. (or you can use simple python ntp client found here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691412) 3. Run `ntpq -p` on client-host. NTP is always in state .INIT. cause server dropped all requests. No logs at all in syslog. No debuglogs even with debuglevel=10. Actual results: NTP drops requests without any logging. Expected results: Packets are not dropped, or this option is configurable and should log something. Took me few weeks to debug why some servers have problems with ntp :( Additional info: http://lists.ntp.org/pipermail/hackers/2009-December/004758.html http://bugs.ntp.org/show_bug.cgi?id=2174 Debian already fixed that: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691412