Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Joel Newkirk <netfilter@newkirk.us>
To: Patrick Kwan <pat@pat.dyndns.info>
Cc: netfilter@lists.netfilter.org
Subject: Re: netmeeting (incoming and outgoing connection)
Date: 28 Apr 2003 03:08:04 -0400	[thread overview]
Message-ID: <1051513684.2388.138.camel@alpha.newkirk.us> (raw)
In-Reply-To: <33659.172.16.28.1.1051508134.squirrel@pat.dyndns.info>

On Mon, 2003-04-28 at 01:35, Patrick Kwan wrote:
> Hello,
> 
> I'm using iptables NAT to allow lan client to access internet.
> if i patch my kernel with netfilter's POM and load the required
> H323 modules.
> 
> I want to confirm if h323 modules also allow "Incoming connection"
> to Netmeeting in internal lan client?

If you're talking about a new connection being initiated, then it's the
same as with any other NAT situation - you have to explicitly DNAT new
incoming connections to a local IP if you want them to reach a
particular target.  Otherwise they will end up in the INPUT chain,
destined for the firewall/nat box itself.  As long as you only need
incoming NEW state connections to reach a single client, just add a DNAT
rule to nat PREROUTING to handle them. If you need multiple internal
clients to be able to receive NEW connections from outside the network,
you have a problem.  (however, you would anyway, regardless of
firewall/NAT solution - this is a limit imposed by the nature of NAT
itself, not netfilter)

> Please clarify me. (already search the past thread)
> Many thanks your advices.
>
> Patrick

j




  reply	other threads:[~2003-04-28  7:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-28  5:35 netmeeting (incoming and outgoing connection) Patrick Kwan
2003-04-28  7:08 ` Joel Newkirk [this message]
2003-04-28  8:17   ` Patrick Kwan
2003-04-28  7:42 ` Alex Nee

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=1051513684.2388.138.camel@alpha.newkirk.us \
    --to=netfilter@newkirk.us \
    --cc=netfilter@lists.netfilter.org \
    --cc=pat@pat.dyndns.info \
    /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