Well, again, the fact that it worked before doesn't mean it's a bug and
therefor needs special handling.
This bug can be closed as WONTFIX.
a.
On 06-Feb-12 17:07, Julia Longtin wrote:
No, i mean something in the changes file, so you know *before* you
restart your firewall, and the port
The fact that your configuration file format has CHANGED, without an entry
in the CHANGELOG is certainly a bug, and i believe asking for a CHANGELOG
entry so that system administrators do not have their firewall rules
dropped randomly, without warning, is appropriate, and represents a bug in
your
Oh, that makes sense to me... except since it WAS valid syntax, it means
that when it STOPPED being valid syntax, i need a little more warning than
oh, all your port forwards no longer exist, have a nice day!. I read
debchanges, so at least a warning to sysadmins that the syntax that used to
be
Well it does do that:
Restarting Arno's Iptables Firewall...
** WARNING: In Variable NAT_FORWARD_TCP, Rule: ~10.100.__0.117~80
is ignored.
Feb 06 13:27:41 WARNING: Not all firewall rules are applied.
a.
On 06-Feb-12 12:54, Julia Longtin wrote:
Oh, that makes sense to me... except since
No, i mean something in the changes file, so you know *before* you restart
your firewall, and the port forwards are dropped. an outage and warning
that does not tell one what to do to fix it is certainly an issue.
Julia Longtin
On Mon, Feb 6, 2012 at 12:28 PM, Arno van Amersfoort
Package: arno-iptables-firewall
Version: 2.0.1-1
Severity: important
Dear Maintainer,
After performing an upgrade, i have found that the format of the rules expected
in firewall.conf have changed.
Instead of accepting a blank source IP, it now requires a source IP, or
parse_rules fails, and
You mean that NAT_FORWARD_TCP=10.100.0.117~80 causes the problem
and NAT_FORWARD_TCP=0/0~10.100.0.117~80 fixes that? I tried
reproducing it, but I can't get it to fail. Could you provide a snippet
of the error?
thanks.
Arno
On 03-Feb-12 15:37, Julia Longtin wrote:
Package:
7 matches
Mail list logo
