Date: Tue, 19 Oct 1999 08:48:06 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: "Zuidam, Hans" <Hans.Zuidam@nl.origin-it.com> Cc: "'hackers@freebsd.org'" <hackers@FreeBSD.ORG> Subject: Re: natd question Message-ID: <Pine.BSF.4.10.9910190844130.36458-100000@resnet.uoregon.edu> In-Reply-To: <9B7E8CE3E214D311A3050008C7A4BDDB934693@nlehx061.ehvvon.nl.origin-it.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Oct 1999, Zuidam, Hans wrote: > I want to set up a test network which (partly) mirrors our production > side network. To match reality as close as possible we keep the IP > addresses in the test network the same as in the production network. In > order not to run around with tapes between the two networks, I would like > to create the following setup: > > ( 130.144.120/22 ) ------ | FreeBSD | ------ ( 130.144.120/22 ) > + (real) + | | + (test) + Ew. There's no way the system can differentiate between the two. It'll probably scream bloody murder when the ARPs start flying. You'll generate megabytes of 'arp: 130.144.120.5 changed from XXXXXXXXXX to YYYYYYYYY' messages. I'd suggest assigning fake addresses to to your test network's primary IPs. Once your setup is complete unplug one of the networks from the bsd box then throw all the IPs over to the real IPs. I assume the two networks don't need to talk to one another once you have the test harness set up. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org 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.BSF.4.10.9910190844130.36458-100000>