From: "Nathan" <etherwolf@sopris.net>
To: "Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Updated to kernel 2.4.19 and now ipchains and iptables are broke.
Date: Thu, 26 Sep 2002 10:50:08 -0600 [thread overview]
Message-ID: <003401c2657c$c5a12e60$f101010a@nathan> (raw)
This is surely the greenest of green questions (sorry), but I finally got my
kernel re-compiled the way I want it using the 2.4.19 sources from
kernel.org. It loads, seems to be working fine, except ipchains and
iptables... ipchains insists that it is incompatible with my kernel, and
iptables isn't sure what's going on but it thinks maybe something (itself or
the kernel) needs upgrading. Well fine. I downloaded the latest versions of
ipchains/tables from rpmfind and upgraded, same thing.
Details: OS is RH 7.3 on an i686 (P3), kernel was 2.4.18-3 that comes with
RH 7.3, ipchains was 1.3.10-10, updated to 1.3.10-17 but when I do
ipchains -V, it says it's still 1.3.10 built in Sep. 2000. iptables was
1.2.5 but is now 1.2.6a.
I haven't been able to find any actual solutions off google for this... a
few people mention the same problem but no fixes. Can someone point this
rookie in the right direction to fix my packet filters? :-)
Also a quick question: can anyone give me either a real quick answer or a
link to more reading on which is better for routing/firewalling/VPN,
ipchains or iptables?
Many thanks!
# Nathan
next reply other threads:[~2002-09-26 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 16:50 Nathan [this message]
2002-09-27 7:07 ` Updated to kernel 2.4.19 and now ipchains and iptables are broke Harald Welte
2002-09-26 17:02 Marc-Christian Petersen
2002-09-26 17:11 ` Nathan
2002-09-26 17:19 ` Marc-Christian Petersen
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='003401c2657c$c5a12e60$f101010a@nathan' \
--to=etherwolf@sopris.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).