REPORTING-BUGS 1.7 KB

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