blob: 0b0380b8dc7331900acda79159e2130a8d12ac14 [file] [log] [blame]
hasso3b564032004-02-20 20:33:43 +00001This 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.
paul718e3742002-12-13 20:15:29 +00004
hasso3b564032004-02-20 20:33:43 +00005Report bugs http://bugzilla.quagga.net
paul718e3742002-12-13 20:15:29 +00006
7Please supply the following information:
hasso3b564032004-02-20 20:33:43 +000081. Your Quagga version or if it is CVS version then the date you did checkout.
9 Always try to report the bugs on the current CVS version.
102. Quagga daemons you run e.g. bgpd or ripd and full name of your OS. Any
11 specific options you compiled Quagga with.
123. Problem description. Copy and paste relative commands and their output to
13 describe your network setup e.g. "zebra>show ip route".
14 Please, also give your simple network layout and output of relative OS
15 commands (e.g. ifconfig or ip in case of Linux).
164. All Quagga configuration files you use. If you don't want to publish your
17 network numbers change 2 middle bytes in IPv4 address to be XXX (e.g.
18 192.XXX.XXX.32/24). Similar could be done with IPv6.
195. If any Quagga daemon core dumped, please, supply stack trace using the
20 following commands: host> gdb exec_file core_file , (gdb) bt .
216. Run all Quagga daemons with full debugging on (see documentation on
22 debugging) and send _only_ part of logs which are relative to your problem.
paul718e3742002-12-13 20:15:29 +0000237. If the problem is difficult to reproduce please send a shell script to
hasso3b564032004-02-20 20:33:43 +000024 reproduce it.
paul718e3742002-12-13 20:15:29 +0000258. Patches, workarounds, fixes are always welcome.
26
27Thank You.