netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: jamal <hadi@cyberus.ca>
Cc: netdev@oss.sgi.com
Subject: Re: corruption of ICMP payload while forwarding
Date: Tue, 6 Jul 2004 17:33:13 +0200	[thread overview]
Message-ID: <20040706153313.GM32707@sunbeam2> (raw)
In-Reply-To: <1089124948.1040.2.camel@jzny.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

On Tue, Jul 06, 2004 at 10:42:29AM -0400, jamal wrote:
> Harald,

Hi Jamal, thanks for your reply.

> I would probably start by downing most of those devices and still see if
> the problem is reproducible with two ethx devices.
> If it is reproducible there then replace the nics with something else
> like tulip or dlinks and see if it still happens there.
> I suspect its a driver issue so if you try the above you can prove it is
> not.

Yes, that was my recommendation, too...   I also recommended disabling
more and more features (i.e. remove iptable_nat, iptable_mangle, ...) to
see if the problem disappears at some point.

However since this is a production machine, I doubt there is too much
room for experimenting.  We're now trying to reproduce this issue with a
seperate box in the lab, though no success so far.

> cheers,
> jamal
-- 
- Harald Welte <laforge@gnumonks.org>               http://www.gnumonks.org/
============================================================================
Programming is like sex: One mistake and you have to support it your lifetime

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-07-06 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 12:29 corruption of ICMP payload while forwarding Harald Welte
     [not found] ` <1089124948.1040.2.camel@jzny.localdomain>
2004-07-06 15:33   ` Harald Welte [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=20040706153313.GM32707@sunbeam2 \
    --to=laforge@gnumonks.org \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    /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).