From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 866AC138330 for ; Wed, 21 Sep 2016 14:30:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 86843E09AF; Wed, 21 Sep 2016 14:30:42 +0000 (UTC) Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A2571E0944 for ; Wed, 21 Sep 2016 14:30:41 +0000 (UTC) Received: by mail-qk0-f181.google.com with SMTP id w204so46719817qka.0 for ; Wed, 21 Sep 2016 07:30:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=LhJkRGXKRijzRG0Vwrg8fL1hQijVh7TUwfpyopceawQ=; b=HfTkPZhjVnMj/1ATEsHtpuaO9s8olqyyOFhuKqNbciqMasjxux6WtgklmDWdx2HqTJ Rq8CF7HOBzn+qHxfVKFR+9jRGxHw6oG06Gdj1PGF/O3CLJEtYJVkI27Ywb4I/RrPqS1l L+6MhTr/F0dThu0Gm1hbhNJa+KN0zJv+7Ik1MGFFfYA0IOzxiuHe4Ze9bvZk0D/R3o2I MIaiyUQSYoKLU3B79nPCbrNj+SGh3Td60FMNepYiSce7n1DbDs7qntoYcaXdKXpQ8tpP M/MYFGTjFVALNkbY73xN4TM0uFxKmaiaztf6VOcCkKEVhCMSBBHM9m7x61G87UHA7TWc hCKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=LhJkRGXKRijzRG0Vwrg8fL1hQijVh7TUwfpyopceawQ=; b=eGEgmh4Czwb8BBZqzamIVH2WBQOsBxde5hXkz2zIQsyFZK7kp6ekx9/qzCx+3DovVV Klm7rFjArRlM4u60ZipP1lLxMBFX/S2m161+jDknNJ6kGYXKxMMIFSXfPo49d9JAKsSD Wm0Yz3Ep5dllpTWma0a8TvpL6qSXpVviRUJkkUPPbIugCxbRQba0bjRosyyE0c2oOVWI LIR6zozQyVu66G8DXA8QZfVhmb+L7q2d8HhFTkbHNKNOIhnOOoSMd9lYLqhZCAjuA2c2 3Q41faLaURZZP6MAi3gegWLVwFHnD9EK92xkGqvAx/WGAm17ZrfjEd9r0nFGrPTTX2o3 ExZw== X-Gm-Message-State: AE9vXwP/xHOXFBVd3CPBiT02PesKfAnuCKdABE6ig0eHmO5d4gRssdn4/+M2jOno1SJ0ArKIk9koBQq3+GT31A== X-Received: by 10.55.204.82 with SMTP id r79mr43998309qki.240.1474468240749; Wed, 21 Sep 2016 07:30:40 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.140.38.179 with HTTP; Wed, 21 Sep 2016 07:30:40 -0700 (PDT) In-Reply-To: <20160921060118.759d94ba@jupiter.sol.kaishome.de> References: <20160921060118.759d94ba@jupiter.sol.kaishome.de> From: Grant Date: Wed, 21 Sep 2016 07:30:40 -0700 Message-ID: Subject: Re: [gentoo-user] Re: TCP Queuing problem To: Gentoo mailing list Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: a06ce8b3-180a-4b82-9f56-f8f0e26e38b6 X-Archives-Hash: 44d0315247aee1d996283e0a02093871 >> >> It looks like the TCP Queuing spike itself was due to imapproxy >> >> which I've now disabled. I'll post more info as I gather it. >> > >> > >> > imapproxy was clearly affecting the TCP Queuing graph in munin but I >> > still ended up with a massive TCP Queuing spike today and >> > corresponding http response time issues long after I disabled >> > imapproxy. Graph attached. I'm puzzled. >> >> >> 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. - Grant