From: Eric Dumazet <eric.dumazet@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Jan Hinnerk Stosch <janhinnerk.stosch@gmail.com>, netdev@vger.kernel.org
Subject: Re: regression when connecting to ipv6 localhost
Date: Mon, 15 Oct 2012 09:43:32 +0200 [thread overview]
Message-ID: <1350287012.21172.17421.camel@edumazet-glaptop> (raw)
In-Reply-To: <1350286790.21172.17414.camel@edumazet-glaptop>
On Mon, 2012-10-15 at 09:39 +0200, Eric Dumazet wrote:
> So if you want to help, grab ntpd sources, reproduce the problem, make a
> bisection so that we have a clue of the kernel change that trigger the
> problem, and so on...
>
> That would be really awesome, given Jan is not a kernel developer, we
> cannot really ask him to do this himself.
>
And before you ask, on my machine, ntpd does listen to ::1, so I dont
have the problem. If I cant reproduce it, I probably wont fix the
problem.
...
ntpd 2964 ntp 16u IPv4 17966 0t0 UDP *:ntp
ntpd 2964 ntp 17u IPv6 17967 0t0 UDP *:ntp
ntpd 2964 ntp 18u IPv4 17973 0t0 UDP 127.0.0.1:ntp
ntpd 2964 ntp 19u IPv4 17974 0t0 UDP 172.30.42.8:ntp
ntpd 2964 ntp 20u IPv6 17975 0t0 UDP [::1]:ntp
ntpd 2964 ntp 21u IPv6 17976 0t0 UDP [fe80::222:15ff:fe87:3ff6]:ntp
ntpd 2964 ntp 22u netlink 0t0 17977 ROUTE
next prev parent reply other threads:[~2012-10-15 7:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 15:38 regression when connecting to ipv6 localhost Jan Hinnerk Stosch
2012-10-14 19:29 ` Eric Dumazet
2012-10-14 19:48 ` Jan Hinnerk Stosch
2012-10-14 19:54 ` Eric Dumazet
2012-10-14 19:57 ` Jan Hinnerk Stosch
2012-10-14 20:25 ` Eric Dumazet
2012-10-14 20:26 ` Eric Dumazet
2012-10-14 20:28 ` Eric Dumazet
2012-10-14 20:39 ` Jan Hinnerk Stosch
2012-10-14 20:45 ` Eric Dumazet
2012-10-14 20:47 ` Eric Dumazet
2012-10-14 20:56 ` Jan Hinnerk Stosch
2012-10-14 21:02 ` Eric Dumazet
2012-10-14 21:07 ` Eric Dumazet
2012-10-14 21:21 ` Jan Hinnerk Stosch
2012-10-14 21:35 ` Eric Dumazet
2012-10-14 21:54 ` Jan Hinnerk Stosch
2012-10-14 22:01 ` Eric Dumazet
2012-10-14 22:11 ` Jan Hinnerk Stosch
2012-10-15 5:42 ` Eric Dumazet
2012-10-15 7:03 ` Jan Hinnerk Stosch
2012-10-15 7:14 ` Joe Perches
2012-10-15 7:39 ` Eric Dumazet
2012-10-15 7:43 ` Eric Dumazet [this message]
2012-10-15 11:25 ` Joe Perches
2012-10-15 12:31 ` Eric Dumazet
2012-10-15 13:10 ` Jan Hinnerk Stosch
2012-10-15 13:21 ` Eric Dumazet
2012-10-15 13:28 ` Jan Hinnerk Stosch
2012-10-16 16:07 ` Jan Hinnerk Stosch
2012-10-16 16:43 ` Eric Dumazet
2012-10-16 16:55 ` Eric Dumazet
2012-10-16 17:37 ` [PATCH] ipv6: addrconf: fix /proc/net/if_inet6 Eric Dumazet
2012-10-16 18:30 ` Jan Hinnerk Stosch
2012-10-16 18:39 ` David Miller
2012-10-16 22:01 ` Joe Perches
2012-10-16 18:55 ` David Miller
2012-10-15 9:25 ` regression when connecting to ipv6 localhost Eric Dumazet
2012-10-15 10:32 ` Jan Hinnerk Stosch
2012-10-15 9:07 ` Jan Ceuleers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1350287012.21172.17421.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=janhinnerk.stosch@gmail.com \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox