From: "Jason Pyeron" <jpyeron@pdinc.us>
To: netfilter@vger.kernel.org
Subject: RE: Parts of firewall disappearing under load
Date: Tue, 2 Jun 2009 14:12:33 -0400 [thread overview]
Message-ID: <A67DFD641F7847289C151D78D48E99BF@phoenix> (raw)
In-Reply-To: <1243957429.10053.7.camel@enterprise.ims-firmen.de>
FYI, please don't cc me use the list.
> -----Original Message-----
> From: netfilter-owner@vger.kernel.org
> [mailto:netfilter-owner@vger.kernel.org] On Behalf Of Thomas Jacob
> Sent: Tuesday, June 02, 2009 11:44
> To: Chris
> Cc: netfilter@vger.kernel.org; Jason Pyeron
> Subject: Re: Parts of firewall disappearing under load
>
> On Tue, 2009-06-02 at 11:31 -0400, Chris wrote:
> > On Tue, Jun 02, 2009 at 10:10:31AM -0400, Jason Pyeron wrote:
> > > > We've got quite a few heavily loaded boxes (ISP shared
> > > > servers) which have firewalls enabled. The firewalls basically
> > > > allow certain ports, block some naughty IPs, and use limit and
> > > > recent to keep some services under control.
> > > >
> > > > What we've noticed is that on rare occasions, a box will
> > >
> > > Can you make a test case? Does it happen on more than one machine?
> >
> > That's the tricky part. It happens maybe once or twice a
> month, and
> > on different machines. I don't know of a way to reproduce it. Any
> > pointers on information that would be useful to gather at
> the time it
> > happens would be extremely useful, since at this point it
> is a mystery
> > to me.
>
> If you can actually see that you have a different active
> rulesets when it "works" than when it doesn't work, then your
> problem most likely is with the ruleset loading/creation
> process. I am not aware of any component of netfilter that
> can change the ruleset by itself without user space
> interaction. Of course various dynamic memory tables can get
> exhausted (connection tracking, neighbor caches, routing
> cache etc), but when this happens you usually get messages in
> your kernel log that clearly say so.
>
> How do you manage your ruleset? Check the logs of that solution....
>
If each machine is rhel/centos it would be managed by the
/etc/sysconfig/iptables file.
Now there are several utilities which may modify it, but all are user run.
/etc/init.d/iptables is how the file is loaded in to memory.
> Thomas
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> netfilter" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
>
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
next prev parent reply other threads:[~2009-06-02 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 13:52 Parts of firewall disappearing under load Chris
2009-06-02 14:10 ` Jason Pyeron
2009-06-02 15:31 ` Chris
2009-06-02 15:43 ` Thomas Jacob
2009-06-02 18:12 ` Jason Pyeron [this message]
2009-06-02 19:39 ` Chris
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=A67DFD641F7847289C151D78D48E99BF@phoenix \
--to=jpyeron@pdinc.us \
--cc=netfilter@vger.kernel.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