REPORTING-BUGS

   1 This file describes the procedure for reporting FRRouting bugs. You are not
   2 obliged to follow this format, but it would be great help for FRRouting 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 on Github Issue Tracker at
  13     https://github.com/frrouting/frr/issues
  14
  15 Please supply the following information:
  16 1. Your FRRouting version or if it is from git then the  commit reference.
  17    Please try to report bugs against git master or the latest release.
  18 2. FRR daemons you run e.g. bgpd or ripd and full name of your OS. Any
  19    specific options you compiled FRR with.
  20 3. Problem description. Copy and paste relative commands and their output to
  21    describe your network setup e.g. "zebra>show ip route".
  22    Please, also give your simple network layout and output of relative OS
  23    commands (e.g., ifconfig (BSD) or ip (Linux)).
  24 4. All FRR configuration files you use. If you don't want to publish your
  25    network numbers change 2 middle bytes in IPv4 address to be XXX (e.g.
  26    192.XXX.XXX.32/24). Similar could be done with IPv6.
  27 5. If any FRR daemon core dumped, please, supply stack trace using the
  28    following commands: host> gdb exec_file core_file , (gdb) bt .
  29 6. Run all FRR daemons with full debugging on (see documentation on
  30    debugging) and send _only_ part of logs which are relative to your problem.
  31 7. If the problem is difficult to reproduce please send a shell script to
  32    reproduce it.
  33 8. Patches, workarounds, fixes are always welcome.
  34
  35 Thank You.