-
Notifications
You must be signed in to change notification settings - Fork 759
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
[plugins] inject new firewall rules #993
Comments
|
Note to self: For now it seems we only have to insert anchors and the utilities will be able to inject their rules at will. This also includes relayd and miniupnpd, which could be split off as plugins in the future. |
|
@fichtner that's only part of the story here... let's keep this for Friday. |
|
of course, only keeping some notes for consistency |
simple start, wrap anchor registration into plugin system, use miniupnpd as an example. use registerAnchor() to register new anchors for pf into the main firewall script, we've hooked head/tail options and the different anchor types. anchorToText() will extract the registered anchors back for the specified types and place in the script (head/tail) in text format for pf. our new codebase was already hooked using legacy_bindings.inc, no additional includes needed to construct \OPNsense\Firewall\Plugin().
|
the framework works, no need to keep this ticket anymore great work by @AdSchellevis |
Just an idea, probably won't make it for 16.7. But we could extend the plugin system to propagate its needed firewall rules, which will be automatically installed into the config.xml.
(like new interfaces do in current master)
Advantage of doing this is that the firewall config shows the actual settings its using and would simplify the fiter.inc a lot.
Ideas, no concrete plan yet.....
The text was updated successfully, but these errors were encountered: