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#36277 - [iptables] --reap option is accidentally disabled
Attached to Project:
Arch Linux
Opened by Oebele Drijfhout (tiemen) - Friday, 26 July 2013, 08:13 GMT
Last edited by Ronald van Haren (pressh) - Monday, 14 October 2013, 19:01 GMT
Opened by Oebele Drijfhout (tiemen) - Friday, 26 July 2013, 08:13 GMT
Last edited by Ronald van Haren (pressh) - Monday, 14 October 2013, 19:01 GMT
|
DetailsDescription:
From the netfilter git: "The reap functionality appears to have been accidentally disabled by (74ded72 libxt_recent: add --mask netmask) since iptables 1.4.15 and later. This adds a patch to restore reap functionality for recent_opts_v1. Patch obtained via: http://patchwork.openwrt.org/patch/3812/"; http://git.netfilter.org/iptables/commit/?id=8cf6fb833840d794289f2abf04b2c5cade5a37bf Currently this breaks the new events feature in shorewall 4.5.19. Steps to reproduce: iptables -A %IfEvent -m recent --rcheck --second 120 --reap --hitcount 5 --name SSH --rsource -j SSH_BLACKLIST |
This task depends upon
Closed by Ronald van Haren (pressh)
Monday, 14 October 2013, 19:01 GMT
Reason for closing: Upstream
Additional comments about closing: I suppose this is fixed in the latest upstream version
Monday, 14 October 2013, 19:01 GMT
Reason for closing: Upstream
Additional comments about closing: I suppose this is fixed in the latest upstream version