From: uniplex <uniplex@maximum-linux.net>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: -m recent
Date: Fri, 24 Jan 2003 02:03:38 +0000 [thread overview]
Message-ID: <3E309EFA.4060605@maximum-linux.net> (raw)
In-Reply-To: 20030123224028.GM484@ns.snowman.net
Stephen Frost wrote:
> It'd be before the -j DROP to see if that fixes it. Recent versions of
> ipt_recent will print out to your kernel log (which you can usually see
> via dmesg) what version of ipt_recent it is. If you're not seeing that
> then you probably want to try and get a later version. The latest
> 'released' version is on my website,
> http://snowman.net/projects/ipt_recent/ . There have been a number of
> bug fixes, however, and so if you want to try my current 'beta' you can
> download it from:
> http://snowman.net/projects/ipt_recent/ipt_recent-0.2.6.tar.gz .
> I've had alot of good responses to the beta so I'm planning on
> releasing it when I have some time to do the 'paperwork'. My son was
> born a week ago and I'm still pretty busy with him tho. :)
>
> Stephen
Congrats! :)
I found this in dmesg
ipt_recent v0.2.3: Stephen Frost <sfrost@snowman.net>.
http://snowman.net/projects/ipt_recent/
Do you know where I can find a guide or howto for installing your patch?
I'm not to swoft with those types of things, I've used patch and diff
only one time that I can remember.
Thanks.
next prev parent reply other threads:[~2003-01-24 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 13:11 -m recent uniplex
2003-01-23 19:15 ` Stephen Frost
2003-01-23 15:59 ` uniplex
2003-01-23 22:40 ` Stephen Frost
2003-01-24 2:03 ` uniplex [this message]
2003-01-24 8:15 ` Fabrice MARIE
2003-01-25 1:29 ` Stephen Frost
2003-01-30 19:50 ` uniplex
2003-02-24 13:59 ` Stephen Frost
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=3E309EFA.4060605@maximum-linux.net \
--to=uniplex@maximum-linux.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 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.