From: Ted Kaczmarek <tedkaz@optonline.net>
To: netfilter@lists.netfilter.org
Subject: New rules set would not work until rules where summarized
Date: Sat, 20 Dec 2003 09:45:25 -0500 [thread overview]
Message-ID: <1071931525.32295.18.camel@tarkus> (raw)
Redhat 9
2.4.20-24.9.i686
iptables-1.2.7a-2
I have one setup where I log based upon clients SA's. Each client has
their own prefix they log to.
The rules were very anal in that SA/DA port for each flow was defined. I
tried to add another pair of SA/DA's port rules
and they refused to work. I tried downgrading to 2.4.20-20.9
no joy. In desperation I redid the rules to limit the amount
of individual rules to SA subnet/DA port , applied the ruleset again
summarized that would not work and it is now working.
So now instead of having 40 lines of rules, 20 logging and 20 accept, I
now have have 16, 8 logging and 8 accept and it is behaving.
How could I identify what was the root of the problem?
I would like to recreate the problem and gather more data, but any
insight into what I should be looking fow would be appreciated.
Is their some allocation somehwere in the kernel that is possibly too
small?
Or did I hit some obscure bug?
Thanks and Happy Holidays,
Ted
reply other threads:[~2003-12-20 14:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1071931525.32295.18.camel@tarkus \
--to=tedkaz@optonline.net \
--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