From: David Ahern <dsahern@gmail.com>
To: Tariq Toukan <tariqt@mellanox.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Cc: ranro@mellanox.com, guye@mellanox.com,
Eran Ben Elisha <eranbe@mellanox.com>
Subject: Re: IPv6 loopback issue report
Date: Mon, 28 Aug 2017 09:07:20 -0600 [thread overview]
Message-ID: <47ca5f63-de49-d9fe-f8f7-08240206627a@gmail.com> (raw)
In-Reply-To: <464e900f-c256-4d22-6a83-a3aea0fca8bc@mellanox.com>
On 8/28/17 8:48 AM, Tariq Toukan wrote:
> # /bin/ping6 -c 3 fe80::7efe:90ff:fecb:7502%ens8
> PING fe80::7efe:90ff:fecb:7502%ens8(fe80::7efe:90ff:fecb:7502) 56 data
> bytes
>
> --- fe80::7efe:90ff:fecb:7502%ens8 ping statistics ---
> 3 packets transmitted, 0 received, 100% packet loss, time 2043ms
I'll take a look. Most likely related to my recent IPv6 change.
prev parent reply other threads:[~2017-08-28 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 14:48 IPv6 loopback issue report Tariq Toukan
2017-08-28 15:07 ` David Ahern [this message]
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=47ca5f63-de49-d9fe-f8f7-08240206627a@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=eranbe@mellanox.com \
--cc=guye@mellanox.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=ranro@mellanox.com \
--cc=tariqt@mellanox.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).