Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a clean Debian 7 installation, and I manually entered the following lines in /etc/ntp.conf:

interface ignore wildcard
interface listen <local_nic_ip>

Hoping that NTP will no longer listen on UDP6, but after a restart, it still does:

5:udp        0      0 <local_nic_ip>:123       0.0.0.0:*                           9172/ntpd       
6:udp        0      0 127.0.0.1:123           0.0.0.0:*                           9172/ntpd       
8:udp6       0      0 ::1:123                 :::*                                9172/ntpd

The command line of NTP shows nothing unusual:

/usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 121:130

How to stop NTP from listening on that UDP6 port?

share|improve this question
    
What is your problem with listening? Isnt it enough for you if ntpd uses ipv4 for DNS resolution? Im asking this as ntpd will always bind to all wildcard addressess. But you can specify IPv4 only DNS, use firewall to block ip6 traffic, or use ntp.conf to restrict ipv6 traffic. –  Semirke Feb 5 at 13:44
    
@Semirke It makes me nervous when I tell a program to do something, yet it does something totally unexpected. Why does NTP listen on UDP6 when I told it not to? –  Howard Feb 5 at 13:49
1  
It's listening on localhost on both IPv4 (127.0.0.1) and IPv6 (::1). Are you sure you haven't configured it to listen on localhost? Or maybe it always listens on localhost. Not sure about that. In either case it will not hurt. –  Sander Steffann Feb 5 at 15:10

2 Answers 2

up vote 5 down vote accepted

I have been able to disable IPv6 for NTP on my Debian 5/6/7 and Ubuntu 12.04 this way :

Edit file /etc/default/ntp and replace

NTPD_OPTS='-g'

by

NTPD_OPTS='-4 -g'

Then, you can keep your directives in ntp.conf, they are not ignored :

interface ignore wildcard
interface listen <local_nic_ip>
  • Without interface ignore wildcard NTP will also listen on 0.0.0.0
  • Without interface listen <local_nic_ip> NTP will only listen on 127.0.0.1 (of course)

This will results in :

# netstat -anp | grep :123
udp    0      0 192.168.0.38:123     0.0.0.0:*                 2901/ntpd
udp    0      0 127.0.0.1:123        0.0.0.0:*                 2901/ntpd

Also, i confirm that OpenNTPD listens where you ask him to listen more friendly (no need to edit multiple config files). By default it listens nowhere until you configure it to do so (very secure) ;)

In config file, just uncomment line

listen on 127.0.0.1

And add line

listen on <local_nic_ip>

Results in :

# netstat -anp | grep :123
udp   0    0 192.168.0.38:123     0.0.0.0:*                 8581/ntpd
udp   0    0 127.0.0.1:123        0.0.0.0:*                 8581/ntpd
share|improve this answer
    
hi, ntpd -4 will only make it to do ipv4 DNS queries. Ntpd will keep listening on IPV6. Also I agree with your OpenNTPD notion, that you can configure to not listen on ipv6. –  Semirke Feb 5 at 21:22
1  
@Semirke I agree with you about the -4 option and DNS queries, but the fact is that, by doing this, i have no more listener on my ipv6 interfaces for ntp (assuming i trust netstat output). –  krisFR Feb 5 at 21:31

If you consider this a bug (and I certainly do: ntpd is ignoring a configuration directive) you're going to have to take it up with the package maintainer or upstream authors. I don't believe any of them hang out here - refer to the package information for their contact details.

Alternatively you could try another NTP implementation (like OpenNTPD - I've not used it personally, but the OpenBSD folks tend to be absolutely paranoid about security, so I imagine it only listens where it's told to).

As Sander pointed out though, your NTP daemon is listening on localhost (127.0.0.1 & ::1) - If you're worried about being hacked from localhost you probably have bigger problems than your NTP daemon.
I'm a bit miffed that the daemon is ignoring a configuration directive, but I wouldn't consider this a serious security concern.

share|improve this answer
1  
Always be wary of recommendations/suggestions when the person giving the recommendation confesses to never having used the product in question. If you need an alternative to ntp reference implementation try chrony. It is important to note that chrony and openntpd do not support a lot of the extended features of the reference implementation. –  dfc Feb 6 at 2:24
1  
@dfc Beware of recommendations in general: All software recommendations should be evaluated for suitability in a given environment before blindly implementing them. In this case I know a number of folks who use OpenNTPD (on OpenBSD), and they speak very well of it as a "basic NTP daemon". Obviously if you're using features of the reference implementation that it doesn't support it's not going to work for you. –  voretaq7 Feb 6 at 20:50

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.