From: Eric Dumazet <eric.dumazet@gmail.com>
To: Menny_Hamburger@Dell.com
Cc: netdev@vger.kernel.org
Subject: Re: IPV6 ndisc:: Bad NIC causing IPV6 NDP to stop working
Date: Thu, 21 Jun 2012 10:22:52 +0200 [thread overview]
Message-ID: <1340266972.4604.4404.camel@edumazet-glaptop> (raw)
In-Reply-To: <D8C50530D6022F40A817A35C40CC06A70B34DBEFCF@DUBX7MCDUB01.EMEA.DELL.COM>
On Thu, 2012-06-21 at 08:59 +0100, Menny_Hamburger@Dell.com wrote:
> Hi,
>
> Our machines runs EL5.8 x86_64.
> We have witnessed several cases where we suspect that a bad NIC on the machine caused IPV6 neighbour discovery to stop working on all the other NICs - when this happens ping6 fails on every NIC we try it.
> From looking into the code I see that there is only a single socket assigned for NDP; Does it sound logical to allocate a socket per interface instead of a single global socket.
> I have found the following thread in LKML: https://lkml.org/lkml/2006/11/29/335, and it seems that this allocation issue still exists in EL5 based kernels - could this cause the above problem?
>
What is a bad NIC, and why not fixing it ?
next prev parent reply other threads:[~2012-06-21 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 7:59 IPV6 ndisc:: Bad NIC causing IPV6 NDP to stop working Menny_Hamburger
2012-06-21 8:22 ` Eric Dumazet [this message]
2012-06-21 8:43 ` Menny_Hamburger
2012-06-21 9:16 ` Eric Dumazet
2012-07-08 8:46 ` Menny_Hamburger
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=1340266972.4604.4404.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=Menny_Hamburger@Dell.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