hasso | 3b56403 | 2004-02-20 20:33:43 +0000 | [diff] [blame^] | 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. |
paul | 718e374 | 2002-12-13 20:15:29 +0000 | [diff] [blame] | 4 | |
hasso | 3b56403 | 2004-02-20 20:33:43 +0000 | [diff] [blame^] | 5 | Report bugs http://bugzilla.quagga.net |
paul | 718e374 | 2002-12-13 20:15:29 +0000 | [diff] [blame] | 6 | |
| 7 | Please supply the following information: |
hasso | 3b56403 | 2004-02-20 20:33:43 +0000 | [diff] [blame^] | 8 | 1. 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. |
| 10 | 2. Quagga daemons you run e.g. bgpd or ripd and full name of your OS. Any |
| 11 | specific options you compiled Quagga with. |
| 12 | 3. 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). |
| 16 | 4. 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. |
| 19 | 5. If any Quagga daemon core dumped, please, supply stack trace using the |
| 20 | following commands: host> gdb exec_file core_file , (gdb) bt . |
| 21 | 6. 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. |
paul | 718e374 | 2002-12-13 20:15:29 +0000 | [diff] [blame] | 23 | 7. If the problem is difficult to reproduce please send a shell script to |
hasso | 3b56403 | 2004-02-20 20:33:43 +0000 | [diff] [blame^] | 24 | reproduce it. |
paul | 718e374 | 2002-12-13 20:15:29 +0000 | [diff] [blame] | 25 | 8. Patches, workarounds, fixes are always welcome. |
| 26 | |
| 27 | Thank You. |