-
Notifications
You must be signed in to change notification settings - Fork 298
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
neutron2snabb egress filters #245
Conversation
Minor nitpick: There is a comment
at https://github.com/SnabbCo/snabbswitch/pull/245/files#diff-e6dc95ae179bd7a0f203adc2547680c0L84 which I guess can be removed with this commit? |
d9364d9
to
ad1bc4e
Compare
yes, this was no longer true. also corrected to respect the merged PR #237, which moved most of the code from |
72ef863
to
f896738
Compare
The last commit fixes the merge history mismatch, hopefully the snabbot would approve it! |
fe2e311
to
f16f6ce
Compare
f16f6ce
to
995324f
Compare
c7731d3
to
581f55a
Compare
3b7ac30
to
2ecb4ae
Compare
@eugeneia could you please pull this into your tree, make yourself happy with the way |
The |
2ecb4ae
to
2ca2e6b
Compare
E.g. just merge this already! ;) |
Sorry to be slow about that! |
Update performance
Creates egress filter rules from Neutron config database and sets up a
packet_filter
app to enforce them.Fixes some loop reinitialization to let the configDB -> filter rules create more than one filter rules.
I've tested this only with a fake hand-built config database. It does handle anything i throw at it as long as it seems to comply the general syntax, but it would be great if somebody with a Neutron installation could help in more "real worlf" tests.