From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (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 487AC21F45C for ; Sun, 26 Jul 2015 05:32:16 -0700 (PDT) Received: by qged69 with SMTP id d69so35816169qge.0 for ; Sun, 26 Jul 2015 05:32:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:mime-version:message-id:in-reply-to:references:from:to:subject :content-type; bh=VBxXIQRzsDaXVhHIGomSiPkRAaXOaFtdsEPPPZ1yI3g=; b=HJv6yrLdhKoC8kY4h0AeK03/rzsv2oujGb7AwwnxZzcvETVGyukSVxNXWaXYeLrr9r 1DTytorKmAN0xhTc4oex+s0DuRkWpD5ypSHVPhIZqTka5bzgGVPJaCG19TjCTPmgzMlJ rZ/uQy3+bqc8pZEeZ9+Iyj0PKsOLuVmqsr6RE1iV2mmyRsI6BHhrHHS5liJtN9kSDQ1y sAR4cRlmsGqDxialbq+3DVvl4Zrwoj0mO/EUeHPg6sT6kVUxq59xKeyXcVRZ5EJ2Avz4 WyqN4za9AoexVlOy82tABG1faKvOJZZY/7CA9i6w+6Zjn0sWnjjaFfkSB91J56vszzbf pnVg== X-Received: by 10.140.94.100 with SMTP id f91mr32842858qge.101.1437913935711; Sun, 26 Jul 2015 05:32:15 -0700 (PDT) Received: from hedwig-63.prd.orcali.com (ec2-54-85-253-19.compute-1.amazonaws.com. [54.85.253.19]) by smtp.gmail.com with ESMTPSA id b75sm7289257qkb.8.2015.07.26.05.32.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Jul 2015 05:32:14 -0700 (PDT) Date: Sun, 26 Jul 2015 05:32:14 -0700 (PDT) X-Google-Original-Date: Sun, 26 Jul 2015 12:32:14 GMT MIME-Version: 1.0 X-Mailer: Nodemailer (0.5.0; +http://www.nodemailer.com/) Message-Id: <1437913934406.cb259c98@Nodemailer> In-Reply-To: <55B4A43B.7050204@gmail.com> References: <55B4A43B.7050204@gmail.com> X-Orchestra-Oid: 7D2989DB-BB86-4241-B1F4-E515329026E8 X-Orchestra-Sig: 8b99f13b8300511fd05c639af760be64f176544b X-Orchestra-Thrid: 16C35577-C0DD-4AD9-A7DC-276830CC8CF3 X-Orchestra-Thrid-Sig: 54b4d22fd1923c4c99ad00b208a14873b3b9f527 X-Orchestra-Account: d3707ce70d6485ff65131f5b7374477200c5081a From: "Alec Robertson" To: cake@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="----Nodemailer-0.5.0-?=_1-1437913934966" Subject: Re: [Cake] How to test Cake on TP-Link WDR3600 X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2015 12:32:45 -0000 ------Nodemailer-0.5.0-?=_1-1437913934966 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am I right to assume that with Cake more bandwidth should be available to = use, without affecting latency=3F -- Alec Robertson On Sun, Jul 26, 2015 at 10:11 AM, Alan Jenkins wrote: >>> Quick sub-question (off-topic so my apologies), this firmware = I=E2=80=99m using that I linked to previously, has HTTPS enabled which = means every time I go to Luci I get a security error in Chrome. How do I = disable HTTPS=3F >> I would say you do not disable it, but rather look why chrome complains= (it might be that chrome dislikes self-signed certificates) and try to = convince chrome to accept the certificate nevertheless. Or you could try = firefox ;) > Firefox is the definitely the simplest browser for this, it's the = only=20 > one I've used. Just click through the instructions. A =22permanent=20 > exception=22 is the default, which should actually help security. = Feels=20 > ironic as I remember Firefox moving first on this & hence complaints=20 > about the scary warning messages etc. > Searching instructions for Chrome on Linux (=22ssl exception=22 OR = =22self=20 > signed certificate=22) they use a certutil command. Internet = Explorer=20 > will use the Windows cert store, same with Chrome on Windows. (If = you=20 > can add to the store using IE, that may be simplest & will cover both). > Additional requirement for those methods should be that the cert CN=20 > matches the URL you access. Not sure about Chrome, but for general=20 > paranoia you should check that CN / common name / =22issued to=22 = doesn't=20 > say =22*=22 i.e. =22everywhere=22. > Access the router using `http://hostname` matching the router = hostname=20 > (as per /etc/config/system). dnsmasq will let that work. If you've=20 > changed the hostname, re-gen the cert by removing it and restarting. > rm /etc/uhttpd.crt /etc/uhttpd.key > /etc/init.d/uhttpd restart > Alan ------Nodemailer-0.5.0-?=_1-1437913934966 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am I right to assume that with Cake = more bandwidth should be available to use, without affecting = latency=3F

--
Alec Robertson


On Sun, Jul 26, 2015 at 10:11 = AM, Alan Jenkins <alan.christopher.= jenkins@gmail.com> wrote:


>> Quick sub-question (off-topic = so my apologies), this firmware I=E2=80=99m using that I linked to = previously, has HTTPS enabled which means every time I go to Luci I get a = security error in Chrome. How do I disable HTTPS=3F
> I would say you do not disable it, but rather look why chrome = complains (it might be that chrome dislikes self-signed certificates) and = try to convince chrome to accept the certificate nevertheless. Or you could= try firefox ;)

Firefox is the definitely the simplest browser for this, it's the = only=20
one I've used. Just click through the instructions. A = =22permanent=20
exception=22 is the default, which should actually help security. = Feels=20
ironic as I remember Firefox moving first on this & hence = complaints=20
about the scary warning messages etc.

Searching instructions for Chrome on Linux (=22ssl exception=22 OR = =22self=20
signed certificate=22) they use a certutil command. Internet = Explorer=20
will use the Windows cert store, same with Chrome on Windows. (If = you=20
can add to the store using IE, that may be simplest & will cover = both).

Additional requirement for those methods should be that the cert = CN=20
matches the URL you access. Not sure about Chrome, but for general=20
paranoia you should check that CN / common name / =22issued to=22 = doesn't=20
say =22*=22 i.e. =22everywhere=22.

Access the router using `http://hostname` matching the router = hostname=20
(as per /etc/config/system). dnsmasq will let that work. If you've=20
changed the hostname, re-gen the cert by removing it and restarting.

rm /etc/uhttpd.crt /etc/uhttpd.key
/etc/init.d/uhttpd restart

Alan

------Nodemailer-0.5.0-?=_1-1437913934966--