From owner-freebsd-questions Mon Apr 23 16:16:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id 7711237B423 for ; Mon, 23 Apr 2001 16:16:53 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f3O0OpW26541; Mon, 23 Apr 2001 19:24:51 -0500 (CDT) (envelope-from nick@rogness.net) Date: Mon, 23 Apr 2001 19:24:51 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: Kent Stewart Cc: Roelof Osinga , G D McKee , Questions FreeBSD Subject: Re: M$ NetMeeting In-Reply-To: <3AE4B34F.BA846BE1@urx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Apr 2001, Kent Stewart wrote: > > > Does anyone have any ideas? I am only interested in getting > NetMeeting > > working from one PC inside my LAN. > > > The thing whith proprietary software is, is that it's designed to > > lock users in. Hear what you want is possible with M$'s Catapult. > > Part of the problem is that xxx-323 (or whatever it is protocol) isn't > designed to be nat-able. Your address is included and if your system > is setup like mine is, the people on the other end try to link to my > internal 192.x.x.x IP instead of the external one. If there was a BSD machine or Cisco on the other side, use a tunnel! Otherwise, You can do it with multiple outside IP's...but it is tricky if you try to leave it on the inside network. Another solution is some H-323 proxy software...IIRC, www.openh323.org. I don't know if it works or not. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message