Messages in this thread | | | Date | Fri, 15 Feb 2002 00:37:56 +0100 | From | Harald Welte <> | Subject | Re: 2.4.18-pre9: iptables screwed? |
| |
On Thu, Feb 14, 2002 at 08:01:11PM +0100, Chris Chabot wrote: > I ran into the same problems with 2.4.18pre9, however upgrading to > iptables 1.2.5 fixed the problem. (there's no redhat packages for it > yet, i did a compile of the source pkg)
As stated in my earlier replies to this issue:
Certain vendor RPMs for iptables have (unvoluntarily?) compiled in iptables debugging . At least RedHat and Mandrake seem to be falling in this category.
The debugging code does not work with recent kernels, but nobody was assuming debugging would be enabled in production systems.
There are two solutions to the problem:
a) update to an iptables package which doesn't have debugging enabled (which is default with iptables source as distributed by the netfilter coreteam)
or
b) use iptables from current CVS when you really need to have debugging enabled. I will release iptables-1.2.6 soon, which will also have the debugging code fixed.
> -- Chris
-- Live long and prosper - Harald Welte / laforge@gnumonks.org http://www.gnumonks.org/ ============================================================================ GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M+ V-- PS++ PE-- Y++ PGP++ t+ 5-- !X !R tv-- b+++ !DI !D G+ e* h--- r++ y+(*) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |