netdev - Re: regression when connecting to ipv6 localhost

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 14 Oct 2012 23:35:42 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Jan Hinnerk Stosch <janhinnerk.stosch@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: regression when connecting to ipv6 localhost

On Sun, 2012-10-14 at 23:21 +0200, Jan Hinnerk Stosch wrote:
> 2012/10/14 Eric Dumazet <eric.dumazet@...il.com>:
> > On Sun, 2012-10-14 at 22:39 +0200, Jan Hinnerk Stosch wrote:
> >
> >> ntpd    368  ntp   16u     IPv4              10453      0t0    UDP *:ntp
> >> ntpd    368  ntp   17u     IPv6              10454      0t0    UDP *:ntp
> >> ntpd    368  ntp   18u     IPv4              10460      0t0    UDP
> >> localhost.localdomain:ntp
> >> ntpd    368  ntp   19u     IPv4              10461      0t0    UDP
> >> hinniepc.fritz.box:ntp
> >> ntpd    368  ntp   20u     IPv6               8775      0t0    UDP
> >> [fe80::922b:34ff:fe33:c292]:ntp
> >> ntpd    368  ntp   21u  netlink                         0t0  10463 ROUTE
> >
> > Hmm, your ntpd doesnt listen normally to ::1 UDP 123
> >
> > grep ntpd /var/log/syslog :
> >
> > (Here I have : )
> >
> > ntpd[4912]: ntpd 4.2.6p3@...290-o Mon Aug 20 15:15:21 UTC 2012 (1)
> > ntpd[4913]: proto: precision = 0.980 usec
> > ntpd[4913]: ntp_io: estimated max descriptors: 1024, initial socket
> > boundary: 16
> > ntpd[4913]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
> > ntpd[4913]: Listen and drop on 1 v6wildcard :: UDP 123
> > ntpd[4913]: Listen normally on 2 lo 127.0.0.1 UDP 123
> > ntpd[4913]: Listen normally on 3 eth1 172.30.42.8 UDP 123
> > ntpd[4913]: Listen normally on 4 lo ::1 UDP 123
> > ntpd[4913]: Listen normally on 5 eth1 fe80::222:15ff:fe87:3ff6 UDP 123
> > ntpd[4913]: peers refreshed
> > ntpd[4913]: Listening on routing socket on fd #22 for interface updates
> >
> >
> 
> Ah, ok. Didn't read correctly..
> 
> journalctl /usr/bin/ntpd gives:
> Oct 14 16:51:22 hinniepc ntpd[368]: proto: precision = 0.117 usec
> Oct 14 16:51:22 hinniepc ntpd[368]: ntp_io: estimated max descriptors:
> 1024, initial socket boundary: 16
> Oct 14 16:51:22 hinniepc ntpd[368]: Listen and drop on 0 v4wildcard
> 0.0.0.0 UDP 123
> Oct 14 16:51:22 hinniepc ntpd[368]: Listen and drop on 1 v6wildcard :: UDP 123
> Oct 14 16:51:22 hinniepc ntpd[368]: Listen normally on 2 lo 127.0.0.1 UDP 123
> Oct 14 16:51:22 hinniepc ntpd[368]: Listen normally on 3 eth0
> 192.168.178.27 UDP 123
> Oct 14 16:51:22 hinniepc ntpd[368]: Listen normally on 4 lo ::1 UDP 123
> Oct 14 16:51:22 hinniepc ntpd[368]: peers refreshed
> Oct 14 16:51:22 hinniepc ntpd[368]: Listening on routing socket on fd
> #21 for interface updates

So ntpd claims to "Listen normally on 4 lo ::1 UDP 123" but lsof doesnt
display a socket bound to ::1 port 123

So I would say there is a ntpd bug.

You could try to strace ntpd from the very beginning of its life, so
that we check what it does exactly.

service ntp stop
strace -o /tmp/STRACE /usr/bin/ntpd -g -u ntp:ntp



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html