Date: Fri, 1 Jun 2001 14:58:59 -0500 From: "Brandt" <brandt@unkempt.net> To: "Nick Rogness" <nick@rogness.net>, "Sean-Paul Rees" <sean@seanrees.com> Cc: <questions@FreeBSD.ORG> Subject: Re: natd and NetMetting Message-ID: <004b01c0ead5$5ec58330$14be2ece@osc20> References: <Pine.BSF.4.21.0106011020390.65888-100000@cody.jharris.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've run into this before. Basically Netmeeting uses H232 or 323 protocol that isn't supported by natd. You will either have to use a public IP or a different program. Actually, when I was looking into this about 6 months ago there was a H232 proxy program in development. You might check into that. -Brandt ----- Original Message ----- From: "Nick Rogness" <nick@rogness.net> To: "Sean-Paul Rees" <sean@seanrees.com> Cc: <questions@FreeBSD.ORG> Sent: Friday, June 01, 2001 10:23 AM Subject: Re: natd and NetMetting > On Thu, 31 May 2001, Sean-Paul Rees wrote: > > > Is there some magic I can perform to get NetMeeting to operate from a > > machine behind my natd box? > > Ahh. Netmeeting will not work because it encodes the source > address (192.168.x.x) in the payload of the packet. Since natd > only fools with the packet header the receiving machine tries to > contact 192.168.x.x OR so I've heard. > > > Nick Rogness <nick@rogness.net> > - 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004b01c0ead5$5ec58330$14be2ece>