Recent content by Tekneek

As long as queries go through dnsmasq to Unbound, it will work. I have successfully tested that setup. I suggest setting dnsmasq's cache-size to 0 in that arrangement, so its cache doesn't disrupt Unbound's prefetch feature. I use a file called dnsmasq.postconf in /jffs/scripts/ with this in...

Is this something that will become part of cake itself, or will we need to add this to a file ourselves to get this feature? FWIW, I ran it from the command line and it seemed to work.

Excellent. Thanks for the guidance. I have a tendency to toil over the most complicated option and work my way down.

How would you make a catchall? For work related purposes, I was trying to get some experience with the full set. I don't *really* need it, though. diffserv4 is preferable to diffserv3, though.

Would a catchall be like this (for diffserv8): ipset=/./tin2_4,tin2_6 Difficult to tell if that is working so far.

I still want to wash DSCP markings on ingress, in cake's settings, right? I'm assuming that wipes whatever classifications Comcast throws on it and v2.2.0 applies its markings AFTER that.

I'm going to try to experiment with this tonight.

And that won't change too much of the functionality, although probably would want to set dnsmasq's cache-size to 0 so Unbound's pre-fetch feature isn't neutralized. In my situation, I have two pi-holes backed by bind9/unbound. Having the router handle DNS requests loses per-device metrics on...

It sounds compelling. Doesn't work for my network, as it functions today, but looking forward to seeing how your progress goes!

Would this require the router be used for DNS by the network?

One note about DSCP for those who might be running bind9 or unbound DNS servers on their network. Both make it very simple to set those values in the config, if the default 0/"best effort" doesn't meet your needs. These examples set the DSCP value to 40/CS5/ bind9 example for your config: dscp...

Is that only in the WebGUI or both the CLI and WebGUI? I saw this with the WebGUI, but not after applying the update using the CLI.

I make extensive use of IPv6 and have not noticed any negative impact on my Comcast connection using Native IPv6. For what that is worth.

For testing cake performance, here is a test that has been discussed on the Bufferbloat project's email list: https://www.waveform.com/tools/bufferbloat I got an A without any additional tweaking of the 386.2 beta 2 default configuration. RT-AX58U 150 Mb/s down 20 Mb/s up, cable/docsis...

I have put in ridiculous hours trying to fine tune performance and I get "seems the same, maybe worse." I no longer talk about my efforts on that front. :)