** Description changed: + [Impact] + + If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. + This is occurring in our environment due to NAT. + + [Test Case] + + The problem can easily be reproduced by having an iptable postrouting + nat forcing the source port to be under 123 set on the client. + + [Regression Potential] + + The patch comes from upstream + [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] + + A testfix[1] package has been provided to the community before the SRU + process to bring more confidence for the patch. Positive feedbacks has + been given by the community to confirm the patch addressed the bug + [comment #7] + + [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 + + [Original description] + [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please?
** Description changed: [Impact] - If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. - This is occurring in our environment due to NAT. + If an NTP client sends a request with a source port less than 123, the + packet is silently ignored by ntpd. This is occurring in our environment + due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream + The patch comes from upstream [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream - [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] + The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174] A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174] + The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
