Thank you so much for your help! I finally gave up ipchains, and switched to iptables using kernel-2.4.18. Then, I tried the NewNAT kernel patch on http://roeder.goe.net/~koepi/, which including ip_conntrack_h323, and ip_nat_h323 modules. Also, I recompiled the latest iptables, as required.
After that, my netmeeting behind NAT works after supplying some port forwarding rules. Surprisingly, my V2 Communicator simply works too! (though I am still not sure what protocol and which port number it uses.) Maybe it's because of the patched version of kernel and iptables. Btw, I really enjoy the discussion in debian-gb ML, through which I am able to learn more, and also get quick response. On Wed, May 29, 2002 at 10:25:15AM -0500, Alex Lau wrote: > �Ҳ�֪������ô�취�ҳ�proprietary socket �� standard (most of > them won't show you how the socket is bind or anything ) �� > ���nmap�ҳ�port number. Kernel module �Ļ�����̫����, �಻��, > ��Ҫ��module����ʲô����, ������reverse engineer���ǵ�socket call > Ӧ�ÿ����ҵ���. ����һЩlink��google.com�ҵ���ϣ���а���, �Һܾ� > û��Develope��Kernel�йصĹ���, �಻̫���masq module�ķ���, ��� > [EMAIL PROTECTED] ���Ƕ�Kernel > ���бȽ��������ʶ. > http://user.rli.net/kevin/masq.html > http://dplay-masq.sourceforge.net/faq.html > http://www.thelinuxreview.com/howto/IP-MASQ/x2135.htm > http://netmeetingmasq.sourceforge.net/ > Good luck > Alex -- regards, ZM -- "The Microsoft Exchange Information Store service depends on the Microsoft Exchange Directory service which failed to start because of the following error: The operation completed successfully." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
