c> The not RSPF iface counter is used when you receive RSPF
c> packets on an interface that you haven't specified in the
c> configuration file. Of course if the inteface is not in the
c> config, then rspfd will not send any RSPF packets out there,
c> including RRHs.
I assume that the code disregards any RRH or other RSPF information received on
an interface not authorized for RSPF? This is a security issue.
c> There is also a bug in the *NOS rspf trace code that says 2.2
c> packets are invalid packet type, this should be changed to
c> someting like incorrect version.
Oops. I thought I fixed that in 1992.
c> I was working on a port of RSPF v2.2 to *NOS. A hard drive
c> failure whiped out what I had done (which wasn't that much)
c> and I haven't started again yet. I'm working on getting
c> RSPFd v0.08 out.
I spent a fair amount of time on this, and I came to the conclusion that
significant changes would be necessary in the NOS IP routing code. That, in
turn, was just too big a job to contemplate at the time. The worst problem had
to do with the mechanism used to test and adjacency, and how to assure that the
routing table would be returned to a valid state if the tested route proved to
be no good.
c> See what interfaces you have and check that this interface
c> you have your friends on is in that list. I should put more
c> bugs in my code, it is the only way I find out who uses the
c> program :)
There is a supply of bugs in all extant code relating to RSPF, including mine.
-- Mike