[quagga-dev 8369] Re: Expose announced routes through SNMP

Greg Troxel gdt at ir.bbn.com
Tue Nov 23 20:45:21 GMT 2010


You can certainly post the patch, but the preferred method is to have a
public git repository that's a clone of the official one with a feature
branch with your work (based on tip of master or the latest release
tag).  See HACKING in the current repository.  Then send a note
describing how much testing the change has had - sounds like it's been
run quite a bit in operations - on what OS/CPU/etc. combinations.

I'm not sure what you mean about custom OID, but assuming you have
extended the MIB beyond the standards, you should perhaps address that
within the IETF.  At least submit an ID describing what's needed.  I
would be reluctant to add code with private codepoints to quagga, but
it's not a line in the sand.  Regardless it is helpful to the community
to post the patch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20101123/524c9a89/attachment-0001.sig>


More information about the Quagga-dev mailing list