[159339] in North American Network Operators' Group
Re: OOB core router connectivity wish list
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Wed Jan 9 11:24:35 2013
In-Reply-To: <CAP-guGWxsGryfE0=fuezeqfu6yO7u76DL5YjG4UgT=3a63kDTQ@mail.gmail.com>
Date: Wed, 9 Jan 2013 11:21:49 -0500
From: Christopher Morrow <morrowc.lists@gmail.com>
To: William Herrin <bill@herrin.us>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Jan 9, 2013 at 11:18 AM, William Herrin <bill@herrin.us> wrote:
> About the only time you'd strictly *need* dynamic configuration in an
> OOB is when directly connecting it to a commodity Internet link. If
> you're willing to give your poorly secured and rarely updated OOB a
> public IP address, you're a braver man than I am. If you are that
> "brave" then you'll need a more robust set of dynamic configuration
> tools than just the ones you've listed and you'll also need a dynamic
> dns client or some other mechanism for the the OOB to let you know
> what addresses it ended up on.
it's possible that he's thinking of a world where your dhcp is not
'dynamic' but a management system which can keep all the other bits of
information updated (and easily updatable!) for the remote nodes:
ip address
def-gw
dns servers
for instance.
