Skip to contentSkip to conversation

Can't compile 1.2.11 because of dstlimit?

DISCUSSION Bob McLaren 2 participants 3 messages Jul 6, 2004 – Jul 12, 2004

lore
Share & tools
lore
#0 lore raw

I don't patch/recompile my kernels or applications very often so please let me know what I've done wrong here.

In order to take advantage of the 'time' match capability of iptables, I have upgraded from iptables-1.2.8-8.72.3 on linux-2.4.20-18.7
to
iptables-1.2.11 on linux-2.4.20-18.7custom (enabled ipt_time)
(note: This is on a RedHat 7.3 box)

I have successfully recompiled my kernel. But now, when I attempt to compile iptables, I get an error regarding "dstlimit".
I don't necessarily need dstlimit, so I tried disabling it in my kernel options (although I didn't recompile the kernel after that), but that doesn't seem to fix the problem.

Here is an extract of the error that I see when I run make for iptables. ANY help or a point in the right direction would be greatly appreciated.
-------------------------------------------------------------------------------
ld -shared -o extensions/libipt_TRACE.so extensions/libipt_TRACE_sh.o
cc -O2 -Wall -Wunused -I/usr/src/linux-2.4.20-18.7/include -Iinclude/ -DIPTABLES_VERSION=\"1.2.11\" -fPIC -o extensions/libipt_TTL_sh.o -c extensions/libipt_TTL.c ld -shared -o extensions/libipt_TTL.so extensions/libipt_TTL_sh.o
cc -O2 -Wall -Wunused -I/usr/src/linux-2.4.20-18.7/include -Iinclude/ -DIPTABLES_VERSION=\"1.2.11\" -fPIC -o extensions/libipt_ULOG_sh.o -c extensions/libipt_ULOG.c ld -shared -o extensions/libipt_ULOG.so extensions/libipt_ULOG_sh.o
cc -O2 -Wall -Wunused -I/usr/src/linux-2.4.20-18.7/include -Iinclude/ -DIPTABLES_VERSION=\"1.2.11\" -fPIC -o extensions/libipt_dstlimit_sh.o -c extensions/libipt_dstlimit.c extensions/libipt_dstlimit.c: In function `init':
extensions/libipt_dstlimit.c:104: structure has no member named `cfg'
extensions/libipt_dstlimit.c:105: structure has no member named `cfg'
extensions/libipt_dstlimit.c:106: structure has no member named `cfg'
extensions/libipt_dstlimit.c: In function `parse':
extensions/libipt_dstlimit.c:138: structure has no member named `cfg'
-------------------------------------------------------------------------------

#1 lore raw
Quoted 4 lines · Bob McLaren

...
I have successfully recompiled my kernel. But now, when I attempt to compile iptables, I get an error regarding "dstlimit".
...

Well, I'm closer to figuring it out...

I noticed that the ipt_dstlimit.h in my iptables source tree did not match the ipt_dstlimit.h in my kernel source tree.
The one in my kernel source tree does not define a "cfg" struct. Which would explain the error I'm getting, but I still don't understand what I need to do to resolve this.

Why would both source trees have ipt_dstlimit.h files?
Why would my 2.4.20 kernel source tree have an outdated ipt_dstlimit.h file?
Can I just move my RedHat 7.3 box from 2.4.20 -> 2.6.7 without worry of bugs/issues? I don't know how stable that new kernel is.

#2 lore raw

Hi Bob,

Quoted 7 lines · Bob McLaren

I noticed that the ipt_dstlimit.h in my iptables source tree did not match the ipt_dstlimit.h in my kernel source tree.
The one in my kernel source tree does not define a "cfg" struct. Which would explain the error I'm getting, but I still don't understand what I need to do to resolve this.

Why would both source trees have ipt_dstlimit.h files?

No official kernel sources contain the ipt_dstlimit.h file.

The header file was added to the iptables source as forward-compatibility until the dstlimit feature is submitted to the kernel.

Quoted 1 line

Why would my 2.4.20 kernel source tree have an outdated ipt_dstlimit.h file?

That's due to the RedHat policy on how to add and maintain features, which hasn't yet been submitted into the official kernel.

Quoted 2 lines

Can I just move my RedHat 7.3 box from 2.4.20 -> 2.6.7 without worry of bugs/issues? I don't know how stable that new kernel is.

If you worry about the 2.6 kernel tree, you are free to use 2.4 - except that use a standard kernel source release from kernel.org instead of a vendor-specific one.

Best regards,
Jozsef
-
E-mail : [email protected], [email protected] PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics

          H-1525 Budapest 114, POB. 49, Hungary