[167889] in North American Network Operators' Group
Re: turning on comcast v6
daemon@ATHENA.MIT.EDU (Josh Hoppes)
Tue Dec 31 12:37:16 2013
In-Reply-To: <52877BE3-CDE9-49D2-8D3D-4B7CF4576E4B@ufp.org>
Date: Tue, 31 Dec 2013 11:37:02 -0600
From: Josh Hoppes <josh.hoppes@gmail.com>
To: Leo Bicknell <bicknell@ufp.org>
Cc: Jamie Bowden <jamie@photon.com>,
North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> Now, boss man comes in and has a new office opening up. Go grab the r1 box
> out of the closet, you need to upgrade the code and reconfigure it. Cable
> it up to your PC with a serial port, open some some sort of terminal program
> so you can catch the boot and password recover it. Plug it's ethernet into
> your lan, as you're going to need to tftp down new config, and turn it on.
Why are you putting a router that you know needs to be reconfigured
onto a production network? This could backfire regardless of IPv6,
since you could have a similar issue if the router was performing DHCP
from a locally configured pool. If someone did this and complained to
me I would tell them they just learned a lesson and now know better
then to go connecting equipment with an existing configuration to a
production network without doing a full review first.
