Am CC'ing this to Jeff Pierce; am not sure if he's on
the leave-devel list or not. His post to the LEAF list (CC'd
below) got me thinking....
Could you kernel-owners post a netmeeting.o module
for Dachstein and Oxygen? Jeff seems to have been able to
get Netmeeting to work, which is nothing to sneeze at. AFAIK,
Netmeeting uses H-323 for host calling, *along with* a buncha
other protocols which also embed IP address information in the
data payload (which breaks masq'ing...grrr).
Since this netmeeting.o module appears to address
all of them, it seems to me a worthwhile replacement for
the more limited ip_masq_h232 one.
Thoughts?
-Scott
----------------------------------------------
Message: 2
Date: Thu, 08 Nov 2001 13:03:19 -0500
From: Jeff Pierce <[EMAIL PROTECTED]>
To: Blanton Lewis <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: [Leaf-user] netmeeting
I am using the following script on Eigerstien2 after starting module
netmeeting.o
#!/bin/sh
IPMASQADM=/usr/sbin/ipmasqadm
EXTERN_IP=`ip addr list label ppp0 |
grep inet |
sed '1!d'|
sed 's/^[^.0-9]*\([.0-9]*\).*$/\1/'`
echo Extern IP: $EXTERN_IP
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 389 -R 192.168.2.205 389
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 522 -R 192.168.2.205 522
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 1503 -R 192.168.2.205 1503
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 1720 -R 192.168.2.205 1720
$IPMASQADM portfw -a -P tcp -L $EXTERN_IP 1731 -R 192.168.2.205 1731
I don't really want it running all of the time.
And this seems to work fine.
Also, goto:
http://support.microsoft.com/support/kb/ARTICLES/Q158/6/23.asp
It explains what is needed to get netmeeting through a firewall.
Now, I have a question, I use netmeeting.o for netmeeting from:
http://netmeetingmasq.sourceforge.net/
However I see mention of ip_masq_h323.o, what are the differences and
which is the better to use?
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
