Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: uniplex <uniplex@maximum-linux.net>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: -m recent
Date: Fri, 24 Jan 2003 20:29:40 -0500	[thread overview]
Message-ID: <20030125012940.GN484@ns.snowman.net> (raw)
In-Reply-To: <3E309EFA.4060605@maximum-linux.net>

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

* uniplex (uniplex@maximum-linux.net) wrote:
> Congrats! :)

Thanks. :)

> I found this in dmesg
> 
> ipt_recent v0.2.3: Stephen Frost <sfrost@snowman.net>. 
> http://snowman.net/projects/ipt_recent/

Ok, yeah, that's a kind of old one.  I think you should try 0.2.6,
honestly.

> 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.

If you want to install using one of the tarballs I've created it's
pretty simple.  Patch your kernel using the patch-o-matic as normal.
Then uncompress/untar the tarball you downloaded and copy the
ipt_recent.h and ipt_recent.c from the tarball over the ones that now
exist in your Linux kernel tree (from the patch-o-matic).  You can also
overwrite the libipt_recent.c that is in the extensions directory with
the one from the tarball.  Then compile iptables and your kernel as you
normally would.

	Stephen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-01-25  1:29 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
2003-01-24  8:15         ` Fabrice MARIE
2003-01-25  1:29         ` Stephen Frost [this message]
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=20030125012940.GN484@ns.snowman.net \
    --to=sfrost@snowman.net \
    --cc=netfilter@lists.netfilter.org \
    --cc=uniplex@maximum-linux.net \
    /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