bugzilla-daemon@netfilter.org
2003-Feb-10 11:45 UTC
[Bug 25] Can't compile iptables-1.2.7a.tar.bz2
https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=25 delaunois@info.ucl.ac.be changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED OS/Version|other |All Resolution| |INVALID ------- Additional Comments From delaunois@info.ucl.ac.be 2003-02-10 12:45 ------- This is not really a bug, but a compatibility issue. The problem is that the release of pom is now decoupled with the release of iptables userspace utilities. And now people are using a recent pom with an old iptables. This is what happens here. The ROUTE target is still in development and I upgraded it recently. iptables-1.2.7a doesn't support the new version of the target. The version of libipt_ROUTE.c compatible with patch-o-matic-20030107 is version 1.3. You can download the right libipt_ROUTE.c at http://cvs.netfilter.org/cgi-bin/cvsweb/~checkout~/netfilter/userspace/extensions/libipt_ROUTE.c?rev=1.3&content-type=text/plain Just replace the corresponding file in your iptables-1.2.7a. However, there is now a newer version of this target (1.4). If you want to use it, I best recommend to use the CVS version of both iptables and patch-o-matic. I'm afraid, but this kind of problem is likely to appear more frequently and for other targets/matches as now path-o-matic and iptables are not released synchronously. A solution to avoid this is to take care about backward and forward compatibility. But the ROUTE target is still in active development and I really don't want to care about that now. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
Maybe Matching Threads
- [ANNOUNCE] New netfilter/iptables patch-o-matic release
- [ANNOUNCE] New netfilter/iptables patch-o-matic release
- [ANNOUNCE] Release of iptables-1.2.7a
- Re: Error: Your kernel and/or iptables does not not support policy match: ipsec
- [Bug 39] New: can't execute 'make modules'