From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: regression when connecting to ipv6 localhost Date: Sun, 14 Oct 2012 23:35:42 +0200 Message-ID: <1350250542.21172.17229.camel@edumazet-glaptop> References: <1350242941.21172.17023.camel@edumazet-glaptop> <1350244485.21172.17077.camel@edumazet-glaptop> <1350246314.21172.17139.camel@edumazet-glaptop> <1350246414.21172.17144.camel@edumazet-glaptop> <1350246481.21172.17147.camel@edumazet-glaptop> <1350248858.21172.17197.camel@edumazet-glaptop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: Jan Hinnerk Stosch Return-path: Received: from mail-wi0-f178.google.com ([209.85.212.178]:59581 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752354Ab2JNVfr (ORCPT ); Sun, 14 Oct 2012 17:35:47 -0400 Received: by mail-wi0-f178.google.com with SMTP id hr7so1349243wib.1 for ; Sun, 14 Oct 2012 14:35:46 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Sun, 2012-10-14 at 23:21 +0200, Jan Hinnerk Stosch wrote: > 2012/10/14 Eric Dumazet : > > 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@1.2290-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