Everything I found also warned that inbound audio wouldn't work. I was able to verify that last night. Although, in a meeting with four or five people, I found that the audio becomes a distraction, slows down communication, trivializes comments - people tend to think more about what they say when the write/type it out, and worst of all, there is no log to save when you rely on just audio. All in all, I don't miss the audio. But the workaround does work for now. Donn ----- Original Message ----- From: "Alan Gore" To: Sent: Thursday, April 13, 2000 11:12 PM Subject: Re: Netmeeting through a linux Masq box > At 09:00 PM 4/12/00 -0700, you wrote: > >I found the following describing how to use autoforward. I have written a > >script that runs these commands and another the reverse the forwarding. Have > >not tested it yet but the link is at > >http://www.tsmservices.com/masq/detailform.php3?132 > > > >Primary TCP connections: > >This will allow what microsoft calls the 'Primary TCPConnections' to work. > >This will allow such features as: applicationsharing, whiteboard, chat, file > >transfer, and directory lookups. > > > >ipmasqadm autofw -A -r tcp 389 389 > >ipmasqadm autofw -A -r tcp 522 522 > >ipmasqadm autofw -A -r tcp 1503 1503 > >ipmasqadm autofw -A -r tcp 1720 1720 > >ipmasqadm autofw -A -r tcp 1731 1731 > > I tried adding these lines to my RH6.1 firewall script, but I still have the > same symptom when I run NetMeeting on a Windows client: audio outbound is > OK, but no audio received. > > > _______________________________________________ > Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss >