netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Siebenmann <cks@cs.toronto.edu>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Chris Siebenmann <cks@cs.toronto.edu>, netdev@vger.kernel.org
Subject: Re: Bug? GRE tunnel periodically won't transmit some packets
Date: Tue, 08 Nov 2011 02:08:19 -0500	[thread overview]
Message-ID: <20111108070819.C643236221@apps0.cs.toronto.edu> (raw)
In-Reply-To: eric.dumazet's message of Tue, 08 Nov 2011 07:43:26 +0100. <1320734606.8976.0.camel@edumazet-laptop>

| 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).
[..]
| OK, but could you please report the exact "ip -s -d link gre..."
| output ?

Sure. Here it is:

7: extun: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1200 qdisc noqueue state UNKNOWN 
    link/gre 66.96.18.208 peer 128.100.3.58
    gre remote 128.100.3.58 local 66.96.18.208 dev ppp0 ttl inherit 
    RX: bytes  packets  errors  dropped overrun mcast   
    2793721    17015    0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    2242148    26824    18      0       0       0      

(The packet and byte counts were much lower when the problem happened;
this time around it happened relatively soon after I rebooted my machine
and brought up the PPPoE and GRE links, but hasn't happened since and
I've been using the GRE link.)

For vaguely historical reasons I don't use 'greXXX' as the name of
the GRE tunnel. I have a 'gre0' device, but it is not up. In case it
matters, its output is:

6: gre0: <NOARP> mtu 1476 qdisc noop state DOWN 
    link/gre 0.0.0.0 brd 0.0.0.0
    gre remote any local any ttl inherit nopmtudisc 
    RX: bytes  packets  errors  dropped overrun mcast   
    0          0        0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    0          0        0       0       0       0      

 Let me know if you want a full dump of 'ip link show' (with or
without verbosity).

	- cks

  reply	other threads:[~2011-11-08  7:08 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
2011-11-08  7:08       ` Chris Siebenmann [this message]
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=20111108070819.C643236221@apps0.cs.toronto.edu \
    --to=cks@cs.toronto.edu \
    --cc=eric.dumazet@gmail.com \
    --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).