Date: Wed, 20 Oct 1999 00:30:16 -0400 (EDT) From: Mike Nowlin <mike@argos.org> To: Nick Rogness <nick@rapidnet.com> Cc: Brian Beattie <beattie@aracnet.com>, hackers@FreeBSD.ORG Subject: Re: natd question Message-ID: <Pine.LNX.4.05.9910200024230.29285-100000@jason.argos.org> In-Reply-To: <Pine.BSF.4.05.9910191146090.99921-100000@rapidnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > ( ) +-------+ +-------+ ( ) > > + + | | | | + + > > ( 130.144.120/22 ) -- |FreeBSD| ---- |FreeBSD| --( 130.144.120/22 ) > > + (real) + | | | | + (test) + > > ( ) +-------+ +-------+ ( ) > > (~~~~~~~~~~) (~~~~~~~~~~) If the whole purpose of this is to (as stated in the original message) avoid running Sneakernet between the two networks, why not use a protocol that really doesn't care about IP addresses, network masks, etc. -- possibly UUCP... It's pretty easy to set up, and if you run it over a 115200 baud serial line, performance is quite adequate for most things, and you won't have to deal with the fact that the two nets share addressing. If you're not planning on using UUCP in common use on the final production network, the changes you'd have to make in the config files for it between the two networks wouldn't make a bit of difference once testing is done -- even if you were, the changes still shouldn't make any difference unless you intentionally tried to create problems. (mental reference to a recent thread on -security, I believe....:) ) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.05.9910200024230.29285-100000>