From: "Alexander W. Janssen" <alexander.janssen@gmx.de>
To: Netfilter Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: netfilter hangups
Date: Wed, 12 Mar 2003 06:51:38 +0100 [thread overview]
Message-ID: <20030312055138.GB1282@ynfonatic.de> (raw)
In-Reply-To: <3019863CF306D211BA4500A0CC30812DC6790D@exchange.cyberwolf.com>
[-- Attachment #1: Type: text/plain, Size: 2072 bytes --]
On Tue, Mar 11, 2003 at 03:00:20PM -0700, Chip Upsal wrote:
> [root@iptables1 root]# /etc/sysconfig/iptables condrestart
> iptables: Chain already exists
> iptables: Chain already exists
> iptables: Chain already exists
> iptables: Chain already exists
> iptables: Chain already exists
The error is, what is says. If you create a custom chain with the -N switch
and fill it with data, the following can happen:
castor:~# iptables -N bla # New chain
castor:~# iptables -A bla -j REJECT # some rule
castor:~# iptables -X bla # try to delete
iptables: Chain is not empty # doesn't work. surprise
castor:~# iptables -N bla # that seems to be your problem
iptables: Chain already exists # oh, well...
castor:~# iptables -F bla # flush the chain
castor:~# iptables -X bla # delete it
castor:~# iptables -N bla # be a lucky boy
castor:~# echo $?
0 # yeah, baby
> Or if i get no error the firewall will not recognize any of the changes i
> have made.
What i gues what happens is that:
1. Create chain
2. Fill chain
3.1. Try to delete chain without flushing it first -> will fail
3.2. Forget to delete chain
4. Try to create chain -> chain allready exists
5. Fill chain with rules -> since the chain was never flushed, it just keeps
up filling with rules
> In either case i am forced to reboot the firewall to get things going again.
Na, i don't think so. Look into your script into the "stop" section (i don't
really know that script, but SYSV-init-style scripts should be the same
everywhere). Look if you custom created chains are getting flushed and
deleted. If they arent't do it there. Save. Try.
If it doesn't work: Send the script.
> Chip Upsal
> SysAdmin
Alex.
--
"Mr Data, when I said 'Fire at Will', I didn't mean for you to be so literal."
Instructions for use of this post: Insert tounge in cheek. Read as normal.
[-- Attachment #2: Type: application/pgp-signature, Size: 248 bytes --]
next prev parent reply other threads:[~2003-03-12 5:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 22:00 netfilter hangups Chip Upsal
2003-03-11 22:15 ` ...
2003-03-12 5:51 ` Alexander W. Janssen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-11 23:27 Chip Upsal
2003-03-12 8:12 ` Rob Sterenborg
2003-03-17 16:10 Chip Upsal
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=20030312055138.GB1282@ynfonatic.de \
--to=alexander.janssen@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox