Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Alistair Tonner <Alistair@nerdnet.ca>
To: netfilter@lists.netfilter.org
Subject: Re: Port forwarding or NAT?
Date: Wed, 15 Sep 2004 01:47:50 -0400	[thread overview]
Message-ID: <200409150147.50672.Alistair@nerdnet.ca> (raw)
In-Reply-To: <01ef01c49a5f$51824900$6300a8c0@93egeater>

On September 14, 2004 09:32 am, 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?  I was under the
> impression that our firewall was set up to allow all traffic, initated
> from the LAN, through.  This apparently isn't the case, however.
>
> Eric

	Not knowing what the application that is communicating in this manner is, 
will make suggestions likely off the mark.

	if you are using the proxy server to handle *outgoing* connections using its 
INSIDE ip address, you need to accept packets from the LAN in INPUT chain, 
coming to the proxy.  You will then need to let packets OUT to the internet 
from the proxy to the internet through the OUTPUT chain.  You might well get 
away with appropriate ESTABLISHED RELATED rules to allow tarffic back, but it 
is possible that you will require additional rules to let traffic in from the 
other end.  I would hope that the proxy is smart enouh to handle NATTING the 
packets to the outside IP.

	if the proxy is accepting connections from the internet and proxying them to 
the LAN, you need to accept packets from the other end in via INPUT and allow 
packets to the internal box through OUTPUT,  again, an appropriate 
ESTABLISHED, RELATED rule *should* handle traffic on the return trip.  

	Since it sounds like the proxy and firewall are the same box, the FORWARD 
chain isnt likely to be involved here.  Thus letting all traffic from LAN 
through to internet will not work here.  You have to let the traffic from the 
LAN client INTO the firewall to get to the proxy.

	Alistair Tonner


      parent reply	other threads:[~2004-09-15  5:47 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
2004-09-14 17:18 ` Rob Sterenborg
2004-09-15  5:47 ` Alistair Tonner [this message]

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=200409150147.50672.Alistair@nerdnet.ca \
    --to=alistair@nerdnet.ca \
    --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