From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Port forwarding or NAT?
Date: Tue, 14 Sep 2004 13:13:56 -0400 [thread overview]
Message-ID: <1095182036.1895.4.camel@wolfpack.ljm.dom> (raw)
In-Reply-To: <01ef01c49a5f$51824900$6300a8c0@93egeater>
On Tue, 2004-09-14 at 09:32, Eric Geater 9/01/04 wrote:
> I have one crazy machine at our home office that must communicate on
> port 6847 to an outside company. This one machine went through our old
> proxy server until it died last week. We're using IPTABLES through
> rc.firewall-2.4 on a Linux proxy, but it doesn't seem to be allowing
> this communication to occur.
>
> Would this be handled through port forwarding or NAT?
it would be handled by the FORWARD chain of the filter table, and by a
SNAT/MASQ rule in the POSTROUTING chain of the nat table.
-j
--
Jason Opperisano <opie@817west.com>
next prev parent reply other threads:[~2004-09-14 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 13:32 Port forwarding or NAT? Eric Geater 9/01/04
2004-09-14 17:13 ` Jason Opperisano [this message]
2004-09-14 17:18 ` Rob Sterenborg
2004-09-15 5:47 ` Alistair Tonner
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=1095182036.1895.4.camel@wolfpack.ljm.dom \
--to=opie@817west.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