From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Scott Doty <scott@sonic.net>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: 2.4.28(+?): Strange ARP problem
Date: Thu, 13 Jan 2005 10:09:00 -0200 [thread overview]
Message-ID: <20050113120900.GA5681@logos.cnet> (raw)
In-Reply-To: <20050113145029.GA22622@sonic.net>
On Thu, Jan 13, 2005 at 06:50:29AM -0800, Scott Doty wrote:
> Hi,
>
> We use Linux extensively here at Sonic.net. Our web servers have two
> NIC's -- a NIC with a public IP address, and a NIC on our SAN (with NetApps).
>
> When we tried to upgrade to 2.4.28, we encountered a problem with NetApp
> reachability, which turns out to have been a problem with ARP: we
> were seeing two ARP entries for the NetApp IP's. One would be correct, and
> one would be "incomplete".
>
> Occasionally, a system would glom onto the incomplete entry, and NFS
> connectivity would tank. This doesn't happen with 2.4.27.
>
> We'd like to upgrade to 2.4.29-rc2, but we have much trepidation about doing
> so. I certainly don't want to treat the list as "our own personal help
> desk" (as warned about in the FAQ), but was hoping someone could shed some
> light on the problem. I think either myself or one of our guys can write a
> patch to fix it, if someone would point us in the right direction.
>
> Thank you,
Scott,
I have no idea of what might be causing such regression - I see a few ARP
related changelogs on v2.4.28-rc2:
o [IPV4]: Set ARP hw type correctly for BOOTP over FDDI
o [IPV4]: Permit the official ARP hw type in SIOCSARP for FDDI
Maybe you can try earlier v2.4.28's (-rc1 for one) to check where
the problem starts to happen?
David, Herbert, any ideas?
next prev parent reply other threads:[~2005-01-13 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 14:50 2.4.28(+?): Strange ARP problem Scott Doty
2005-01-13 12:09 ` Marcelo Tosatti [this message]
2005-01-13 16:18 ` Scott Doty
2005-01-13 21:01 ` Herbert Xu
2005-01-13 22:01 ` Scott Doty
2005-01-13 22:15 ` Herbert Xu
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=20050113120900.GA5681@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=davem@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@sonic.net \
/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