From: Bob McLaren <BobMcLaren@fssi-ca.com>
To: netfilter@lists.netfilter.org
Subject: Re: Can't compile 1.2.11 because of dstlimit?
Date: Fri, 09 Jul 2004 12:03:59 -0700 [thread overview]
Message-ID: <40EEEC1F.7090201@fssi-ca.com> (raw)
In-Reply-To: <40EB1C80.4050108@fssi-ca.com>
Bob McLaren wrote:
> ...
> 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.
next prev parent reply other threads:[~2004-07-09 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 21:41 Can't compile 1.2.11 because of dstlimit? Bob McLaren
2004-07-09 19:03 ` Bob McLaren [this message]
2004-07-12 9:51 ` Jozsef Kadlecsik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40EEEC1F.7090201@fssi-ca.com \
--to=bobmclaren@fssi-ca.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox