All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: "Eble, Dan" <DanE@aiinet.com>
Cc: Chris Shaw <chriss@watertech.com>, bridge@osdl.org
Subject: Re: [Bridge] MTU Question
Date: Wed, 30 Jun 2004 11:15:59 -0700	[thread overview]
Message-ID: <20040630111559.4e2a36b1@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <C0170D0AF1277849A4B4518034F855DD0CFBFD@aiexchange.ai.aiinet.com>

On Wed, 30 Jun 2004 14:03:28 -0400
"Eble, Dan" <DanE@aiinet.com> wrote:

> What if someone (or something) attempts to change the MTU on the port after
> it has been added to the bridge?  Perhaps SIOCSIFMTU should do something
> special for bridge ports, such as return -EBUSY, or maybe ask the bridge
> whether or not the new MTU is acceptable?  If a port's MTU changes, the
> bridge may have to adjust its own MTU to maintain consistency.  It could get
> hairy.

That can be handled by a notifier callback.

> I faced this question recently when trying to implement bridging over Cisco
> HDLC.  I finally decided not to try to maintain consistency of MTUs between
> two devices, but rather to drop *all* transmitted packets when the MTU of
> the lower-layer device was insufficient to handle the largest possible
> packets from the upper-layer device.  I decided that would be enough to
> prevent someone from wrongly thinking they had configured it properly, since
> not even a cheap a 64-byte ping would work.

Probably a good idea as well.

Also, we could check when adding interface to a bridge that the MTU is big
enough for the existing ports in the bridge.

  reply	other threads:[~2004-06-30 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 18:03 [Bridge] MTU Question Eble, Dan
2004-06-30 18:15 ` Stephen Hemminger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-30 18:16 Chris Saw
2004-06-30  0:02 Chris Shaw
2004-06-30  4:22 ` shemminger
     [not found]   ` <002001c45ebb$86e7ccd0$8805640a@internal.watertech.com>
2004-06-30 17:32     ` Stephen Hemminger

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=20040630111559.4e2a36b1@dell_ss3.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=DanE@aiinet.com \
    --cc=bridge@osdl.org \
    --cc=chriss@watertech.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.