Hi, On Sun, 15 Nov 2015 15:37:29 +0700 Han Coumans <[email protected]> wrote:
> Dear Timo, Quagga dev-list, > > Every time there is a new protocol implemented in Quagga it will give > some (hopefully small) issues. Nothing wrong with that, and they will > be fixed. Yes. Like with every bugfix, it's possible that it breaks something else. We've seen that once in a while too :) > With NHRP this is no different. > There is the OpenNHRP implementation and as of writing it's project > page ( http://sourceforge.net/projects/opennhrp/ ) reports 18 > downloads in the past week. > If one takes a look at Cisco's NHRP pages the latest update is from > April 2007. > > OpenNHRP gets 5 stars from 4 reviewers (with one very strange one). Yes, I am the author of OpenNHRP also. I know what it can do and cannot do. > The only use of this technology is for VPNs. Cisco mentions it works > with FR and ATM, but if one uses PVCs, than bypassing the hub for > traffic will not be possible. This is not entirely true. While NHRP is originally done for ATM things, and the RFCs are old. The protocol is actively used in new technologies. This is because NHRP was designed to be protocol independent. DMVPN is fully based on it. So is FlexVPN which basically it the new Cisco implementation of DMVPN. FlexVPN was added only few years back, and is actively developed. The documentation for it does not talk too much about NHRP as it's role is smaller (e.g. registration is left out, and handled in IKEv2 exchange). But the shortcut establishment still is fully based on NHRP. Also Quagga/NHRP focuses on the DMVPN implementation. The legacy ATM stuff is not supported at all. It might be an option to call it Quagga/DMVPN or similar. > To me there is no use in having NHRP being part of Quagga and with > OpenNHRP the functionality can be set up. Why? It's not really an argument to say that FOO can do it too, so we don't need it. I can do BGP with openbgpd and BIRD. Why do we need Quagga/BGP? Please elaborate. As counter argument, OpenNHRP has few bugs and missing features that are impossible to fix if it's separated daemon. One to name is binding shortcuts to BGP prefixes - that is that the shortcuts are invalidated/refreshed immediately on BGP prefix update. This simply is not doable without strong integrationg to RIB. Quagga/NHRP module does this right. I did try to implement this in opennhrp by few different ways, e.g. by using policy routing and putting the shortcuts to different table - but it created another set of problems when the BGP prefix and the NHRP shortcut prefix are not of equal length. Another benefit is unified configuration and debugging (vtysh). Writing NHRP as Quagga module allows to directly use Quagga CLI as configration tool and to investigate what's happening on related protocol levels, simplifying things and allow a more unified user experience. In short - me, the author of both OpenNHRP and Quagga/NHRP - concluded that the benefits of doing it as quagga module are so great, that I took the time to do the coding, testing etc. all again. Thanks, Timo _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
