You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nixos/tayga: add option to allow toggling WKPF strict compliance
The RFC requires that we don't allow access to non-global v4 addresses
using the well-known 64:ff9b:: prefix, but there are some deployments
where it's convenient to permit this.
To make this work in tests, disable wkpf-strictness via the config
option introduced in bc18503e2ff1ee48ac472a67ba982dae76a5c2d3.
Tayga added 100.64.0.0 to the set of WKPF in
4dff17ef61821f5bc1996ce687a3dc317fd4fa50.
Copy file name to clipboardExpand all lines: nixos/modules/services/networking/tayga.nix
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,8 @@ let
27
27
${optionalString((builtins.lengthcfg.log)>0)''
28
28
log ${concatStringsSep" "cfg.log}
29
29
''}
30
+
31
+
wkpf-strict ${ifcfg.wkpfStrictthen"yes"else"no"}
30
32
'';
31
33
32
34
addrOpts=
@@ -145,6 +147,12 @@ in
145
147
[ "drop" "reject" "icmp" "self" ]
146
148
'';
147
149
};
150
+
151
+
wkpfStrict=mkOption{
152
+
type=types.bool;
153
+
default=true;
154
+
description="Enable restrictions on the use of the well-known prefix (64:ff9b::/96) - prevents translation of non-global IPv4 ranges when using the well-known prefix. Must be enabled for RFC 6052 compatibility.";
0 commit comments