From: Harald Welte <laforge@netfilter.org>
To: Sumit Pandya <sumit@elitecore.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Delition of rule after altering data in check/match entry
Date: Tue, 15 Jul 2003 14:28:46 +0200 [thread overview]
Message-ID: <20030715122846.GH7198@naboo> (raw)
In-Reply-To: <02b201c34a1c$faef6ac0$010f430a@elitecore7>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Mon, Jul 14, 2003 at 09:01:22PM +0530, Sumit Pandya wrote:
> Hi All,
> In a netfilter match or check extension at the time of rule-insertion,
> If I update any data passed along
> 1> void *matchinfo (argument to matchentry) or
> 2> void *targinfo (argument to checkentry)
> Then I'm not able to delete same inserted rule.
> Is there something regarding caching of the data? Does It require to
> notify iptables somewhere about this change?
Just at first glance, I think this is quite possible (and certainly not
the desired behaviour). Can you please verify that this bug is also
present with already-existing matches/targets that change
targinfo/matchinfo contents (like the nth or random match)?
If so, please commit this as a bug report to bugzilla.netfilter.org.
> Thanks,
> -- Sumit
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-15 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 15:31 Delition of rule after altering data in check/match entry Sumit Pandya
2003-07-15 12:28 ` Harald Welte [this message]
2003-07-16 8:27 ` Sumit Pandya
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=20030715122846.GH7198@naboo \
--to=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sumit@elitecore.com \
/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 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.