From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jagdmann@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ethernet IP multicast maximum packet size
Date: Thu, 08 Sep 2005 17:40:25 +0100 [thread overview]
Message-ID: <1126197625.19834.52.camel@localhost.localdomain> (raw)
In-Reply-To: <5d0f6099050908083510aa9ab4@mail.gmail.com>
On Iau, 2005-09-08 at 17:35 +0200, Dirk Jagdmann wrote:
> Hello developers,
>
> I googled around all day, but did not find any satisfying answer. Is
> there a maximum packet size when I use IP multicasting in a local
> ethernet LAN? Or more precisely, does the multicast code in Linux
> handle an IP fragmentation/defragmentation of a 63K UDP multicast
> datagram, which is transmitted over an 1500bytes MTU ethernet? Or
> should I stay on the safe edge and don't construct datagrams > 1500 so
> I'll avoid fragmentation?
It is considered good practice to keep local multicast within local MTU.
For remote multicast 576 byte total frames used to be recommended by
some people but MTU discovery and multicast is a real can of worms. (A
google for "multicast implosion" should find some useful material on the
question of discovery and multicast)
prev parent reply other threads:[~2005-09-08 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 15:35 Ethernet IP multicast maximum packet size Dirk Jagdmann
2005-09-08 16:40 ` Alan Cox [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=1126197625.19834.52.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jagdmann@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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