Hello Richard, or anyone else affected, Accepted ntp into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.6.p5+dfsg- 3ubuntu8.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: ntp (Ubuntu Wily) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: ntp (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus Status in NTP: Fix Released Status in ntp package in Ubuntu: Fix Committed Status in ntp source package in Precise: Fix Committed Status in ntp source package in Trusty: Fix Committed Status in ntp source package in Wily: Fix Committed Status in ntp source package in Xenial: Fix Committed Status in ntp package in Debian: New Bug description: [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. [Development Fix] Fixed by merge of NTP of newer upstream release that includes the fix. Stuck in dep-wait in xenial-proposed due to an unrelated issue (pps- tools MIR or other resolution). [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. Setup: ==> NTP server = y.y.y.y ntp.conf configured to be a server. ==> NTP client = x.x.x.x "ntpdate" used to submmit requests #iptable setup to force src port to be lower than 123 iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source x.x.x.x:100-122 ## On the client, set to force src port < 123 (without patch) $ ntpdate y.y.y.y ntpdate[<PID>]: no server suitable for synchronization found ## On the client, set to force src port < 123 (with patch) $ ntpdate y.y.y.y ntpdate[<PID>]: adjust time server y.y.y.y offset -0.028483 sec [Regression Potential] 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? To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
