LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: "Gosney, JeremiX" <jeremix.gosney@intel.com>
Cc: linux-kernel@vger.kernel.org, "Peters,
	Gordon" <gordon.peters@intel.com>,
	"Sy, Dely L" <dely.l.sy@intel.com>
Subject: Re: ARP Bug?
Date: Wed, 19 Dec 2007 15:51:27 -0500	[thread overview]
Message-ID: <4769844F.4030902@redhat.com> (raw)
In-Reply-To: <F2B6B9EAC551DA4AA8833629D55D9CA8482D4C@orsmsx418.amr.corp.intel.com>

On 12/14/2007 08:11 PM, Gosney, JeremiX wrote:
> We've noticed the 2.6-based Linux systems in our test lab are
> experiencing some "ARP flux"-like symptoms.  
> 
> The systems reply with eth0's hardware address to all ARP requests,
> regardless of the IP being queried.  Because of this, the system will
> only send and receive packets on eth0; if eth0 is brought down, the
> system is unreachable even though it still has several active
> connections.  With eth0 unplugged, none of the other interfaces are
> reachable (this is presumably a side-effect caused by the switch ARP
> cache.) Failover routes are defined in the routing table, but the system
> still will not send/receive packets out those interfaces.
> 
> Can anything be done to correct this behaviour?
> 
> 

Offtopic here, but anyway look at http://linux-ip.net/html/ch-ether.html


  parent reply	other threads:[~2007-12-19 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-15  1:11 Gosney, JeremiX
2007-12-15  1:32 ` Jan Engelhardt
     [not found]   ` <3A64AD58EE71B34FB333E733C62CDE3C04A83F60@orsmsx414.amr.corp.intel.com>
2007-12-19 18:30     ` Jan Engelhardt
2007-12-19 20:51 ` Chuck Ebbert [this message]
2008-01-30 12:29 Matti Linnanvuori
2008-01-30 12:31 ` Jan Engelhardt
2008-01-30 12:44 Matti Linnanvuori
2008-01-30 13:20 ` Andi Kleen
2008-01-30 13:28   ` Jan Engelhardt
2008-01-30 13:23 ` Jan Engelhardt

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=4769844F.4030902@redhat.com \
    --to=cebbert@redhat.com \
    --cc=dely.l.sy@intel.com \
    --cc=gordon.peters@intel.com \
    --cc=jeremix.gosney@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: ARP Bug?' \
    /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

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).