egress: the forward chain refuses by default where the intercept is on
egress.forward defaults to reject while egress.intercept.enable is on (a hive controller host turns it on) and to log otherwise, because reject without the intercept would refuse all web traffic and an assertion already forbids it. log stays an explicit choice. The hive-squid VM test runs its log-mode half on the base node, so the base pins forward = log at mkDefault priority and the reject specialisation overrides it. A module-eval case covers the default on a controller host, on a host without the intercept, and an explicit log.
This commit is contained in:
parent
d88a0cc526
commit
b8851743e8
1 changed files with 86 additions and 35 deletions
|
|
@ -228,9 +228,12 @@ pkgs.testers.runNixOSTest {
|
|||
pkgs.mkpasswd
|
||||
pkgs.nftables
|
||||
];
|
||||
# The reject-mode half of the test switches to this at its end. The
|
||||
# forward mode is fixed when the node evaluates; the switch reloads
|
||||
# `hive-egress` with the other ruleset.
|
||||
# The log-mode half of the test runs on this node, and the reject-mode
|
||||
# half switches to the specialisation at its end. The forward mode is
|
||||
# fixed when the node evaluates; the switch reloads `hive-egress` with
|
||||
# the other ruleset. The default is `reject` while the intercept is on,
|
||||
# so the base pins `log`, at a priority the specialisation overrides.
|
||||
services.hyperhive.deploy.hive-controller.egress.forward = lib.mkDefault "log";
|
||||
specialisation.reject.configuration.services.hyperhive.deploy.hive-controller.egress.forward =
|
||||
"reject";
|
||||
services.hyperhive.deploy.hive-controller.squid.selfcheck.unrestrictedCanary = "other.t.local";
|
||||
|
|
|
|||
Loading…
Reference in a new issue