GNOME Bugzilla – Bug 694797
dualprotocol: NetworkManager should pass on the NTP Server from DHCP to the underlying system
Last modified: 2013-08-13 20:41:45 UTC
Forwarded from a downstream bug https://bugzilla.novell.com/show_bug.cgi?id=798886 dhcp based network connections request ntp servers from the dhcp server if present and configured on the client side. NetworkManager version 0.9.4 do not provide those settings to the netconfig ntp-runtime module, which works in traditional if mode (and I did not just see anything in 0.9.8 doing that)
Created attachment 237524 [details] [review] added ntp server to NetworkManager netconfig file Patch frmo the downstream bug tracker,
Any reason we can't run this as a dispatcher script instead of a code addition? The dispatcher script would grab the NTP servers out of its environment on the 'up' and 'dhcp4-change' events. That's a good way to do it for now, and in the future we're planning to add more flexible support for DNS "plugins" which would report changes to the consolidated DNS information which then an enhanced NTP NM plugin would use.
I think the main issue is that NM is not passing down all the DHCP Answers to the dispatcher scripts, or does it? If I'm mistaken: do you have any example scripts at hand?
NM will pass whatever it got from dhclient to the dispatcher scripts on the 'up' or 'dhcp4-change' or 'dhcp6-change' events. However, investigating, there is one case where this doesn't happen. Since iPv4 and IPv6 are run in parallel, and whichever one completes first will trigger the 'up' event. So, if IPv6 completes first and triggers the 'up' dispatcher script event, that won't contain any information about IPv4, because IPv4 may not be done yet. THen, when IPv4 does complete the *first* time after IPv6 is successful, NetworkManager does not trigger a dispatcher event, and thus the DHCP information will not be sent to the scripts. This is a bug. A temporary workaround would be to disable IPv6 if it's not used.
NM bugzilla reorganization. Sorry for the bug spam.
Could be merged with bug 689742?
(In reply to comment #4) > However, investigating, there is one case where this doesn't happen. Since > iPv4 and IPv6 are run in parallel, and whichever one completes first will > trigger the 'up' event. So, if IPv6 completes first and triggers the 'up' > dispatcher script event, that won't contain any information about IPv4, because > IPv4 may not be done yet. THen, when IPv4 does complete the *first* time after > IPv6 is successful, NetworkManager does not trigger a dispatcher event, and > thus the DHCP information will not be sent to the scripts. This is a bug. > > A temporary workaround would be to disable IPv6 if it's not used. There's already a bug report for that. *** This bug has been marked as a duplicate of bug 89741 ***
(In reply to comment #7) > > *** This bug has been marked as a duplicate of bug 89741 *** That is very likely the wrong bug... I fail to see how NM and galeon are related.
(In reply to comment #8) > (In reply to comment #7) > > > > *** This bug has been marked as a duplicate of bug 89741 *** > > That is very likely the wrong bug... I fail to see how NM and galeon are > related. Thanks! Also, we don't keep such old bugs in NetworkManager ;). *** This bug has been marked as a duplicate of bug 689741 ***