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
|
|
@ -61,10 +61,10 @@ key changed and you didn't change the machine, don't clear it: something else
|
|||
answers at that address.
|
||||
|
||||
The SSH switch and the CA don't open the network. The default `egress.forward`
|
||||
of `log` lets the agent's direct connection to the machine's port through. If
|
||||
you set it to `reject`, the hive refuses the connection unless you gave the
|
||||
agent a named connection to that host and port (see
|
||||
[Named connections](#named-connections)). See
|
||||
is `reject`, so the hive refuses the agent's direct connection to the machine's
|
||||
port unless you gave the agent a named connection to that host and port (see
|
||||
[Named connections](#named-connections)). If you set `egress.forward` to `log`,
|
||||
the connection goes through. See
|
||||
[the network page](../../4-implementation/networking/network.md).
|
||||
|
||||
## 2. Make a machine trust the CA
|
||||
|
|
|
|||
Loading…
Reference in a new issue