-
Notifications
You must be signed in to change notification settings - Fork 188
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
fast activation error handling #22
Comments
I have just greped the line. Normaly we should have better error control by detecting the configuration command that generated the wrong line. This requires a lot of re-writing though. |
@philwhineray I have not tested this in ipv6. |
I can confirm the offending line is correctly reported with an IPv6 error too. To get the original line can we add comments to the generated iptables-restore file linking back to the original firehol.conf line? |
I guess comments will do it. |
In fast activation mode, if it fails it should at least print the offending line that broke the firewall.
iptables-restore does provide the line number.
The text was updated successfully, but these errors were encountered: