All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org, benoit.papillault@free.fr,
	Jamal Hadi Salim <hadi@cyberus.ca>
Subject: Re: [Bugme-new] [Bug 14837] New: gretap does not fragment IP packets
Date: Fri, 18 Dec 2009 15:47:00 -0800	[thread overview]
Message-ID: <20091218154700.623f6779@nehalam> (raw)
In-Reply-To: <20091218153209.45042a58.akpm@linux-foundation.org>

On Fri, 18 Dec 2009 15:32:09 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:

> > 
> > The expected behavior would be that the encapsulated packet be fragmented. The
> > observed behavior is that any encapsulated packets over 1500 bytes are simply
> > dropped and an ICMP "fragmentation needed" message is sent to ... who knows.
> > 
> > My feeling is that DF bit is not playing nice here.
> >   

TCP uses DF bit to do path mtu discovery.  If your firewall et all, doesn't
do ICMP correctly, then this is the classic TCP path MTU discovery ICMP
blackhole problem. 

http://www.ietf.org/rfc/rfc2923.txt

  reply	other threads:[~2009-12-18 23:47 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 [this message]
2009-12-19 12:55   ` jamal
2009-12-21  1:17     ` Benoit PAPILLAULT
2009-12-21 19:09       ` jamal
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=20091218154700.623f6779@nehalam \
    --to=shemminger@vyatta.com \
    --cc=akpm@linux-foundation.org \
    --cc=benoit.papillault@free.fr \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=hadi@cyberus.ca \
    --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 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.