From: Eric Dumazet <eric.dumazet@gmail.com>
To: Chris Siebenmann <cks@cs.toronto.edu>
Cc: netdev@vger.kernel.org
Subject: Re: Bug? GRE tunnel periodically won't transmit some packets
Date: Tue, 08 Nov 2011 07:43:26 +0100 [thread overview]
Message-ID: <1320734606.8976.0.camel@edumazet-laptop> (raw)
In-Reply-To: <20111108061737.B04D236221@apps0.cs.toronto.edu>
Le mardi 08 novembre 2011 à 01:17 -0500, Chris Siebenmann a écrit :
> | Le lundi 07 novembre 2011 à 11:21 -0500, Chris Siebenmann a écrit :
> | > I have a weird problem where a GRE tunnel periodically won't transmit
> | > some (TCP) packets, while at the same time it will transmit others just
> | > fine. This is happening in the current kernel.org git head kernel as
> | > well as earlier ones.
> [...]
> | Do you have any errors on :
> |
> | ip -s -d link show dev greXXXX
>
> I do indeed. When the problem is happening, I see TX errors counting
> up one-for-one with packets that are not transmitted (and no RX
> errors). Otherwise I don't see any errors. The other end of the GRE
> tunnel shows no errors (TX or RX).
>
> Further information: when the problem is not happening, SSH doesn't
> seem to transmit 500-data-octet packets during startup. Instead I see:
>
> IP 128.100.3.52.42538 > 128.100.3.51.ssh: Flags [.], seq 22:824, ack 22, win 91, options [nop,nop,TS val 1393299 ecr 29703771], length 802
>
> I have also once seen an 'ip route show table cache' entry for a route
> through the GRE tunnel with 552-byte MTU listed:
>
> 24.173.24.46 from 128.100.3.52 dev extun
> cache expires 21333540sec ipid 0x9e5c mtu 552
>
> I haven't been able to reproduce this. I have seen listed mtu figures
> in 'ip route show table cache' output routinely drop to 774, though.
>
> (I would like to have more data on this but inconveniently the problem
> is now not reproducing itself. When it comes back I'll capture more
> information about route cache mtu values and error counts and see if
> there's anything interesting.)
>
OK, but could you please report the exact "ip -s -d link gre..."
output ?
next prev parent reply other threads:[~2011-11-08 6:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 16:21 Bug? GRE tunnel periodically won't transmit some packets Chris Siebenmann
2011-11-07 16:55 ` Eric Dumazet
2011-11-08 6:17 ` Chris Siebenmann
2011-11-08 6:43 ` Eric Dumazet [this message]
2011-11-08 7:08 ` Chris Siebenmann
2011-11-08 7:34 ` Eric Dumazet
2011-11-08 10:25 ` Eric Dumazet
2011-11-08 13:05 ` Chris Siebenmann
2011-11-08 14:05 ` Eric Dumazet
2011-11-10 5:16 ` Chris Siebenmann
2011-11-21 0:23 ` Recursive routing causes MTU collapse (was Re: Bug? GRE tunnel periodically won't transmit some packets) Chris Siebenmann
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=1320734606.8976.0.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=cks@cs.toronto.edu \
--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