From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Port Triggering in IPTables?
Date: Tue, 23 Sep 2008 15:34:49 -0500 [thread overview]
Message-ID: <48D952E9.7070501@riverviewtech.net> (raw)
In-Reply-To: <37a72e270809222156l2c9a9d2ci47bf4101defd5e3d@mail.gmail.com>
On 09/22/08 23:56, Marcin Polewski wrote:
> Does IPTables support port triggering similarly like DD-WRT does? I
> want to build my own Linux (or FreeBSD) box with IPTables that would
> be able to use port triggering. I don't want to use DD-WRT since I
> want full control over my box (hardware and software).
I'm not aware of any thing in IPTables (proper or extensions) persay
that provide port knocking support. However I would think it trivial to
have something watch log entries and / or ulog entries and alter
something. You will need to think out side of the box, but I see no
reason that you can't solve this and get it to work.
Grant. . . .
prev parent reply other threads:[~2008-09-23 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 4:56 Port Triggering in IPTables? Marcin Polewski
2008-09-23 20:34 ` Grant Taylor [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=48D952E9.7070501@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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