Return to REPORTING-BUGS CVS log

Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / quagga

quagga

    1: This file describes the procedure for reporting Quagga bugs. You are not
    2: obliged to follow this format, but it would be great help for Quagga developers
    3: if you report a bug as described below.
    4: 
    5: Bugs submitted with woefully incomplete information may be summarily
    6: closed.  Submitters of bugs against old versions may be asked to
    7: retest against the latest release.  Submitters may be asked for
    8: additional information.  Bugs may be closed after 30 days of
    9: non-response to requests to reconfirm or supply additional
   10: information.
   11: 
   12: Report bugs http://bugzilla.quagga.net
   13: 
   14: Please supply the following information:
   15: 1. Your Quagga version or if it is from git then the  commit reference.
   16:    Please try to report bugs against git master or the latest release.
   17: 2. Quagga daemons you run e.g. bgpd or ripd and full name of your OS. Any
   18:    specific options you compiled Quagga with. 
   19: 3. Problem description. Copy and paste relative commands and their output to
   20:    describe your network setup e.g. "zebra>show ip route".
   21:    Please, also give your simple network layout and output of relative OS
   22:    commands (e.g., ifconfig (BSD) or ip (Linux)).
   23: 4. All Quagga configuration files you use. If you don't want to publish your
   24:    network numbers change 2 middle bytes in IPv4 address to be XXX (e.g.
   25:    192.XXX.XXX.32/24). Similar could be done with IPv6.
   26: 5. If any Quagga daemon core dumped, please, supply stack trace using the
   27:    following commands: host> gdb exec_file core_file , (gdb) bt .
   28: 6. Run all Quagga daemons with full debugging on (see documentation on
   29:    debugging) and send _only_ part of logs which are relative to your problem.
   30: 7. If the problem is difficult to reproduce please send a shell script to
   31:    reproduce it.
   32: 8. Patches, workarounds, fixes are always welcome.
   33: 
   34: Thank You.