1This file describes the procedure for reporting Quagga bugs. You are not
2obliged to follow this format, but it would be great help for Quagga developers
3if you report a bug as described below.
4
5Bugs submitted with woefully incomplete information may be summarily
6closed.  Submitters of bugs against old versions may be asked to
7retest against the latest release.  Submitters may be asked for
8additional information.  Bugs may be closed after 30 days of
9non-response to requests to reconfirm or supply additional
10information.
11
12Report bugs http://bugzilla.quagga.net
13
14Please supply the following information:
151. 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.
172. Quagga daemons you run e.g. bgpd or ripd and full name of your OS. Any
18   specific options you compiled Quagga with. 
193. 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)).
234. 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.
265. If any Quagga daemon core dumped, please, supply stack trace using the
27   following commands: host> gdb exec_file core_file , (gdb) bt .
286. 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.
307. If the problem is difficult to reproduce please send a shell script to
31   reproduce it.
328. Patches, workarounds, fixes are always welcome.
33
34Thank You.
35