From: Athan <netfilter@miggy.org>
To: Mladen Meduric <mladen_meduric@yahoo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: patching iptables - how?
Date: Thu, 9 Jan 2003 01:24:20 +0000 [thread overview]
Message-ID: <20030109012420.GG21359@miggy.org> (raw)
In-Reply-To: <20030108221616.1503.qmail@web12706.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Wed, Jan 08, 2003 at 10:16:16PM +0000, Mladen Meduric wrote:
> Pretty new to linux/iptables (on SuSE8.0). I'm trying to patch from 1.2.5
> to 1.2.6a and then to 1.2.7a.
It would probably be easier to just grab the tar ball of 1.2.7a:
http://www.netfilter.org/downloads.html#1.2.7a
> Do have all patches. Tried "patch" command, but I seem can't figure it out
> properly. Would someone explain how to do this in couple of steps, please?
> Also, from reading other articles, after patching up or reinstalling
> iptables from scratch, is it necessary to recompile the kernel?
Depends what features you're trying to make use of. What's your
current kernel version (uname -r) ?
The only thing I've personally found not working on 2.4.20 is ECN
mangle'ing for which you need this patch to the kernel:
http://www.netfilter.org/documentation/pomlist/pom-pending.html#05_ECN-tcpchecksum-littleendian-fix
HTH,
-Ath
-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-01-09 1:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 22:16 patching iptables - how? Mladen Meduric
2003-01-09 1:24 ` Athan [this message]
2003-01-09 2:11 ` Vincent Lim
2003-01-09 2:34 ` Fabrice MARIE
2003-01-09 3:42 ` Mladen Meduric
2003-01-09 16:22 ` Arnt Karlsen
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=20030109012420.GG21359@miggy.org \
--to=netfilter@miggy.org \
--cc=mladen_meduric@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.