From: Mr Ritter <netfilter@candlefire.org>
To: Dimitri Yioulos <dyioulos@firstbhph.com>, netfilter@lists.netfilter.org
Subject: Re: Port forwarding question
Date: Thu, 21 Sep 2006 14:25:04 -0600 [thread overview]
Message-ID: <4512F520.6010104@candlefire.org> (raw)
In-Reply-To: <200609211555.39634.dyioulos@firstbhph.com>
Greetings,
Dimitri Yioulos wrote:
> Noob, question:
>
> I want to allow a vendor to access a piece of equipment on our LAN
> (192.168.100.46) through port 4000 from outside via a server in our
> DMZ (www.xxx.yyy.zzz). While I should know how to do this, I'm not
> 100% sure. Can someone help?
DNAT.
for example:
iptables -t nat -A PREROUTING -d www.xxx.yyy.zzz -i eth1 -p tcp --dport
4000 -j
DNAT --to 192.168.100.46
iptables -t filter -A INETIN -d 192.168.100.46 -p tcp --dport 4000 -j ACCEPT
> Oh, and separately, how would I allow that access only through the
> vendor's ip address, if that were the way I decided to go?
for example:
iptables -t nat -A PREROUTING -s 1.2.3.4 -d www.xxx.yyy.zzz -i eth1 -p
tcp --dport 4000 -j DNAT --to 192.168.100.46
Regards,
--
Ritter
next prev parent reply other threads:[~2006-09-21 20:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 19:55 Port forwarding question Dimitri Yioulos
2006-09-21 20:23 ` Martijn Lievaart
2006-09-21 20:25 ` Mr Ritter [this message]
2006-09-21 20:32 ` Mr. Ritter
2006-09-21 20:53 ` Dimitri Yioulos
2006-09-21 21:14 ` Martijn Lievaart
2006-09-21 21:23 ` Dimitri Yioulos
-- strict thread matches above, loose matches on Subject: below --
2007-04-30 17:37 David
2007-05-02 12:00 ` Elvir Kuric
2008-03-17 16:26 port " Phil Sutter
2008-03-17 18:13 ` Jan Engelhardt
2008-03-17 18:32 ` Cloves Pereira Costa Jr
2008-03-17 20:01 ` Andrew Schulman
2008-03-18 16:36 ` Jan Engelhardt
2009-05-06 18:25 Port Forwarding Question Aaron Clausen
2009-05-08 15:57 ` Michele Petrazzo - Unipex
[not found] ` <8ec0428d0905171444q4e8a75dj6e60bfbab93bc75d@mail.gmail.com>
2009-05-17 21:54 ` Aaron Clausen
2009-05-18 7:03 ` Покотиленко Костик
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=4512F520.6010104@candlefire.org \
--to=netfilter@candlefire.org \
--cc=dyioulos@firstbhph.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