From owner-freebsd-isp Mon Jan 24 14:25:34 2000 Delivered-To: freebsd-isp@freebsd.org Received: from guardian.fortress.org (guardian-ext.fortress.org [199.202.137.242]) by hub.freebsd.org (Postfix) with ESMTP id 962181518F for ; Mon, 24 Jan 2000 14:25:28 -0800 (PST) (envelope-from andrew@guardian.fortress.org) Received: from localhost (andrew@localhost) by guardian.fortress.org (8.9.3/8.8.8) with ESMTP id RAA50012; Mon, 24 Jan 2000 17:13:56 -0500 (EST) (envelope-from andrew@guardian.fortress.org) Date: Mon, 24 Jan 2000 17:13:56 -0500 (EST) From: Andrew Webster Reply-To: andrew@pubnix.net To: Mitch Collinsworth Cc: Sean Michael Whipkey , freebsd-isp@FreeBSD.ORG Subject: Re: Network renumbering (Yack!) In-Reply-To: <200001242041.PAA43470@benge.graphics.cornell.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org YUCK, been there, done that. It was a "medium to low" priority project that laster over 12 months. In reflection, it was a mistake, and should have been done at a very high level as quickly as possible. One think that you need to be aware of (yes I know this is completely irrelevant to the ISP mailing list), is that if you have any NT boxes running WINS, you will have BIG problems with multiple IPs on these machines. You'll need to identify these systems and cut them over immediately and/or setup replicas of these systems on old/new networks to ease the transition. On Mon, 24 Jan 2000, Mitch Collinsworth wrote: > > >daniel B wrote: > >> I dreaded this moment would come but I am in a position that I need to > >> change upstream and all DNS info is going to change, customer workstations > >> may have to be reconfigured ... > >> Since I haven't done this before what is the least painful way to handle > >> this task? is there a documented procedure/how-to somewhere? > >> Realy don't want to start guessing. > > > >We're in the middle of that right now, and all I can really think of to > >say is..."Sorry." :-( > > > >It's rough. We started by giving our servers multiple IP addresses, one > >old and one new. We then moved our customers over slowly - first all of > >the static IP addresses, and then each phone number depending on how it > >was tied to a router. We hired an outside consultant to do some of our > >network customers, which was a mistake. > > > >You just have to be patient...:) > > I nominate this line for understatement of the month! :-) > > Another thing to consider it taking this as an opportunity to start > using DHCP for all non-server systems. You might even want to use > it on some of your servers, though I haven't felt that brave yet. > This seems like a good idea even if you're not using dynamic addresses > since it puts all the network configuration info in one place where > it's easy to change when you need to. > > -Mitch > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > --- Andrew Webster FULL SERVICE ISP President http://www.pubnix.net PubNIX Inc. Access: PPP - SHELL - UUCP - VPN - ... P.O. Box 147 Hosting: WWW - Email - DB - Your Servers - ... C.S.L. QC H4V 2Y3 tel: 514-990-5911 fax: 514-990-9443 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message