From: Daniel Chemko <dchemko@smgtec.com>
To: Paul Fontenot <wpfontenot@cox.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: nat
Date: Tue, 25 Nov 2003 22:33:03 -0800 [thread overview]
Message-ID: <3FC4491F.1020002@smgtec.com> (raw)
In-Reply-To: <GGEFKDNEPJHKAMAGGLFLGEDLCBAA.wpfontenot@cox.net>
iptables -t nat -A PREROUTING -i <your inet iface> --destination 1.1.1.1
-p tcp --dport 3306 -j DNAT --to 192.168.1.1
If you have sane filtering rules (same as IOS access-list), you will
also have to open up the FORWARD chain for inbound traffic:
iptables -A FORWARD -i <your inet iface> --destination 192.168.1.1 -p
tcp --dport 3306 -j ACCEPT
reading the iptables man pages fills in most of the important stuff, and
if that isn't enough, you could always read the documentation on
netfilter.org for more info than you'll need.
Paul Fontenot wrote:
>Not sure what the ipfilter lingo is for what i want to do so I will
>demonstrate with a Cisco PIX ACL.
>
>access-list outside_access_in permit tcp any host 1.1.1.1 eq 3306
>
>There would be a static for the 1.1.1.1 address:
>
>static (inside,outside) 192.168.1.1 1.1.1.1
>
>Where the MySQL server is running on host 192.168.1.1 and that ip is mapped
>via a static translation to 1.1.1.1 on the PIX's outside interface.
>
>
>
>
>
next prev parent reply other threads:[~2003-11-26 6:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 5:31 nat Paul Fontenot
2003-11-26 6:33 ` Daniel Chemko [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-03 6:52 NAT Martin Schiøtz
2007-07-03 7:27 ` NAT Grant Taylor
2007-07-03 7:55 ` NAT Martin Schiøtz
2007-07-03 14:29 ` NAT Robert LeBlanc
2004-06-06 17:36 Nat mafioso1823
2004-06-07 7:38 ` Nat Antony Stone
2003-10-01 11:11 NAT tlussnig
2003-10-03 10:22 ` NAT Harald Welte
2002-09-08 20:43 Nat Mattia Martinello
2002-09-08 21:00 ` Nat Antony Stone
2002-09-08 21:27 ` Nat R. Sterenborg
2002-09-08 21:49 ` Nat Anders Fugmann
2002-06-14 8:29 nat saied tabandeh
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=3FC4491F.1020002@smgtec.com \
--to=dchemko@smgtec.com \
--cc=netfilter@lists.netfilter.org \
--cc=wpfontenot@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.