Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare 0.16.0 #285

Merged
merged 1 commit into from
Dec 30, 2023
Merged

Prepare 0.16.0 #285

merged 1 commit into from
Dec 30, 2023

Conversation

grembo
Copy link
Collaborator

@grembo grembo commented Dec 30, 2023

No description provided.

@grembo grembo merged commit 9ac5a5f into bsdpot:master Dec 30, 2023
2 checks passed
dblane-digicatapult added a commit to digicatapult/pot that referenced this pull request Feb 20, 2024
* Make init/de-init less intrusive (bsdpot#284)

This adds the flag "-m" to be minimally intrusive. Also allows
de-init to use "-p pf_file" to specify the firewall rulesets
(this way it's symmetrical to init).

Rename "-f pf_file" to "-p pf_file" in init (as "-f" was already
taken in de-init), but keep "-f" as an alias for the time being.

Add flag "-s" to init (do not alter syslogd configuration).

Some minor cleanup of variable names while there.

Fixes bsdpot#85

* Find bridge interfaces by interface group (bsdpot#282)

This allows users to give their bridges custom names.
We might make use of this as well in the future
(think $POT_BRIDGE_NAME).

* New global config to isolate vnet pots (bsdpot#283)

This new global setting called `POT_ISOLATE_VNET_POTS` sets bridge
member epaira interfaces to be private, preventing them from
forwarding traffic to each other. This helps with overall security,
but (primarily) makes sure that pots in larger nomad clusters don't
talk to each other using direct communication instead of published
(natted) endpoints.

This could be a more fine-grained per pot setting in the future,
in our setups we only ever needed a global setting decided by
the infrastructure operator (so, e.g., in the nomad cluster,
everything uses this setting, whereas in the more static part
forming the infrastructure the nomad cluster relies on, direct
communication between pots is wanted) and changing it per pot
would be a disadvantage - hence this implementation.

* Fix typo in set-status.sh

* Prepare 0.16.0 (bsdpot#285)

---------

Co-authored-by: grembo <freebsd@grem.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant