Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Beating bufferbloat
Date: Sun, 1 May 2016 22:30:16 +0100	[thread overview]
Message-ID: <57267568.1030208@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAGwEnGyV79gcgPOWt+6okRQph=3oSVjpFXVESeqkZpf_298JBQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]

Hi Alec,

I don't use that build, I roll my own so I don't know if there's
anything particularly clever with it.  However:  I assume your clients
are getting IPs via DHCP.  The DHCP server on Openwrt is the truly
wonderful dnsmasq.  By default, dnsmasq advertises itself as the local
dns server....that way it can act as a bit of a cache for dns requests
AND resolve internally handled DHCP addresses for you.  Dnsmasq will
also do DNSSEC validation on your clients behalf too.

If you really want to hand out dns server address 'direct' to your
clients and avoid all the caching/resolving goodness of dnsmasq then
take a look at
http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html and the
'--dhcp-option' defaults.  They can be overridden, indeed you can
specify 'dhcp-options' via the luci gui (network-interfaces-lan-dhcp
server->advanced settings'

Hopefully that helps.

Kevin

On 01/05/16 19:23, Alec Robertson wrote:
> Dear All,
>
> I know this isn’t directly related to bufferbloat but you all seem to
> be experts on OpenWRT so I thought I’d ask my question here anyway.
>
> I’ve installed the OpenWRT build from here
> - https://forum.openwrt.org/viewtopic.php?id=50914 - and it’s working
> well except for the fact that I can’t seem to set custom DNS servers
> on the clients. Or rather I can set them but the router seems to
> overrride them. How can I disable this? Is this special to this build
> or does OpenWRT always do this?
>
> —
> Alec Robertson.
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]

  reply	other threads:[~2016-05-01 21:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01 18:23 Alec Robertson
2016-05-01 21:30 ` Kevin Darbyshire-Bryant [this message]
2016-05-01 21:32   ` Alec Robertson
  -- strict thread matches above, loose matches on Subject: below --
2016-04-22 21:59 Alec Robertson
2016-04-22 22:01 ` Alec Robertson
2016-04-22 22:26   ` Dave Taht
2016-04-23  9:46   ` Kevin Darbyshire-Bryant
     [not found]     ` <etPan.571bc183.1196373c.318@gmail.com>
     [not found]       ` <571BC61C.4070008@darbyshire-bryant.me.uk>
     [not found]         ` <etPan.571bd013.59df9c16.318@gmail.com>
     [not found]           ` <571BD3BC.2090405@darbyshire-bryant.me.uk>
     [not found]             ` <etPan.571bd473.43735a3d.318@gmail.com>
2016-04-23 22:22               ` Alec Robertson
2016-04-24 10:37                 ` Arie
2016-04-25 16:01                   ` Dave Taht
2016-04-25 16:59                     ` Dave Taht
2016-04-29 14:58                   ` Dave Taht
2016-05-01 12:18                     ` Alec Robertson
2016-05-01 13:27                       ` 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=57267568.1030208@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --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