Date: Wed, 9 Feb 2000 21:02:22 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Ivan Fetch <ivanfetch@technologist.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: What can natd forward besides telnet, ftp, http, Etc? Message-ID: <20000209210222.Q17536@fw.wintelcom.net> In-Reply-To: <Pine.LNX.4.20.0002092117270.153-100000@ibis.ivanfetch.tzo.com>; from ivanfetch@technologist.com on Wed, Feb 09, 2000 at 09:20:31PM -0700 References: <Pine.LNX.4.20.0002092117270.153-100000@ibis.ivanfetch.tzo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Ivan Fetch <ivanfetch@technologist.com> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000209210222.Q17536>