All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Earnshaw <tonni@billy.demon.nl>
To: netfilter@lists.samba.org
Cc: James Sneeringer <james+netfilter@vincentsystems.com>,
	"Philippe Dhont  (Sea-ro)" <Philippe.Dhont@searo.be>
Subject: Re: Error when using iptables 1.2.6a (or another version)
Date: 05 Jun 2002 08:25:50 +0200	[thread overview]
Message-ID: <1023258350.2834.8.camel@billy.demon.nl> (raw)
In-Reply-To: <20020604212807.GA30300@valjean.si.ocslink.com>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

tir, 2002-06-04 kl. 23:28 skrev James Sneeringer:

> There is a compile-time option to modutils (modprobe, insmod, et al) that
> permits gzipped kernel modules.

> I know Slackware 7.1 and 8.0 enable this feature.

Ah. Well then, Philippe's possibly suffering from the well-known
ipchains syndrome. lsmod would show this.

The solution is remove the ipchains modules (if they're not compiled
into a monolithic kernel) and substitute iptables.

Under Red Hat, up to v7.2, anyway, it was standard to start up ipchains
instead of iptables after a fresh install. All the iptables stuff had to
be done by hand, i.e. stopping automatic loading and enabling automatic
loading of iptables.

Tony

-- 

Tony Earnshaw

e-post:		tonni@billy.demon.nl
www:		http://www.billy.demon.nl
gpg public key:	http://www.billy.demon.nl/tonni.armor

Telefoon:	(+31) (0)172 530428
Mobiel:		(+31) (0)6 51153356

GPG Fingerprint = 3924 6BF8 A755 DE1A 4AD6 FA2B F7D7 6051 3BE7 B981
3BE7B981



[-- Attachment #2: Dette er en digitalt signert meldingsdel --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2002-06-05  6:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04  8:42 Error when using iptables 1.2.6a (or another version) Philippe Dhont   (Sea-ro)
2002-06-04 20:41 ` Tony Earnshaw
2002-06-04 21:06   ` Tony Earnshaw
2002-06-04 21:06   ` Tony Earnshaw
2002-06-04 21:28   ` James Sneeringer
2002-06-05  6:25     ` Tony Earnshaw [this message]

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=1023258350.2834.8.camel@billy.demon.nl \
    --to=tonni@billy.demon.nl \
    --cc=Philippe.Dhont@searo.be \
    --cc=james+netfilter@vincentsystems.com \
    --cc=netfilter@lists.samba.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.