[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 14 Oct 2012 21:48:43 +0200
From: Jan Hinnerk Stosch <janhinnerk.stosch@...il.com>
To: Eric Dumazet <eric.dumazet@...il.com>, netdev@...r.kernel.org
Subject: Re: regression when connecting to ipv6 localhost
2012/10/14 Eric Dumazet <eric.dumazet@...il.com>:
> On Sun, 2012-10-14 at 17:38 +0200, Jan Hinnerk Stosch wrote:
>> Hi,
>> I detected a small regression since linux 3.6.0:
>> When I run "ntpq -p" to query the status of my ntp-daemon I receive a
>> timeout (localhost.localdomain: timed out, nothing received
>> ***Request timed out). Strace shows that connecting to the ipv6
>> loopback interface times out. If I explicitly use ipv4 (ntpq -4 -p)
>> everything works as intended. Downgrading to linux 3.5.6 solves that
>> issue.
>> I reported a bug both to my distribution
>> (https://bugs.archlinux.org/task/31775) and to the kernel bugtracker
>> (https://bugzilla.kernel.org/show_bug.cgi?id=48741) not knowing
>> exactly which component caused the regression, so I was told to ask
>> this here. At the kernel-report you find an strace and tcpdump output.
>> If you need any further information just tell me, but be patient as me
>> kernel knowledge tends to zero.
>> Thanks in advance, Jan Hinnerk
>> --
>
>
> What gives :
>
> cat /etc/ntp.conf
> lsof -p `pidof ntpd`
> ntpq -p ::1
>
>
>
ntp.conf is (without comments):
server fritz.box iburst
restrict default noquery nopeer nomodify
restrict 127.0.0.1
restrict ::1
driftfile /var/lib/ntp/ntp.drift
logfile /var/log/ntp.log
"lsof -p `pidof ntpd`" gives nothing
and "ntpq -p ::1" results in the same timeout error "::1: timed out,
nothing received
***Request timed out".
--
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
Powered by blists - more mailing lists