* iptables-retore very slow
@ 2007-03-05 18:10 Rackage | Randles
2007-03-06 20:32 ` Daniel De Graaf
2007-04-10 17:45 ` Pablo Neira Ayuso
0 siblings, 2 replies; 3+ messages in thread
From: Rackage | Randles @ 2007-03-05 18:10 UTC (permalink / raw)
To: netfilter
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: iptables-retore very slow
2007-03-05 18:10 iptables-retore very slow Rackage | Randles
@ 2007-03-06 20:32 ` Daniel De Graaf
2007-04-10 17:45 ` Pablo Neira Ayuso
1 sibling, 0 replies; 3+ messages in thread
From: Daniel De Graaf @ 2007-03-06 20:32 UTC (permalink / raw)
To: netfilter
iptables-restore has some flags that could be useful: --verbose,
--test (to prevent the actual sending back to the kernel), --noflush
(to prevent flushing already existing chains)
If that doesn't help at all, you could either use strace to find if it
is hanging on a syscall, or add #define DEBUG to the top of
iptables-restore.c and recompile to enable more debugging output.
Are there rules on tables other than filter? Those aren't flushed by
iptables -F and could possibly be slowing it down if there were many
of them.
Hope that helps,
Daniel De Graaf
On 3/5/07, Rackage | Randles <randles@rackage.com> wrote:
> 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
>
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: iptables-retore very slow
2007-03-05 18:10 iptables-retore very slow Rackage | Randles
2007-03-06 20:32 ` Daniel De Graaf
@ 2007-04-10 17:45 ` Pablo Neira Ayuso
1 sibling, 0 replies; 3+ messages in thread
From: Pablo Neira Ayuso @ 2007-04-10 17:45 UTC (permalink / raw)
To: randles; +Cc: netfilter
Rackage | Randles wrote:
> 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.
Are you using iptables >= 1.3.x?
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-04-10 17:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-05 18:10 iptables-retore very slow Rackage | Randles
2007-03-06 20:32 ` Daniel De Graaf
2007-04-10 17:45 ` Pablo Neira Ayuso
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.