From: David T-G <davidtg-netfilter@justpickone.org>
To: NetFilter Users' List <netfilter@lists.netfilter.org>
Cc: Ray Leach <raymondl@knowledgefactory.co.za>
Subject: Re: where is libipt_match.so?
Date: Thu, 29 May 2003 06:47:13 -0400 [thread overview]
Message-ID: <20030529104713.GL33081@justpickone.org> (raw)
In-Reply-To: <1054186276.13296.186.camel@raylinux.internal>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
Ray, et al --
...and then Ray Leach said...
%
% On Thu, 2003-05-29 at 05:56, David T-G wrote:
...
% > What is it? From where does (er, should) it come?
% >
% It's a netfilter module, and it comes from the iptables distribution
The module part I had guessed, but I couldn't find it.
% (also in the 2.4 kernel distro). You get it by compiling and installing
% the iptables distro, or selecting match support in the netfilter kernel
% config section and compiling the kernel.
Ahhh... So it *was* there before, and I *didn't* botch the typing as I
was tweaking the script! Very interesting.
1) I originally tried doing the firewall config for this machine via
SuSEfirewall2 before giving up and going directly to iptables. After
getting things tested, we rebuilt the server from scratch to ensure that
my installation script would work -- and got to this problem. Would fw2
have added the match module and possible kernel tweaks, or did my client
install a different kernel when he rebuilt this time?
2) What, if anything is the difference between
iptables -t filter -A INPUT -i EXTT -m match NEW,RELATED,ESTABLISHED -j ACCEPT
(the original, which throws the error) and
iptables -t filter -A INPUT -i EXTT -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT
(the current, which seems to work)?
TIA & HAND
:-D
--
David T-G * There is too much animal courage in
(play) davidtg@justpickone.org * society and not sufficient moral courage.
(work) davidtgwork@justpickone.org -- Mary Baker Eddy, "Science and Health"
http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2003-05-29 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 3:43 where is libipt_match.so? David T-G
2003-05-29 3:54 ` George Vieira
2003-05-29 3:56 ` David T-G
2003-05-29 5:31 ` Ray Leach
2003-05-29 10:47 ` David T-G [this message]
2003-05-29 11:58 ` ip_queue, userspace module, ipq_packet_msg_t field 'hook'. Any purpose? Scott MacKay
2003-05-29 6:59 ` where is libipt_match.so? Michael K
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=20030529104713.GL33081@justpickone.org \
--to=davidtg-netfilter@justpickone.org \
--cc=netfilter@lists.netfilter.org \
--cc=raymondl@knowledgefactory.co.za \
/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.