mirror of
https://github.com/pi-hole/dnsmasq.git
synced 2025-12-19 10:18:25 +00:00
2.81rc5 CHANGELOG and man/dnsmasq.8 manual page improvements
Hi Simon, > Add --shared-network config. This enables allocation of addresses > the DHCP server in subnets where the server (or relay) doesn't > have an interface on the network in that subnet. Many thanks to > kamp.de for sponsoring this feature. Does this paragraph lack a preposition "by" early on the 2nd line, or am I mis-guessing the purpose? ...enables allocation of addresses *by* the DHCP server... The manual page also seems to offer room for linguistic improvement (apparently written by a German, so I see the typical patterns, and also the misuse of which vs. that. I am attaching a patch series vs. git to fix several issues in the manpage and CHANGELOG. From 35b88d98429e2fe016d9989d220f6faf2b933764 Mon Sep 17 00:00:00 2001 From: Matthias Andree <matthias.andree@gmx.de> Date: Sun, 5 Apr 2020 11:18:05 +0200 Subject: [PATCH 1/5] man/dnsmasq.8: Properly capitalize DHCP acronym.
This commit is contained in:
committed by
Simon Kelley
parent
532246fc9e
commit
081a1c4014
10
CHANGELOG
10
CHANGELOG
@@ -1,12 +1,12 @@
|
||||
version 2.81
|
||||
Impove cache behaviour for TCP connections. For ease of
|
||||
Improve cache behaviour for TCP connections. For ease of
|
||||
implementaion, dnsmasq has always forked a new process to handle
|
||||
each incoming TCP connection. A side-effect of this is that
|
||||
any DNS queries answered from TCP connections are not cached:
|
||||
when TCP connections were rare, this was not a problem.
|
||||
With the coming of DNSSEC, it's now the case that some
|
||||
With the coming of DNSSEC, it is now the case that some
|
||||
DNSSEC queries have answers which spill to TCP, and if,
|
||||
for instance, this applies to the keys for the root then
|
||||
for instance, this applies to the keys for the root, then
|
||||
those never get cached, and performance is very bad.
|
||||
This fix passes cache entries back from the TCP child process to
|
||||
the main server process, and fixes the problem.
|
||||
@@ -35,7 +35,7 @@ version 2.81
|
||||
configuration.
|
||||
|
||||
Add --shared-network config. This enables allocation of addresses
|
||||
the DHCP server in subnets where the server (or relay) doesn't
|
||||
by the DHCP server in subnets where the server (or relay) does not
|
||||
have an interface on the network in that subnet. Many thanks to
|
||||
kamp.de for sponsoring this feature.
|
||||
|
||||
@@ -66,7 +66,7 @@ version 2.81
|
||||
Evgenii Seliavka for the suggestion and initial patch.
|
||||
|
||||
In the router advert code, handle case where we have two
|
||||
different interfaces on the same IPv6 net, and we're doing
|
||||
different interfaces on the same IPv6 net, and we are doing
|
||||
RA/DHCP service on only one of them. Thanks to NIIBE Yutaka
|
||||
for spotting this case and making the initial patch.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user