From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jan Hinnerk Stosch <janhinnerk.stosch@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: regression when connecting to ipv6 localhost
Date: Sun, 14 Oct 2012 23:02:29 +0200 [thread overview]
Message-ID: <1350248549.21172.17188.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAO_aot5eyNmYhMi7LSKqwsb=hFbWUqOF3rzWt7Kt-C4hJ9pOmQ@mail.gmail.com>
On Sun, 2012-10-14 at 22:56 +0200, Jan Hinnerk Stosch wrote:
> 2012/10/14 Eric Dumazet <eric.dumazet@gmail.com>:
> > On Sun, 2012-10-14 at 22:45 +0200, Eric Dumazet wrote:
> >
> >> OK so IPv6 UDP frames are delivered to ntpd
> >>
> >> could you strace it while doing one "ntpq -p"
> >>
> >> strace -p 368
> >>
> >
> > Also please post "ip -6 addr"
> >
> >
>
> ip -6 addr gives:
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
> inet6 fe80::922b:34ff:fe33:c292/64 scope link
> valid_lft forever preferred_lft forever
>
> And the output of "strace ntpq -p" is attached in file "ntpq-p".
>
> I also did a tcpdump earlier this day as told in the bugtracker. Find
> the parts containing "ntpd" attached in file "tcpdump".
I already got these files, thank you
I asked a strace of the ntpd daemon, since we now know frames are
delivered to the application. I want to check what ntpd does of these
frames, since apparently it gives no answer.
next prev parent reply other threads:[~2012-10-14 21:02 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 [this message]
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
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=1350248549.21172.17188.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=janhinnerk.stosch@gmail.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