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
|
|
@ -344,10 +344,16 @@ in
|
|||
"log"
|
||||
"reject"
|
||||
];
|
||||
default = "log";
|
||||
default = if egressCfg.intercept.enable then "reject" else "log";
|
||||
defaultText = lib.literalMD ''
|
||||
`"reject"` while `egress.intercept.enable` is on, `"log"` otherwise
|
||||
'';
|
||||
description = ''
|
||||
What the `inet hive_egress` table does with traffic the host forwards
|
||||
from the agent bridge to anywhere but the bridge. In `log` and
|
||||
from the agent bridge to anywhere but the bridge. The default is `reject`
|
||||
on a host with the intercept on, which a hive controller host has, and
|
||||
`log` on a host without it, because `reject` without the intercept would
|
||||
refuse every agent's web traffic. In `log` and
|
||||
`reject` the traffic of the MACs in the `direct_mac` set (the unrestricted
|
||||
agents and the service containers) is accepted and never logged, and so
|
||||
is TCP from an agent to an address and port in the `agent_allow` set
|
||||
|
|
|
|||
Loading…
Reference in a new issue