From: Grant Taylor <gtaylor@riverviewtech.net>
To: Jared Cook <jared@vsahost.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Using NAT to relay traffic
Date: Thu, 24 Mar 2005 10:03:18 -0600 [thread overview]
Message-ID: <4242E4C6.6050305@riverviewtech.net> (raw)
In-Reply-To: <4242CE01.5090105@vsahost.com>
You are welcome. I'm glad that I could help. :)
I do ask a favor, have a good day for me as I was up WAY too late working on things. Now where did I put my sleeping bag at work???
Grant. . . .
Jared Cook wrote:
> Thanks. The SNAT piece indeed was the part I was missing. It all works
> great now.
prev parent reply other threads:[~2005-03-24 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 23:57 Using NAT to relay traffic Jared Cook
2005-03-24 0:37 ` Grant Taylor
2005-03-24 8:44 ` Sietse van Zanen
2005-03-24 14:29 ` Jared Cook
2005-03-24 14:26 ` Jared Cook
2005-03-24 16:03 ` 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=4242E4C6.6050305@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=jared@vsahost.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox