Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Paul Cousins" <paul@pimper.fsnet.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: [iptables] Help Required
Date: Wed, 30 Jul 2003 15:29:17 +0100	[thread overview]
Message-ID: <000901c356a6$f990eb90$0300a8c0@frodo> (raw)
In-Reply-To: 20030730093120.M51327@vfmindia.biz

iptables -t -A PREROUTING -i eth1 -p TCP --dport 1494 -j DNAT --to
192.168.0.1:1494
iptables -A FORWARD -i eth1 -o eth0 -p TCP -d 192.168.0.1 --dport 22 -j
ACCEPT

of course your -i and -o interfaces may have different names. -i being the
external and -o being the internal in this scenario. an dof course the
address will be different but you should get the idea.
------------------------------------------------
Paul Cousins
Canterbury Computer Services
paul@canterburycomputerservices.co.uk


----- Original Message ----- 
From: "Sridhar Murthy" <sridhar@vfmindia.biz>
To: <netfilter@lists.netfilter.org>
Sent: Wednesday, July 30, 2003 10:40 AM
Subject: [iptables] Help Required


>
>
> Hi Team,
>
> I require help to my following setup:
>
> I have a Redhat 8 Server with squid,smtp & pop3 with iptables running.
>
> My requirement is we have a citrix server with local LAN ipaddress. People
> from Internet will have to access this server from outside(my firewall is
> having a public ipaddress which is dynamic assigned). I want to know what
is
> the rules that i have to add to allow the traffic which uses port number
> 1494, to get into my network and access my citrix server which is having
LAN
> ip. Should any nat be added.
>
> Thanks in advance.
>
> Regards,
>
> Sridhar
>
>
>




  reply	other threads:[~2003-07-30 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  9:40 Help Required Sridhar Murthy
2003-07-30 14:29 ` Paul Cousins [this message]
2003-07-30 15:28   ` [iptables] " Paul Cousins
2003-07-31  0:34 ` Carlo Florendo

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='000901c356a6$f990eb90$0300a8c0@frodo' \
    --to=paul@pimper.fsnet.co.uk \
    --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