From: "Alec Robertson" <alecrobertson13@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] How to test Cake on TP-Link WDR3600
Date: Sun, 26 Jul 2015 05:32:14 -0700 (PDT) [thread overview]
Message-ID: <1437913934406.cb259c98@Nodemailer> (raw)
In-Reply-To: <55B4A43B.7050204@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]
Am I right to assume that with Cake more bandwidth should be available to use, without affecting latency?
--
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’m 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?
>> 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
> one I've used. Just click through the instructions. A "permanent
> exception" is the default, which should actually help security. Feels
> ironic as I remember Firefox moving first on this & hence complaints
> about the scary warning messages etc.
> Searching instructions for Chrome on Linux ("ssl exception" OR "self
> signed certificate") they use a certutil command. Internet Explorer
> will use the Windows cert store, same with Chrome on Windows. (If you
> 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
> matches the URL you access. Not sure about Chrome, but for general
> paranoia you should check that CN / common name / "issued to" doesn't
> say "*" i.e. "everywhere".
> Access the router using `http://hostname` matching the router hostname
> (as per /etc/config/system). dnsmasq will let that work. If you've
> 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
[-- Attachment #2: Type: text/html, Size: 2287 bytes --]
next prev parent reply other threads:[~2015-07-26 12:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 15:45 Alec Robertson
2015-07-25 16:27 ` Sebastian Moeller
2015-07-25 16:40 ` Alec Robertson
2015-07-25 16:49 ` Alec Robertson
2015-07-25 17:15 ` Sebastian Moeller
2015-07-25 17:38 ` Alec Robertson
2015-07-25 18:12 ` Dave Taht
2015-07-25 18:21 ` Alec Robertson
2015-07-25 18:49 ` Sebastian Moeller
2015-07-25 18:47 ` Sebastian Moeller
2015-07-25 18:57 ` Alec Robertson
2015-07-25 19:19 ` Sebastian Moeller
2015-07-25 20:58 ` Alec Robertson
2015-07-26 7:01 ` Sebastian Moeller
2015-07-26 9:11 ` Alan Jenkins
2015-07-26 12:32 ` Alec Robertson [this message]
2015-07-26 12:35 ` Jonathan Morton
2015-07-26 20:09 ` Alec Robertson
2015-07-26 21:05 ` Alan Jenkins
2015-07-26 21:20 ` Jonathan Morton
2015-07-26 21:38 ` Alan Jenkins
2015-07-27 7:17 ` Sebastian Moeller
2015-08-02 19:04 ` Benjamin Cronce
2015-08-02 20:07 ` Dave Taht
2015-07-27 7:13 ` Sebastian Moeller
2015-07-27 7:10 ` Sebastian Moeller
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1437913934406.cb259c98@Nodemailer \
--to=alecrobertson13@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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