-
Notifications
You must be signed in to change notification settings - Fork 31
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
How to disable pf bridge filtering #281
Comments
@einsibjarni you have various options.
Replace the IP with what you're using as POT_GATEWAY. For IPv6 the selection is done by finding if the external pot interface is part of it (so it's a bit more complex). I have no experience using it, but I would assume it's something like:
Note that this is all from the top of my head, so take it with a grain of salt ;) |
I have an ansible playbook that deploys hosts running nomad + pot + pot task driver.
The pots I deploy are using public-bridge dual stack. Pf is enabled and my current pf.conf is generated from a template in ansible, and it blocks everything not strictly allowed. As-is, it blocks traffic from jails on the bridge interface, and IPv6 rtsol/rtadv packets.
I can't disable bridge filtering in sysctl.conf, because there has to be a bridge created before I can apply the sysctl changes.
Anybody have experience with this? Should I disable filtering in a pot hook or create a dummy bridge at boot? Or should I leave filtering enabled and add the rules I need in a sensible way?
The text was updated successfully, but these errors were encountered: