From: "pengjie" <bill.peng@ocamar.com>
To: Netfilter Mailinglist <netfilter@lists.netfilter.org>
Subject: h323 & nat
Date: Tue, 11 May 2004 09:39:25 +0800 [thread overview]
Message-ID: <003101c436f8$cb052d80$0f6ea8c0@acamarpeng> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
i had read many documents but i didn't find answer.
i have a network as following:
A------------------B====================C
192.168.110.x 192.168.110.y 202.101.k.m 202.101.k.n
the B is a gateway doing NAT. it's eth0 is 192.168.110.y and eth1 is 202.101.k.m. there is RH9 running on it,it's kernel is 2.4.21. i have pathched the h323,and runned up the modules ip_conntrack_h323 and ip_nat_h323.
the A and the C are netmeeting clients.
i test it with 2 methods:
1)both A and C logon to a ILS.
RESULTS:
A calls C is ok, and they can chat to each other.
C calls A is failure, i see the address called is the private address of A. so setting up is failure.
QUESTION: doesn't the patch do something when client logon to a ILS?
2)call each other without the ILS.
i add a rule: iptables -t nat -A PREROUTING -i eth1 -p tcp -m multiport --dports 1503,1720 -j DNAT --to-destination 192.168.110.x
they call each other with IP address. A calls C with C's IP as the destination, and C calls A with gateway's valid IP as the destination.
RESULTS:
A calls C is ok, and they can chat to each other.
C calls A is ok, but they can't chat to each other.
QUESTION: is the rule right? h.323 streaming port is dynamic, does it result this symptom?
even though i add the rule right,i think it's no use.it just enable one client to go through the gateway.is it?
any help is appreciated.
[-- Attachment #2: Type: text/html, Size: 3139 bytes --]
next reply other threads:[~2004-05-11 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 1:39 pengjie [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 22:21 H323 NAT Jerry Rasmussen
2003-11-20 22:16 George Vieira
2003-11-20 12:49 German Viera
2002-10-15 16:06 Carles Xavier Munyoz Baldó
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='003101c436f8$cb052d80$0f6ea8c0@acamarpeng' \
--to=bill.peng@ocamar.com \
--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