From owner-freebsd-questions Wed Feb 9 20:41:10 2000 Delivered-To: freebsd-questions@freebsd.org Received: from vail.net (vail.net [199.45.148.10]) by builder.freebsd.org (Postfix) with ESMTP id 4338A430F for ; Wed, 9 Feb 2000 20:41:07 -0800 (PST) Received: from gatekeeper.cfcc.com (cfcc.com [204.144.216.251]) by vail.net (8.9.3/8.9.3) with ESMTP id VAA21169 for ; Wed, 9 Feb 2000 21:36:20 -0700 (MST) Received: from ibis.ivanfetch.tzo.com (206.133.170.176 [206.133.170.176]) by gatekeeper.cfcc.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id CYDH57WC; Wed, 9 Feb 2000 21:44:34 -0700 Date: Wed, 9 Feb 2000 21:39:34 -0700 (MST) From: Ivan Fetch X-Sender: ifetch@ibis.ivanfetch.tzo.com To: freebsd-questions@FreeBSD.ORG Subject: Re: What can natd forward besides telnet, ftp, http, Etc? In-Reply-To: <20000209210222.Q17536@fw.wintelcom.net> 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 Thank you for your reply Albert -- Where might I be able to start looking into specific proxies for the kind of connections you describe below (connections in which a server is really calling you back)? VPN is the only connection I know of at the moment that seems to do this for sure. Thanks Again, Ivan. On Wed, 9 Feb 2000, Alfred Perlstein wrote: > * Ivan Fetch [000209 20:50] wrote: > > Hi, > > I was wondering where there might be a list of what natd can forward > > "automatically" besides telnet, ftp, http, Etc. More specifically, I am > > using FreeBSD 3.4-release and natd as a very nice gateway. I notice that > > one of the things which is not forwarded from the internal network to the > > internet is VPN packets sent from one of the win98 clients. IS it > > possible to have these packets be forwarded (I know with Linux this took > > some patching and such)? What else (real audio?) does natd have > > "difficulty" forwarding from the internal network to the outside world? > > Any connectionless procotols, or protocols requireing that the server > perform a callback connection to the client behind the natd. > > Basically, udp connections are going to have issues without an explicit > proxy because there is no state with UDP, it's connectionless therefore > the natd doesn't really know where to send packets recieved in responce > to the client contacting an outside source. > > The same problems will happen when a connection is 'active' from > the server, meaning the client connects via TCP to the server, then > the server tries to initiate a TCP connection back the client. > > The problem is that natd doesn't really know which machine to forward > the incoming connection to. > > -Alfred > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message