Re: [OpenWrt-Devel] [LEDE-DEV] RFC netifd: UCI parameter to sort name servers in resolv.conf.auto

One other point about provider order in dnsmasq. dnsmasq added long ago the facility (particularly for reverse lookups on ipv6) to bind source addresses to destination dns servers. This solves a portion of this problem. Stuff coming in from one ipv6 network gets dns lookups out the right network

Re: [OpenWrt-Devel] RFC netifd: UCI parameter to sort name servers in resolv.conf.auto

Hans Dedecker writes: > Hi Felix, > > Current implementation in netifd writes the dns servers into > resolv.conf.auto file based on the order of the interfaces in the > interface list which is alphabetical sorted. The resolver, in this > case dnsmasq, reads the

Re: [OpenWrt-Devel] [LEDE-DEV] RFC netifd: UCI parameter to sort name servers in resolv.conf.auto

On Mon, Sep 5, 2016 at 3:23 PM, Kevin Darbyshire-Bryant wrote: > > > On 05/09/16 13:49, Hans Dedecker wrote: > > On Mon, Sep 5, 2016 at 1:49 PM, Jo-Philipp Wich wrote: > > Hi Hans, > > imho it would also make sense to take any existing metric setting

Re: [OpenWrt-Devel] [LEDE-DEV] RFC netifd: UCI parameter to sort name servers in resolv.conf.auto

On 05/09/16 13:49, Hans Dedecker wrote: On Mon, Sep 5, 2016 at 1:49 PM, Jo-Philipp Wich wrote: Hi Hans, imho it would also make sense to take any existing metric setting into account as well. At least I'd expect that if I have a wan1 with metric 10 and a wan2 with metric 20

Re: [OpenWrt-Devel] [LEDE-DEV] RFC netifd: UCI parameter to sort name servers in resolv.conf.auto

On Mon, Sep 5, 2016 at 1:49 PM, Jo-Philipp Wich wrote: > Hi Hans, > > imho it would also make sense to take any existing metric setting into > account as well. At least I'd expect that if I have a wan1 with metric > 10 and a wan2 with metric 20 that the DNS server entries "inherit"

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH ubus 0/3] ubusd: fix ACL checking

On 2016-09-05 10:21, Denis Osvald wrote: > Ping? I've applied patch 1 and 3. I need more time to properly review patch 2. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] [LEDE-DEV] RFC netifd: UCI parameter to sort name servers in resolv.conf.auto

Hi Hans, imho it would also make sense to take any existing metric setting into account as well. At least I'd expect that if I have a wan1 with metric 10 and a wan2 with metric 20 that the DNS server entries "inherit" the same weight/order. So priority wise I'd first order by dns metric, then by

Re: [OpenWrt-Devel] RFC netifd: UCI parameter to sort name servers in resolv.conf.auto

On 2016-09-05 10:45, Hans Dedecker wrote: > Hi Felix, > > Current implementation in netifd writes the dns servers into > resolv.conf.auto file based on the order of the interfaces in the > interface list which is alphabetical sorted. The resolver, in this > case dnsmasq, reads the

[OpenWrt-Devel] a little of confusion about the official trunk....

Hello folks, I have noticed that now there are currently two openwrt trunk repos : 1. https://github.com/openwrt/openwrt 2. https://git.openwrt.org/?p=openwrt.git;a=summary is the official development continuing officially on the first one since the latest commit on the second one

[OpenWrt-Devel] RFC netifd: UCI parameter to sort name servers in resolv.conf.auto

Hi Felix, Current implementation in netifd writes the dns servers into resolv.conf.auto file based on the order of the interfaces in the interface list which is alphabetical sorted. The resolver, in this case dnsmasq, reads the resolv.conf.auto file and queries the nameserver(s) in the order

Re: [OpenWrt-Devel] [PATCH ubus 0/3] ubusd: fix ACL checking

Ping? On 2016-08-25 13:54, Denis Osvald wrote: > Denis Osvald (3): > ubusd: don't check ACL when object is NULL > ubusd: fallback to linear search on ACLs to fix wildcards > ubusd: fix inverted check in ubusd_reply_add > > ubusd_acl.c | 20 +--- > 1 file changed, 9