I still can't get NetMeeting to work. I installed the ip_masq_h3231.o and
followed John's instructions for this, but it still doesn't work, and ends
up locking up my STN box. However, someone previously said it works only
when receiving, not originating the call, and I haven't tried it that way
yet.
FYI, here is the instructions John provided back in December 1999:
1) Cut your STN diskette with debug support on.
2) Attach a kb and monitor
3) Boot STN
4) Alt-F8
5) Type "Of Mice and Men<CR>" for a shell prompt
6) Type "cd /lib/modules"
7) Type "snarf ftp://www.sharethenet.com/pub/ip_masq_h3231.o"
8) Type "insmod ip_masq_h3231.o"
9) test test test :)
10) Report results
Now, you will find that the link to the module no longer exists. I did find
it at this link:
ftp://ftp.kddlabs.co.jp/.10/Linux/floppy-linux/sharethenet/ip_masq_h3231.o
Perhaps the newest version, which is ip_masq_h3233.o, would work better, but
I have not been able to find this file anywhere on the net. I can find the
c source, but have no idea how to compile it for STN. If anyone can help
here, let me know.
Also, would following the above instructions only work for that session of
STN? In other words, after you reboot the box, would you have to repeat the
insmod ip_masq_h3231.o step? I assume you would; I believe that module
inserts have to be in a .rc file to get done at boot, and, again, I have no
idea how to incorporate this into STN.
I think that the big problem with NetMeeting is that it uses dynamic ports.
What good is a firewall if you have to open up the entire world? Here is the
Microsoft documentation about it:
http://support.microsoft.com/support/kb/articles/Q158/6/23.asp?LN=EN-US&SD=g
n&FR=0
I'll reproduce the settings part here:
NetMeeting uses the following Internet Protocol (IP) ports:
Port Purpose
-------------------------------------
389 Internet Locator Server [Transmission Control Protocol
(TCP)]
522 User Location Server (TCP)
1503 T.120 (TCP)
1720 H.323 call setup (TCP)
1731 Audio call control (TCP)
Dynamic H.323 call control (TCP)
Dynamic H.323 streaming [Realtime Transport Protocol (RTP) over
User Datagram Protocol (UDP)]
To establish outbound NetMeeting connections through a firewall, the
firewall must be configured to do the following:
Pass through primary TCP connections on ports 522, 389, 1503, 1720 and
1731.
Pass through secondary UDP connections on dynamically assigned ports
(1024-65535).
So, I would assume you would take care of the first 5 steps like this:
ipautofw -A -r tcp 389 389 -c tcp 389 -u
ipautofw -A -r tcp 522 522 -c tcp 522 -u
ipautofw -A -r tcp 1503 1503 -c tcp 1503 -u
ipautofw -A -r tcp 1720 1720 -c tcp 1720 -u
ipautofw -A -r tcp 1731 1731 -c tcp 1731 -u
Then I assume the last line would require something like this:
ipautofw -A -r udp 1024 65535 -c udp 1024 -u
(Not sure about the 1024 -u at the end of the last line; I assume this means
the first port in a range, but I can't find any documentation about what the
parameters in these rules mean).
That huge range of open ports would scare the daylights out of me.
As for the Dynamic H.323 call control(TCP) step, I don't have the slightest
idea how that would be implemented.
So if anyone wants to tackle any of this, be my guest. Let us all know if
you figure it out.
Cheers,
Carl
--
Visit http://www.ShareTheNet.com for info about ShareTheNet
Visit http://www.topica.com/lists/sharethenet for info about this list
___________________________________________________________
T O P I C A The Email You Want. http://www.topica.com/t/16
Newsletters, Tips and Discussions on Your Favorite Topics
