Hi Christian,
On Fri, 5 May 2006, Christian Hammers wrote:
Just to be sure, "RC" means that the patch is now in a releasable
state
Yes. The 0.98 CVS branch is now in the "this is what we intend to
release as 0.98.6" state.
and does no longer change the default behaviour?
The defaults are unchanged.
The difference in 0.98 now is that the 'no ip rip authentication
mode' will actually set "no authentication". It will write out such
as well, that should allow everything to remain compatible, and also
allow any 0.98 users to upgrade to 0.99 in a compatible manner
(provided they 'write file' in 0.98.6+ before going to 0.99, or at
least, take heed of either the output of 'show running-config' or the
updated documentation - the section on "RIP Authentication").
Or if it does, could it cause any trouble?
Wrt ripd:
upgrading from <= 0.98.5 to >= 0.98.6 shouldn't be any trouble - as
the defaults remain the same.
upgrading from >= 0.98.6 to 0.99+ should be ok too, except that any
users who relied on simple-auth being the default will need to have
either:
- done a 'write file' in >=0.98.6 any time before upgrading
- or taken heed of the documentation in 0.98.6 and manually updated
their ripd.conf
- or noticed that 0.98.6+ 'show running-config' output has changed,
and explicitely outputs 'ip rip authentication mode text', and
hence taken that as their cue to update their ripd.conf
ie for users who don't use 'write file' to maintain their ripd.conf,
there are two 'cues' that things have changed - the docs and 'show
running-config'. If they take heed of those cues, then they wont have
problems upgrading later to 0.99+.
RIPv2 MD5 authentication users would be fine (and hopefully anyone
using RIPv2 authentication is using MD5) - nothing changes there.
Make sense? :)
regards,
--
Paul Jakma [EMAIL PROTECTED] [EMAIL PROTECTED] Key ID: 64A2FF6A
Fortune:
Beware of geeks bearing graft.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
