From 8eb8355567a56d3be58aae59741a60824a105110 Mon Sep 17 00:00:00 2001 From: Jeremy Harris Date: Tue, 19 Feb 2019 14:45:27 +0000 Subject: [PATCH] Docs: Add note on lsearch for IPv4-mapped IPv6 addresses Cherry-picked from: 52af443324, c77d3d85fe (cherry picked from commit 8dde16b89efe2138f92cbfa6c59fb31dc80ec22a) (cherry picked from commit a457174087afff3685856e295bd8ffcfefe0e05e) --- doc/doc-docbook/spec.xfpt | 11 ++++++++++- doc/doc-txt/ChangeLog | 2 +- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index 112c1efa2..0bce6fe86 100644 --- a/doc/doc-docbook/spec.xfpt +++ b/doc/doc-docbook/spec.xfpt @@ -6745,6 +6745,11 @@ lookup types support only literal keys. &*Warning 2*&: In a host list, you must always use &(net-iplsearch)& so that the implicit key is the host's IP address rather than its name (see section &<>&). + +.new +&*Warning 3*&: Do not use an IPv4-mapped IPv6 address for a key; use the +IPv4. Such addresses being searched for are converted to IPv4. +.wen .next .cindex "linear search" .cindex "lookup" "lsearch" @@ -8663,8 +8668,12 @@ to quote keys was made available in &(lsearch)& files. However, the more recently implemented &(iplsearch)& files do require colons in IPv6 keys (notated using the quoting facility) so as to distinguish them from IPv4 keys. For this reason, when the lookup type is &(iplsearch)&, IPv6 addresses are -converted using colons and not dots. In all cases, full, unabbreviated IPv6 +converted using colons and not dots. +.new +In all cases except IPv4-mapped IPv6, full, unabbreviated IPv6 addresses are always used. +The latter are converted to IPv4 addresses, in dotted-quad form. +.wen Ideally, it would be nice to tidy up this anomalous situation by changing to colons in all cases, given that quoting is now available for &(lsearch)&. diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog index 13c2cb64b..35d26b3b9 100644 --- a/doc/doc-txt/ChangeLog +++ b/doc/doc-txt/ChangeLog @@ -29,7 +29,7 @@ JH/07 GnuTLS: Our use of late (post-handshake) certificate verification, under TLS connection attempt, so that the normal retry-in-clear can work (if suitably configured). -JB/01 BZg 2375: fix expansions of 822 addresses having comments in local-part +JB/01 Bug 2375: fix expansions of 822 addresses having comments in local-part and/or domain. Found and fixed by Jason Betts. -- 2.30.2