From owner-freebsd-isp@FreeBSD.ORG Wed Apr 26 15:07:34 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9B7316A418 for ; Wed, 26 Apr 2006 15:07:34 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66B3C43D45 for ; Wed, 26 Apr 2006 15:07:33 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 6493D3DC; Wed, 26 Apr 2006 10:07:33 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 960D461C32; Wed, 26 Apr 2006 10:07:32 -0500 (CDT) Date: Wed, 26 Apr 2006 10:07:32 -0500 From: "Matthew D. Fuller" To: Brian Candler Message-ID: <20060426150732.GQ4202@over-yonder.net> References: <20060426104803.GO4202@over-yonder.net> <20060426134530.GB8912@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060426134530.GB8912@uk.tiscali.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: freebsd-isp@freebsd.org, Tyrone.VanDerHaar@TelecityRedbus.com Subject: Re: Router upgrade.... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 15:07:34 -0000 On Wed, Apr 26, 2006 at 02:45:30PM +0100 I heard the voice of Brian Candler, and lo! it spake thus: > > I think you're forgetting the time sat in single-user mode while > doing installworld and manually mergemaster'ing the rc scripts. No, I'm not, because I wouldn't do that :) When I upgraded some production systems from RELENG_2_2 to mid-life RELENG_4, you're darn tootin' I did a lot of work in single-user mode (and some off boot disks, for that matter). But extraordinary circumstances aside, I do virtually all my upgrades in normal multi-user, and often many miles from the console. Now, I get away with it because I've done a lot of upgrades before, and I watch the mailing lists and keep track of any gotchas in a given upgrade. But Usually(tm) there's not even a twitch. I've done upgrades from 5.3/5.4ish to RELENG_6 remotely (no console, just ssh) several times, on i386 and amd64, and wouldn't flinch at doing it again. To a large extent, the smoothness of doing so is related to how often you do it; if you go a year or two between upgrades, accumulated differences can make things really unpleasant, while doing it every few months is usually grass through a duck. > Personally I prefer the other option suggested by the OP: > - build a brand new router using whatever O/S and software revisions you > choose to be on Which is the other extreme. I've rarely been in a situation where I consider my "normal" method too risky and went with something like this, but "rarely" isn't "never". In the end, you always have to balance. In the OP's case, I wouldn't be too worried about just doing it in-place; whether that would apply for anyone else, I (obviously) couldn't say. > If you want it to come up on the same IP address then you may have > to clear ARP caches on some other devices on the same LAN > segment(s), but that's about it. If you got real smart, you could just pull the NIC and put it in the new box, so even if something was foolishly holding onto the MAC, it would still get there :) -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.