[FROG] IS-IS HMAC-MD5 Authentication Not Working

[Donald Sharp]

Chriztoffer -

The `lsp-mtu (128-4352)` command has never been 'hidden' ( this
connotates you can't see it in the vtysh cli if you look for it, you
have to know it exists ), it has always been visible just not
documented.  Quentin's commit is trying to document the command in our
documentation.

This command was introduced in Nov 2015:

commit b20ccb3aa94ff96e8d32e5206d8b16fa3b081908
Author: Christian Franke <nobody at nowhere.ws>
Date:   Tue Nov 10 18:43:31 2015 +0100

    isisd: allow to adjust lsp-mtu

    Signed-off-by: Christian Franke <chris at opensourcerouting.org>
    Acked-by: Donald Sharp <sharpd at cumulusnetworks.com>

This command has been available in FRR since it's first release:

sharpd at eva:~/frr3$ git checkout frr-2.0
Previous HEAD position was 01bb08b6d isisd: API: timers (IIH, CSNP, PSNP)
HEAD is now at 3e71b5d90 Release: FRR-2.0
sharpd at eva:~/frr3$ git grep lsp-mtu
isisd/isis_vty.c:       "lsp-mtu <128-4352>",
isisd/isis_vty.c:  VTY_GET_INTEGER_RANGE("lsp-mtu", lsp_mtu, argv[0],
128, 4352);
isisd/isis_vty.c:       "no lsp-mtu",
isisd/isis_vty.c:       "no lsp-mtu <128-4352>",
isisd/isisd.c:      vty_out(vty, " lsp-mtu %u%s", area->lsp_mtu, VTY_NEWLINE);

I would like to apologize for the state of our documentation.  For
many years the community accepted new code without a requirement that
it also be documented in our docs.  This has led to a gap where there
is a large number of knobs/commands that are not documented very well
at all.  This has changed recently as that all new cli changes (
semantically if you touch a DEFUN/DEFPY function ) must also come with
documentation.  In addition people have been trickling in missed cli
documentation changes pretty regularly over the last year( I like
Quentin have been hitting missed commands when I notice it from
community interaction ).  It's a large effort that takes away from
what developers see as their day job, so missed documentation has
taken a small back seat to new functionality and bug fixes.  Having
said that this is one of those areas where you don't need to be a `c`
coder at all and we would appreciate help from anyone who uses FRR.

I think, Mark's question now, is how to get authentication working
properly using isisd.  I've included Christian Franke on the email
since he was one of the primary authors of isisd.  Hopefully he can
shed some light on what is going on here?

donald

On Wed, Apr 8, 2020 at 7:07 AM Chriztoffer Hansen <ch at ntrv.dk> wrote:
>
> Mark,
>
> On Wed, 8 Apr 2020 at 09:45, Mark Tinka <mark.tinka at seacom.mu> wrote:
> > > qlyoung at nicobar$ sudo vtysh
> > >
> > > Hello, this is FRRouting (version 7.4-dev).
> > > Copyright 1996-2005 Kunihiro Ishiguro, et al.
> > >
> > > nicobar# find mtu | include isis
> > > ...
> > >   (isis)  lsp-mtu (128-4352)$val
> > >   (isis)  no lsp-mtu [(128-4352)]
> >
> > So the "lsp-mtu" command is coming to 7.4?
>
> Based on the PR, the command is already there, but just not exposed
> when using tab-complete or `find mtu | include isis` to look for it.
> (i.e. hidden command in "version < 7.4")
>
> https://github.com/FRRouting/frr/pull/6183/files
>
> _______________________________________________
> frog mailing list
> frog at lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog