mirror of
https://github.com/openwrt/openwrt.git
synced 2024-12-26 17:01:14 +00:00
7541d30c9c
f52bb5b fix previous commit
18eac67 Fix entries in /etc/hosts disabling static leases.
f8c77ed Fix removal of DHCP_CLIENT_MAC options from DHCPv6 relay replies.
4bf62f6 Tidy cache_blockdata_free()
9c0d445 Fix e7bfd556c079c8b5e7425aed44abc35925b24043 to actually work.
2896e24 Check for not(DS or DNSKEY) in is_outdated_cname_pointer()
a90f09d Fix crash freeing negative SRV cache entries.
5b99eae Cache SRV records.
2daca52 Fix typo in ra-param man page section.
2c59473 File logic bug in cache-marshalling code. Introduced a couple of commits back.
cc921df Remove nested struct/union in cache records and all_addr.
ab194ed Futher address union tidying.
65a01b7 Tidy address-union handling: move class into explicit argument.
bde4647 Tidy all_addr union, merge log and rcode fields.
e7bfd55 Alter DHCP address selection after DECLINE in consec-addr mode. Avoid offering the same address after a recieving a DECLINE message to stop an infinite protocol loop. This has long been done in default address allocation mode: this adds similar behaviour when allocaing addresses consecutively.
The most relevant fix for openwrt is 18eac67 (& my own local f52bb5b
which fixes a missing bracket silly) To quote the patch:
It is possible for a config entry to have one address family specified by a
dhcp-host directive and the other added from /etc/hosts. This is especially
common on OpenWrt because it uses odhcpd for DHCPv6 and IPv6 leases are
imported into dnsmasq via a hosts file.
To handle this case there need to be separate *_HOSTS flags for IPv4 and IPv6.
Otherwise when the hosts file is reloaded it will clear the CONFIG_ADDR(6) flag
which was set by the dhcp-host directive.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
33 lines
1.1 KiB
Diff
33 lines
1.1 KiB
Diff
From 07e25da5bf26d46aad4f1d2eb19b260789182004 Mon Sep 17 00:00:00 2001
|
|
From: Simon Kelley <simon@thekelleys.org.uk>
|
|
Date: Sun, 16 Dec 2018 18:21:58 +0000
|
|
Subject: [PATCH 13/30] Treat DS and DNSKEY queries being forwarded the same as
|
|
those locally originated.
|
|
|
|
The queries will not be forwarded to a server for a domain, unless
|
|
there's a trust anchor provided for that domain. This allows, especially,
|
|
suitable proof of non-existance for DS records to come from
|
|
the parent domain for domains which are not signed.
|
|
|
|
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
|
|
---
|
|
src/rfc1035.c | 7 +++++++
|
|
1 file changed, 7 insertions(+)
|
|
|
|
--- a/src/rfc1035.c
|
|
+++ b/src/rfc1035.c
|
|
@@ -916,6 +916,13 @@ unsigned int extract_request(struct dns_
|
|
if (qtype == T_ANY)
|
|
return F_IPV4 | F_IPV6;
|
|
}
|
|
+
|
|
+ /* F_DNSSECOK as agument to search_servers() inhibits forwarding
|
|
+ to servers for domains without a trust anchor. This make the
|
|
+ behaviour for DS and DNSKEY queries we forward the same
|
|
+ as for DS and DNSKEY queries we originate. */
|
|
+ if (qtype == T_DS || qtype == T_DNSKEY)
|
|
+ return F_DNSSECOK;
|
|
|
|
return F_QUERY;
|
|
}
|