From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id D4E5D21F324 for ; Thu, 23 Apr 2015 13:59:46 -0700 (PDT) Received: by oica37 with SMTP id a37so25154767oic.0 for ; Thu, 23 Apr 2015 13:59:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=IuT4aFxZ9yQOwNDuAzn9mqUKd/PQFEUAvU4XvllF84k=; b=B0PnHWVfWBO8SMlWIBc2WWpxIQ6/XTf8NOM1d++c+n635A5qtOAXtlUXt7uTKiVA9K rOTyYLcbEQ6sCLQvhhTrNNwayrYyH3qwJvtOlAmGEDnpDVLvPaYrktJTPVKG6LmXql2H gKvzKDWRvTIErw2bhrDdm67PFir/WES9QSQ/Saf0o7s1bXqi8dkU7X50LArqHlFdWG8l poefkt+cxydNT7jIfvvaGIgvleJoxlKzn6oQVUg7VnEtH5+2X/G1ceoTRVv/vbJm8aOp CG0oS5l05Hw4CoYPyRwgofPQN/SKz5fdDii7REdNnEaTFUE7XcEPWzFsqmGFMfB4NbNC n5pw== MIME-Version: 1.0 X-Received: by 10.202.4.76 with SMTP id 73mr4068395oie.11.1429822786001; Thu, 23 Apr 2015 13:59:46 -0700 (PDT) Received: by 10.202.71.139 with HTTP; Thu, 23 Apr 2015 13:59:45 -0700 (PDT) In-Reply-To: <36c42052-1ce6-4e94-b4ab-6b9186fa3d1e@chromium.org> References: <36c42052-1ce6-4e94-b4ab-6b9186fa3d1e@chromium.org> Date: Thu, 23 Apr 2015 13:59:45 -0700 Message-ID: From: Dave Taht To: "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] Fwd: [proto-quic] Bad router QoS settings can disrupt QUIC X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2015 21:00:15 -0000 ---------- Forwarded message ---------- From: Nelson Minar Date: Thu, Apr 23, 2015 at 11:57 AM Subject: [proto-quic] Bad router QoS settings can disrupt QUIC To: proto-quic@chromium.org I just fixed a problem where Google Chrome wasn't working well with Google sites and wanted to share my experience in case it helps anyone. The problem was that Google sites were loading very slowly in Chrome using QUIC. HTTP requests everywhere were working fine, but Google search and Google Groups using QUIC were super-slow. I think the problem was my router's QoS settings. The default QoS config for this firmware has a rule which is "unidentified UDP protocols are labeled Crawl and limited to 5% of bandwidth". QUIC was unidentified. Removing that rule fixed the problem. The QoS rule in the router is definitely stupid but it may not be entirely uncommon. I had the rule as a default from Tomato v1.32 (Toastman). I think some of the newer Tomato/Shibby builds have a rule like this as well. QoS is off by default in Tomato, but if you turn it on you get this Crawl classification. And while Tomato is hackerware and people who use it should know better, I suspect many of its QoS ideas have made their way into commercial products. Newer ASUS routers, for instance, have a Tomato-derived firmware installed. Every time I see a new UDP protocol on the Internet I worry what all may break. I love UDP but a whole lot of Internet infrastructure these days is optimized only for TCP (or worse, HTTP). I don't think QUIC is a bad idea at all, I'm just curious what UDP misconfigurations it will uncover. -- You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group. To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+unsubscribe@chromium.org. To post to this group, send email to proto-quic@chromium.org. For more options, visit https://groups.google.com/a/chromium.org/d/optout. --=20 Dave T=C3=A4ht Open Networking needs **Open Source Hardware** https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67