Date: Sun, 27 Jan 2002 16:36:16 -0500 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: "Clemens Hermann" <haribeau@gmx.de> Cc: "BSD NET-List" <freebsd-net@FreeBSD.ORG> Subject: Re: natd restart Message-ID: <002901c1a77a$a7027790$1200a8c0@gsicomp.on.ca> References: <20020126234617.C267@idefix.local> <5.1.0.14.0.20020127002514.01d56978@mail.drwilco.net> <20020127100745.A267@idefix.local> <00c401c1a743$2f8f9170$1200a8c0@gsicomp.on.ca> <20020127214638.A267@idefix.local>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 27.01.2002 um 09:59:14 schrieb Matthew Emmerton: > > Hi Matthew, > > > Why not just add an IP alias for the "new" network on each machine? Each > > system will respond to packets directed to either network, but without the > > complexity of a NAT box in the middle. Once you've got everything switched, > > then you can remove the original IP addresses. > > Sounds like a way better solution as the one I thought of. > Thanks a lot for this hint! > > > I've used this method in the > > past to transition LANs between IP ranges and it works absolutely fine. > > Did you use Windows machines in this setup? > There are many NT4 Boxes, Win2k, some 98 and 95 computers here. No, I used the alias trick on a bunch of UNIX and NT4 servers. All of the desktops on the LAN used DHCP so it was easy to change them. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002901c1a77a$a7027790$1200a8c0>