From: "Carles Xavier Munyoz Baldó" <carles@descom.es>
To: netfilter <netfilter@lists.netfilter.org>
Subject: H323 NAT.
Date: Tue, 15 Oct 2002 18:06:01 +0200 [thread overview]
Message-ID: <200210151806.05183.carles@descom.es> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm having lot of problems with the ip_nat_h323 and ip_conntrack_h323
netfilter modules.
I have applied the patch-o-matic to the 2.4.19 kernel source and compile it in
my firewall.
I can load the modules with:
# modprobe ip_nat_h323
I have a h323 VoIP device behind my firewall and another one in the internet.
When I call from the device behind the NAT-firewall, I can reach the device
in the Internet. All VoIP data from the device behind the firewall arrives to
the device in the internet, but all de VoIP data from the device in the
internet is sent to the private addres of the device behind the firewall, and
never arrives to it.
It seems that the ip_nat_h323 module is not making its work. It is not
changing the source IP at the h323 aplication level.
I have seen the next logs in the /var/log/messages file:
Oct 15 17:47:47 fwtemplate kernel: ASSERT: ip_nat_core.c:838
&ip_conntrack_lock not readlocked
Oct 15 17:47:47 fwtemplate kernel: ASSERT ip_conntrack_core.c:93
&ip_conntrack_lock_R71150de5 readlocked
I'm using the last iptables version (1.2.7a).
May anyone help me with this ?
Any suggestions ?
Greetings.
- ---
Carles Xavier Munyoz Baldó
carles@descom.es
Descom Consulting
Telf: +34 965861024
Fax: +34 965861024
http://www.descom.es/
- ---
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBPaw86jvYAf7VZNaaEQLZNACgn3lsxB5m17khtlSzfRd+OUpMy4gAn0E+
Or8bWYQESsQnb1QK8EFyaGB9
=yrw1
-----END PGP SIGNATURE-----
next reply other threads:[~2002-10-15 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 16:06 Carles Xavier Munyoz Baldó [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 12:49 H323 NAT German Viera
2003-11-20 22:16 George Vieira
2003-11-20 22:21 Jerry Rasmussen
2004-05-11 1:39 h323 & nat pengjie
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=200210151806.05183.carles@descom.es \
--to=carles@descom.es \
--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