-
Notifications
You must be signed in to change notification settings - Fork 10
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
outerface? #74
Comments
Hi, this is currently not possible. Are you interested to provide a patch for this? |
@bastelfreak I might have a look when I get a chance, is it just rules.pp or are there definitions elsewhere that also would need updating. |
I already implemented magic for the interface: Lines 147 to 173 in 936d5f7
You probably need to update the rule.pp and some tests. And you need to implement a check that prohibits settings |
Sorry If i Misunderstood you but why would I want to prevent setting interface and outerface in the same rule, that's a perfectly valid thing to do in a forward chain. |
oh true, that's a valid usecase! |
@bastelfreak I had a play but I'm afraid it's way beyond my understanding of how to write a puppet module, I'm right at the beginner level in that regard. All I ended up doing was zapping most of my rules (whoops) although I did seem to manage to add the outerface in the output chain. It seems it's not just the case of copying you existing magic and writing an elsif to deal with outerface. The only thing I did notice is I can't help think the rules are overly complicated for a single rule for instance
can easily become
It really depends on if you wanted to put multiple rules with the same interface definition, then it would make sense. e.g
That said for an interface AND outerface it might have to be a one liner I'm not sure if
Is actually valid or not. |
#78 - @bastelfreak might be worth a look, but I fear it's probably not upto the required code quality standards. |
Is outerface supported by the module?, I did try using it in the rule but it didn't seem to like it.
outerface does occasionally come in handy for forward rules where you want to match the outgoing interface either instead of or as well as the incoming one.
The text was updated successfully, but these errors were encountered: