Re: [Cake] How to test Cake on TP-Link WDR3600

[Sebastian Moeller <moeller0@gmx.de>]

Hi Alec,

On Jul 26, 2015, at 14:32 , Alec Robertson <alecrobertson13@gmail.com> wrote:

> Am I right to assume that with Cake more bandwidth should be available to use, without affecting latency?

	This depends; compared to not using SQM you will loose some bandwidth, BUT the latency should stay nicely bound. The main improvement in a nutshell is that with properly configured SQM (with cake being the easiest to setup variant with lots of clever tricks under the hood) your link will still stay reasonably snappy even under saturating load. In other words the links keeps useable when you actually use it, most people consider the typically required bandwidth sacrifice of 10-15% for downstream acceptable…

	By the way, if I could convince you to post the results of the following commands run on your router via ssh:

cat /etc/config/sqm
/etc/init.d/sqm stop
tc -d qdisc
/etc/init.d/sqm start
tc -d qdisc

I would be delighted ;)


Best Regards
	Sebastian


> 
> --
> 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 
> 
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake