Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Rackage | Randles <randles@rackage.com>
To: netfilter@lists.netfilter.org
Subject: iptables-retore very slow
Date: Mon, 05 Mar 2007 18:10:07 +0000	[thread overview]
Message-ID: <45EC5CFF.5000209@rackage.com> (raw)

Hi,

I recently noticed that one of my firewalls was taking a very long time 
to reboot. Which was odd as its a very new  machine.

On investigation is seemed to be the iptables-restore command that was 
adding 10+ minutes to the boot-up times.

I ran iptables-restore from a terminal and found that it was indeed 
taking an amazingly long time.

Obviously I assumed it was related to the rules on the server, so I 
flushed all rules and all user defined tables from the firewall (nat, 
mangle and filter) and used iptables-save which took less than 1 
millisecond :) on the empty rule set.

However iptables-restore is still taking 10+ minutes even with no rules 
to read / apply.

Has anyone seen the behaviour before?  or has anybody got some bright 
ideas on how I might continue debugging this issue?

Thanks in Advance

Regards

Ben



             reply	other threads:[~2007-03-05 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 18:10 Rackage | Randles [this message]
2007-03-06 20:32 ` iptables-retore very slow Daniel De Graaf
2007-04-10 17:45 ` Pablo Neira Ayuso

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=45EC5CFF.5000209@rackage.com \
    --to=randles@rackage.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