Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36272 - [shorewall] shorewall 4.5.19 adds --reap option but it's removed from iptables
Attached to Project:
Community Packages
Opened by Oebele Drijfhout (tiemen) - Thursday, 25 July 2013, 12:21 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 26 July 2013, 21:16 GMT
Opened by Oebele Drijfhout (tiemen) - Thursday, 25 July 2013, 12:21 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 26 July 2013, 21:16 GMT
|
DetailsDescription:
when using the new Events feature, shorewall tries to generate a config using the iptables --reap option, but that option has been removed in 1.4.16. shorewall check runs without errors, but when you actually start shorewall, it fails: Running /sbin/iptables-restore... iptables-restore v1.4.19.1: unknown option "--reap" Error occurred at line: 85 Try `iptables-restore -h' or 'iptables-restore --help' for more information. ERROR: iptables-restore Failed. Input is in /var/lib/shorewall/.iptables-restore-input Processing /etc/shorewall/stop ... Processing /etc/shorewall/tcclear ... Running /sbin/iptables-restore... IPv4 Forwarding Enabled Processing /etc/shorewall/stopped ... /usr/share/shorewall/lib.common: line 113: 9618 Terminated $SHOREWALL_SHELL $script $options $@ Changing line 101 in /usr/share/shorewall/action.IfEvent from $duration .= '--reap '; to $duration .= ''; solves the problem for me. |
This task depends upon
Closed by Jelle van der Waa (jelly)
Friday, 26 July 2013, 21:16 GMT
Reason for closing: Upstream
Additional comments about closing: it's actually a (fixed) bug in iptables: http://git.netfilter.org/iptables/commit /?id=8cf6fb833840d794289f2abf04b2c5cade5 a37bf
Friday, 26 July 2013, 21:16 GMT
Reason for closing: Upstream
Additional comments about closing: it's actually a (fixed) bug in iptables: http://git.netfilter.org/iptables/commit /?id=8cf6fb833840d794289f2abf04b2c5cade5 a37bf