From: Andrew Beverley <andy@andybev.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] patching iptables for connlimit
Date: Wed, 26 Jul 2006 15:56:45 +0000 [thread overview]
Message-ID: <44C790BD.1010800@andybev.com> (raw)
In-Reply-To: <20060726161343.097de260@localhost>
> the patch described at
>
> http://www.netfilter.org/documentation/HOWTO//netfilter-extensions-HOWTO-3.html#ss3.5
>
> works for the FORWARD chain as well ?
Yes I've just tried it and it works fine.
If you want to use connlimit and you're using a recent kernel you'll need to take
a look at the netfilter users mailing list for details on how to use connlimit
with it. Take a look at:
http://lists.netfilter.org/pipermail/netfilter/2006-July/066227.html
and also the thread index for the other messages. Unfortunately the thread is
split up into several places in the index.
Andy Beverley
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-07-26 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 13:13 [LARTC] patching iptables for connlimit Petre Bandac
2006-07-26 15:56 ` Andrew Beverley [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=44C790BD.1010800@andybev.com \
--to=andy@andybev.com \
--cc=lartc@vger.kernel.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