* netmeeting (incoming and outgoing connection)
@ 2003-04-28 5:35 Patrick Kwan
2003-04-28 7:08 ` Joel Newkirk
2003-04-28 7:42 ` Alex Nee
0 siblings, 2 replies; 4+ messages in thread
From: Patrick Kwan @ 2003-04-28 5:35 UTC (permalink / raw)
To: netfilter
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?
Please clarify me. (already search the past thread)
Many thanks your advices.
Patrick
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: netmeeting (incoming and outgoing connection)
2003-04-28 5:35 netmeeting (incoming and outgoing connection) Patrick Kwan
@ 2003-04-28 7:08 ` Joel Newkirk
2003-04-28 8:17 ` Patrick Kwan
2003-04-28 7:42 ` Alex Nee
1 sibling, 1 reply; 4+ messages in thread
From: Joel Newkirk @ 2003-04-28 7:08 UTC (permalink / raw)
To: Patrick Kwan; +Cc: netfilter
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: netmeeting (incoming and outgoing connection)
2003-04-28 5:35 netmeeting (incoming and outgoing connection) Patrick Kwan
2003-04-28 7:08 ` Joel Newkirk
@ 2003-04-28 7:42 ` Alex Nee
1 sibling, 0 replies; 4+ messages in thread
From: Alex Nee @ 2003-04-28 7:42 UTC (permalink / raw)
To: lists.netfilter
Yes but i believe it must be forwarded to an internal IP
thus meaning you would need to have Multiple external IP's ...
----- Original Message -----
From: "Patrick Kwan" <pat@pat.dyndns.info>
To: <netfilter@lists.netfilter.org>
Sent: Monday, April 28, 2003 3:35 PM
Subject: netmeeting (incoming and outgoing connection)
> 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?
>
> Please clarify me. (already search the past thread)
> Many thanks your advices.
>
>
> Patrick
>
>
>
>
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: netmeeting (incoming and outgoing connection)
2003-04-28 7:08 ` Joel Newkirk
@ 2003-04-28 8:17 ` Patrick Kwan
0 siblings, 0 replies; 4+ messages in thread
From: Patrick Kwan @ 2003-04-28 8:17 UTC (permalink / raw)
To: Joel Newkirk; +Cc: netfilter
Hello,
Thanks your help first!
I found there is a OpenGatekeeper H323 proxy, it seem to solve that
limitation. Am I right?
Or any other suggestions?
Thanks!
Patrick
> 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
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-04-28 8:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-28 5:35 netmeeting (incoming and outgoing connection) Patrick Kwan
2003-04-28 7:08 ` Joel Newkirk
2003-04-28 8:17 ` Patrick Kwan
2003-04-28 7:42 ` Alex Nee
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.