From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: NAT rule
Date: Wed, 16 Jul 2008 14:31:31 -0500 [thread overview]
Message-ID: <487E4C93.9080502@riverviewtech.net> (raw)
In-Reply-To: <487E4A67.70400@hoecoop.org>
On 07/16/08 14:22, Michael Crider wrote:
> Thank you, Jan, for taking the time to come up with rules that would do
> exactly what I was asking. Thank you, Grant, for thinking outside the
> box. I implemented your suggestion and it works perfectly.
You are welcome. I'm glad that things are working the way they need to.
And as an added benefit with the second network, you don't have to worry
about keeping them from connecting to other hosts. Of course depending
on what access they have to the target system they can still bounce
elsewhere. :s But with a VPN, they are just about in any way.
Grant. . . .
next prev parent reply other threads:[~2008-07-16 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 19:22 NAT rule Michael Crider
2008-07-16 19:31 ` Grant Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 16:12 Michael Crider
2008-07-16 16:54 ` Jan Engelhardt
2008-07-16 17:19 ` Grant Taylor
2008-07-16 17:25 ` Jan Engelhardt
2008-07-16 18:49 ` Grant Taylor
2008-07-16 17:18 ` Grant Taylor
2008-07-16 17:26 ` Grant Taylor
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=487E4C93.9080502@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