From: Pablo Neira <pablo@eurodev.net>
To: Kevin Stadlmayer <kevins@wirelessedge.ca>
Cc: netfilter@lists.netfilter.org
Subject: Re: TIME extension rule not matching under (Fedora) kernel 2.6.9?
Date: Sat, 05 Mar 2005 15:42:05 +0100 [thread overview]
Message-ID: <4229C53D.2060604@eurodev.net> (raw)
In-Reply-To: <200503042355.j24NtSu3027597@mail79.megamailservers.com>
Kevin Stadlmayer wrote:
> I have patched the kernel with the patch-o-matic, and any rules that I add
> show up in the iptables rules listing. However, no packets are matching the
> rules. I can create a rule that is identical to the TIME based rule,
> without the TIME constraint, and the rule matches fine. As soon as I add
> the "-m time" component to the rule, no more matching.
There has been some discussion about TIME in netfilter-devel, have a
look at the mail archive.
https://lists.netfilter.org/pipermail/netfilter-devel/2005-January/018136.html
Those changes are still pending to be applied to pom-ng.
--
Pablo
prev parent reply other threads:[~2005-03-05 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 23:55 TIME extension rule not matching under (Fedora) kernel 2.6.9? Kevin Stadlmayer
2005-03-05 14:42 ` Pablo Neira [this message]
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=4229C53D.2060604@eurodev.net \
--to=pablo@eurodev.net \
--cc=kevins@wirelessedge.ca \
--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