All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Szilveszter Ordog <slipszi@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Problems with tg3 driver after lowering the MTU
Date: Thu, 21 Jan 2010 15:27:23 +0000	[thread overview]
Message-ID: <1264087643.2794.2.camel@achroite.uk.solarflarecom.com> (raw)
In-Reply-To: <ac67d9131001210721q37a6883eg85430f9564d8e007@mail.gmail.com>

On Thu, 2010-01-21 at 16:21 +0100, Szilveszter Ordog wrote:
> After the MTU is lowered (e.g. to 1420) on a tg3-driven interface,
> received packets larger than that (e.g. 1500 bytes) are silently
> discarded by the driver. Therefore the system doesn't send ICMP
> fragmentation-needed packets and the other side doesn't detect this
> condition.
> 
> Is this a known bug?

I don't believe this a bug.  Within a local network, MTU should be set
the same for all interfaces.  Routers that connect networks with
different MTUs will generate the fragmentation-needed message as
appropriate.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.


  reply	other threads:[~2010-01-21 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 15:21 Problems with tg3 driver after lowering the MTU Szilveszter Ordog
2010-01-21 15:27 ` Ben Hutchings [this message]
2010-01-21 15:42   ` Szilveszter Ordog
2010-01-21 17:47     ` Templin, Fred L
2010-01-21 18:30       ` Ben Hutchings
2010-01-21 23:02         ` Templin, Fred L

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=1264087643.2794.2.camel@achroite.uk.solarflarecom.com \
    --to=bhutchings@solarflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=slipszi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.