From: jamal <hadi@cyberus.ca>
To: Benoit PAPILLAULT <benoit.papillault@free.fr>
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 14837] New: gretap does not fragment IP packets
Date: Mon, 21 Dec 2009 14:09:03 -0500 [thread overview]
Message-ID: <1261422543.8201.6.camel@bigi> (raw)
In-Reply-To: <4B2ECCAB.8010702@free.fr>
On Mon, 2009-12-21 at 02:17 +0100, Benoit PAPILLAULT wrote:
> >
> As I explained in my original message, the gre device MTU must be 1500
> bytes (since it is used in an Ethernet bridge).
Ok, sorry i missed this bit. I didnt realize that the bridge device had
such draconian enforcement. Bridge picks whatever the lowest common
denominator is for MTU (I suspect so as to not keep track of all the
interfaces; good policy, IMO, should allow a user to shoot themselves in
the toe while defaulting to the min mtu).
>From the looks of it, this enforcement could be changed with a one line
patch - but not being privy to the reasoning it would be unfair of me to
do so from my comfortable couch. Stephen?
> To reproduce the
> problem, I did a very simple setup with two machines (A & B) connected
> with an Ethernet cable (so no router between them).
>
> On machine A :
> # ip link add gre0 type gretap local <A> remote <B>
> # ifconfig gre0 mtu 1500
What i meant is try to ifconfig gre0 to something small like 1420B
cheers,
jamal
next prev parent reply other threads:[~2009-12-21 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14837-10286@http.bugzilla.kernel.org/>
2009-12-18 23:32 ` [Bugme-new] [Bug 14837] New: gretap does not fragment IP packets Andrew Morton
2009-12-18 23:47 ` Stephen Hemminger
2009-12-19 12:55 ` jamal
2009-12-21 1:17 ` Benoit PAPILLAULT
2009-12-21 19:09 ` jamal [this message]
2010-01-07 14:30 ` Benoit PAPILLAULT
2010-01-10 16:03 ` jamal
2010-01-10 17:43 ` Benoit PAPILLAULT
2010-01-10 21:59 ` 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=1261422543.8201.6.camel@bigi \
--to=hadi@cyberus.ca \
--cc=akpm@linux-foundation.org \
--cc=benoit.papillault@free.fr \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).