public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: TCP Queuing problem
Date: Wed, 21 Sep 2016 21:29:13 +0200	[thread overview]
Message-ID: <20160921212913.352eae72@jupiter.sol.kaishome.de> (raw)
In-Reply-To: CAN0CFw1mc5f5hzvLChkxUybx_B95hLjPhHXjBVd6ptWhpikrug@mail.gmail.com

Am Wed, 21 Sep 2016 07:30:40 -0700
schrieb Grant <emailgrant@gmail.com>:

>  [...]  
>  [...]  
> >>
> >>
> >> I just remembered that our AT&T modem/router does not respond to
> >> pings.  My solution is to move PPPoE off of that device and onto my
> >> Gentoo router so that pings pass through the AT&T device to the
> >> Gentoo router but I haven't done that yet as I want to be on-site
> >> for it. Could that behavior somehow be contributing to this
> >> problem?  There does seem to be a clear correlation between user
> >> activity at that location and the bad server behavior.  
> >
> > If that device behaves badly in router mode by blocking just all
> > icmp traffic instead of only icmp-echo-req, this is a good idea.
> > You may want to bug AT&T about this problem then. It should really
> > not block related icmp traffic.  
> 
> 
> Hi Kai, yesterday I switched my Gentoo router over to handling PPPoE
> and pings seem to be working properly now.  The AT&T device is now
> functioning as a modem only and passing everything through.  Today
> I'll find out if it helps with TCP Queuing and (supposedly) related
> http response slowdowns.

You may want to set the default congestion control to fq-codel (it's in
the kernel) if you're using DSL links. This may help your problem a
little bit. It is most effective if you deploy traffic shaping at the
same time. There was once something like wondershaper. Trick is to get
the TCP queuing back inside your router (that is where you deployed
pppoe) as otherwise packets will queue up in the modem (dsl modems use
huge queues by default). This works by lowering the uplink bandwith to
80-90% of measured maximum upload (the excess bandwidth is for short
bursts of traffic). Traffic shaping now re-orders the packets. It
should send ACK and small packets first. This should solve your
queuing problem.

Between each step check dslreports.com for bufferbloat. I'm guessing it
is currently way above 1000 ms while it should stay below 20-50 ms for
dsl.

The fq-codel congestion control fights against buffer bloat. But it can
only effectively work if you're doing traffic shaping at least on your
uplink (downlink may or may not be worth the effort depending on your
use-case).

Additionally, you can lower the priority of icmp-echo-reply this way so
during icmp flooding your uplink will still work.

This link may help you:
https://www.bufferbloat.net/projects/codel/wiki/Cake/

-- 
Regards,
Kai

Replies to list-only preferred.



  reply	other threads:[~2016-09-21 19:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 21:13 [gentoo-user] TCP Queuing problem Grant
2016-09-19 17:23 ` [gentoo-user] " Grant
2016-09-19 21:25   ` Grant
2016-09-20  0:38     ` Grant
2016-09-20 13:08       ` Grant
2016-09-21  4:01         ` Kai Krakow
2016-09-21 14:30           ` Grant
2016-09-21 19:29             ` Kai Krakow [this message]
2016-09-21 19:37               ` Grant
2016-09-21 20:06                 ` Kai Krakow
2016-09-21 20:28                   ` Kai Krakow
2016-09-21 19:41               ` Kai Krakow
2016-09-21 19:53                 ` Grant
2016-09-21 20:18                   ` Kai Krakow
2016-09-21 20:47                     ` Grant
2016-09-21 21:44                       ` Michael Mol
2016-09-22  0:30                         ` Grant
2016-09-22  7:06                       ` Kai Krakow
2016-09-25  0:25                         ` Grant
2016-10-01  9:57                           ` Grant
2016-09-20 13:50       ` J. Roeleveld
2016-09-20 14:53         ` Grant
2016-09-20 18:06           ` J. Roeleveld
2016-09-20 19:52             ` Grant
2016-09-20 20:19               ` Alarig Le Lay
2016-09-22 16:58               ` Volker Armin Hemmann

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=20160921212913.352eae72@jupiter.sol.kaishome.de \
    --to=hurikhan77@gmail.com \
    --cc=gentoo-user@lists.gentoo.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