Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Herman <Herman@AerospaceSoftware.com>
To: Arnt Karlsen <arnt@c2i.net>, netfilter@lists.netfilter.org
Subject: Re: Port forwarding doesn't work.
Date: Mon, 13 Oct 2003 12:05:55 -0600	[thread overview]
Message-ID: <200310131205.55401.Herman@AerospaceSoftware.com> (raw)
In-Reply-To: <20031013031712.7fd7be69.arnt@c2i.net>

On Sunday 12 October 2003 7:17 pm, Arnt Karlsen wrote:
   On Sun, 12 Oct 2003 18:40:27 -0600,
   Herman <Herman@AerospaceSoftware.com> wrote in message

   <200310121840.27031.Herman@AerospaceSoftware.com>:
   > The real problem that I'm trying to solve is this:
   > Several hosts need to acces a gov service that uses Java and a certain
   > port.

   ..if these hosts are initiating this connection from your end,
   " -j ESTABLISHED,RELATED" should do it, instead of you
   running around chasing your tail.

Hi Arnt,

Could you please elaborate on that?

As far as I can see, the hosts are initiating the connection, but the port 
must somehow be forwarded through the firewall snat box.

This is what I have:
echo "   DNAT Forward port 3270 for Alberta Registries application on Pluto"
$IPTABLES -A FORWARD -i $EXTIF -o $INTIF -p tcp --dport 3270 -j ACCEPT
$IPTABLES -t nat -A PREROUTING -i $EXTIF -p tcp --dport 3270 -j DNAT --to 
192.168.10.1:3270

This is working now, provided that I use that specific IP address on the 
inside - I had to load the iptable_mangle module, which made my problems go 
away...

I don't understand how to add the ESTABLISHED,RELATED idea into this type of 
rule.  

Something like this:

$IPTABLES -t nat -A PREROUTING -i $EXTIF -p tcp --dport 3270 -m state --state 
ESTABLISHED,RELATED

???


Cheers,
-- 
Herman Oosthuysen 
B.Eng(E), MIEEE
Aerospace Software Ltd.
Ph: 1.403.241-8773, Cell: 1.403.852-5545, Fx: 1.403.241-8841
Herman@AerospaceSoftware.com, http://www.AerospaceSoftware.com


  parent reply	other threads:[~2003-10-13 18:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-12  7:41 Invalid friggen argument Herman
2003-10-12 11:08 ` Willy TARREAU
2003-10-12 15:46   ` Herman
2003-10-12 17:44 ` Mark E. Donaldson
2003-10-12 18:18   ` Herman
2003-10-12 20:11     ` Port forwarding doesn't work Herman
2003-10-12 21:41       ` Gerd Zemella
2003-10-12 22:04         ` Herman
2003-10-12 23:00           ` Herman
2003-10-13  0:10             ` Philip Craig
2003-10-13  0:20               ` Herman
2003-10-13  0:40                 ` Herman
2003-10-13  1:17                   ` Arnt Karlsen
2003-10-13 13:06                     ` Robert P. J. Day
2003-10-13 19:11                       ` Arnt Karlsen
2003-10-13 18:05                     ` Herman [this message]
2003-10-13 19:31                       ` Jeffrey Laramie
2003-10-13 20:00                       ` Jeffrey Laramie
2003-10-13 20:09                       ` Arnt Karlsen
2003-10-13 20:47                         ` Herman
2003-10-13  0:44             ` Chris Brenton
2003-10-13  1:17               ` Herman
2003-10-13  1:30                 ` Herman
2003-10-13  1:52                   ` Port forwarding now *almost* works Herman
2003-10-13  7:13           ` Port forwarding doesn't work Gerd Zemella
2003-10-13 14:32             ` Adam D. Barratt
2003-10-13 15:02               ` Gerd Zemella
2003-10-14  6:04 ` Invalid friggen argument Joel Newkirk
2003-10-14 13:14   ` Herman

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=200310131205.55401.Herman@AerospaceSoftware.com \
    --to=herman@aerospacesoftware.com \
    --cc=arnt@c2i.net \
    --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