-
Notifications
You must be signed in to change notification settings - Fork 349
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
firewall: T6216: replace plus symbols (allowed by IPset but not NFT) in group names with underscores #3290
Conversation
v4_found = True | ||
if group_type in v6_groups and not v6_found: | ||
v6_found = True | ||
new_group_name = group_name.replace('+', '_') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if the config has both LAN+VLANS
and LAN_VLANS
groups already? :)
It's a rather unlikely situation, but I think we should agree what exactly we should do if our normalized name already exists in the old config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Iv'e submitted a patch for this situation
…o avoid errors when using character <+> in 1.3 in firewall groups and custom firewall chains.
And new tittle indicates that this path is only for firewall groups, while it actually also applies for firewall ruleset |
@Mergifyio backport sagitta |
✅ Backports have been created
|
Change Summary
Add patch while migrating from 1.3 to 1.4 in order to avoid errors when using character <+> in 1.3 in firewall groups and custom firewall chains.
Types of changes
Related Task(s)
Related PR(s)
Component(s) name
firewall
Proposed changes
How to test
Firewall config running on 1.3.4:
And after upgrade to custom build for 1.5 with this patch:
Smoketest result
test_firewall.py -- OK
Checklist: