Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: netdev <netdev@vger.kernel.org>, 708995@bugs.debian.org
Subject: Re: Bug#708995: iptables firewall is dropping GRO'd packets
Date: Mon, 20 May 2013 17:53:25 -0700	[thread overview]
Message-ID: <1369097605.3301.203.camel@edumazet-glaptop> (raw)
In-Reply-To: <1369096123.3469.127.camel@deadeye.wl.decadent.org.uk>

On Tue, 2013-05-21 at 01:28 +0100, Ben Hutchings wrote:
> I'm seeing packet loss when forwarding from a LAN to PPP, whenever GRO
> kicks in on the LAN interface.
> 
> On Mon, 2013-05-20 at 05:48 +0100, Ben Hutchings wrote:
> [...]
> > The Windows system is connected to the LAN interface (int0).  Turning
> > off GRO on this interface works around the problem.  But since GRO is
> > on by default, it clearly ought to work properly with iptables.
> > 
> > I'll try to work out where the drops are occurring, but the
> > perf net_dropmonitor script is also broken...
> [...]
> 
> I've fixed that script and now I can see that it's not iptables but
> tbf_enqueue() that is dropping the GRO'd packets.  I do traffic-shaping
> on the PPP link like this:
> 
> tc qdisc replace dev ppp0 root tbf rate 420kbit latency 50ms burst 1540
> 
> The local TCP will never generate an skb larger than the burst size
> because it knows the PPP interface can't do GSO or TSO.  And the wifi
> network doesn't seem to be fast enough for GRO to have much of an
> effect.  But a peer on the wired network can trigger GRO and this
> produces an skb that exceeds the burst size.
> 
> Is this a bug in sch_tbf, or should I accept it as a limitation?  It
> seems like it should do GSO on entry to the queue if necessary.
> 

This has been discussed on netdev this year.

Jiri Pirko was working on this. 

(thread :  tbf: take into account gso skbs)

  reply	other threads:[~2013-05-21  0:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130520044850.31127.24148.reportbug@shadbolt.decadent.org.uk>
2013-05-21  0:28 ` Bug#708995: iptables firewall is dropping GRO'd packets Ben Hutchings
2013-05-21  0:53   ` Eric Dumazet [this message]
2013-05-21  2:03     ` Eric Dumazet
2013-05-21 12:55       ` Jiri Pirko
2013-05-21 13:22         ` Eric Dumazet
2013-05-21 18:16       ` [PATCH net-next] sch_tbf: segment too big GSO packets Eric Dumazet
2013-05-21 20:39         ` Jiri Pirko
2013-05-23  7:07           ` David Miller

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=1369097605.3301.203.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=708995@bugs.debian.org \
    --cc=ben@decadent.org.uk \
    --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