From: Chip Upsal <cupsal@cyberwolf.com>
To: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: netfilter hangups
Date: Tue, 11 Mar 2003 15:00:20 -0700 [thread overview]
Message-ID: <3019863CF306D211BA4500A0CC30812DC6790D@exchange.cyberwolf.com> (raw)
I am running nefilter 1.2.7a on a Redhat 7.3 box kernel v. 2.4.18-24.7.x.
I have experienced the following problems. Sometimes after making many
changes and reloading the firewall after each change...the firewall will
refuse to reload with the following output:
[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
Or if i get no error the firewall will not recognize any of the changes i
have made.
In either case i am forced to reboot the firewall to get things going again.
Chip Upsal
SysAdmin
next reply other threads:[~2003-03-11 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 22:00 Chip Upsal [this message]
2003-03-11 22:15 ` netfilter hangups ...
2003-03-12 5:51 ` Alexander W. Janssen
-- 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=3019863CF306D211BA4500A0CC30812DC6790D@exchange.cyberwolf.com \
--to=cupsal@cyberwolf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox