From: Alistair Tonner <Alistair@nerdnet.ca>
To: Kevin Smith <kevin@perfht.com>,
Netfilter List <netfilter@lists.netfilter.org>
Subject: Re: Noob Question
Date: Fri, 31 Oct 2003 22:26:43 -0500 [thread overview]
Message-ID: <200310312226.43276.Alistair@nerdnet.ca> (raw)
In-Reply-To: <NGBBLGFEALDADHNDAAFFGEPJDMAA.kevin@perfht.com>
On October 31, 2003 12:03 pm, Kevin Smith wrote:
> Ok thanks, I think I had to but wasn't 100%. Now I can eliminate that is a
> possibility (Iptables 1.2.8).
> I finished it late last night so I wasn't in the mood for Googling
> anything. but tonight I shall. But I would turn away any tips. ;-)
> Thanks
>
>
> --__--__--
>
> Message: 5
> Subject: Re: Noob Question
> From: Ray Leach <raymondl@knowledgefactory.co.za>
> To: Netfilter Mailing List <netfilter@lists.netfilter.org>
> Organization: Knowledge Factory
> Date: Fri, 31 Oct 2003 16:25:39 +0200
>
>
> --=-p9AU5830cWaY0P2ToPWv
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
>
> On Fri, 2003-10-31 at 16:13, Kevin Smith wrote:
> > Does IPtables need to be recompiled every time you roll a new kernel?
> > I just compiled 2.4.22 and when my firewall (Shorewall) started, it
> > spit some "device busy" errors with ip_tables.o.=20
> > Kev
>
That error usually is generated when one has both iptables and ipchains in
the tree.
if ipchains loads ... iptables *coughs* and exits stage left.
> No. The kernel source includes (at least as far as I recall) the
> iptables kernel space drivers/programs/libraries.
>
> The userspace tools (the iptables executables used to manage rules) are
> separate, and do not get recompiled every time you recompile the kernel.
>
> The exception would be if you have iptables v0.1.0 (for example)
> userspace programs and in your kernel have iptables v1.2.8 source code,
> then there would be a mismatch, and the userspace programs may be
> incompatible with the kernel modules.
>
> Best to keep them all the same.
> --=20
> --
> Raymond Leach <raymondl@knowledgefactory.co.za>
> Network Support Specialist
> http://www.knowledgefactory.co.za
> "lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
> Key fingerprint =3D 7209 A695 9EE0 E971 A9AD 00EE 8757 EE47 F06F FB28
> --
--
Alistair Tonner
nerdnet.ca
Senior Systems Analyst - RSS
Any sufficiently advanced technology will have the appearance of magic.
Lets get magical!
next prev parent reply other threads:[~2003-11-01 3:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 17:03 Noob Question Kevin Smith
2003-11-01 3:26 ` Alistair Tonner [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-06 22:11 noob question Fitzgerald, Dan
2014-01-06 22:43 ` Chris Murphy
2014-01-07 1:58 ` Stan Hoeppner
2014-01-07 15:22 ` Fitzgerald, Dan
2012-12-21 1:07 Noob Question awingnut
2012-12-21 1:43 ` Andrew Ardill
2012-12-21 13:27 ` W T Riker
2012-12-21 22:38 ` Andrew Ardill
2011-01-13 23:58 noob question Harry Johnson
2011-01-14 11:10 ` Thomas Rast
2011-01-14 21:32 ` Harry Johnson
2003-10-31 14:13 Noob Question Kevin Smith
2003-10-31 14:25 ` Ray Leach
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=200310312226.43276.Alistair@nerdnet.ca \
--to=alistair@nerdnet.ca \
--cc=kevin@perfht.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.