3 about: Create a report to help us improve
14 YOU MUST READ THIS TO HAVE YOUR ISSUE ADDRESSED
16 PLEASE READ AND FILL OUT THIS TEMPLATE
18 NEGLECTING TO PROVIDE INFORMATION REQUESTED HERE WILL RESULT IN
19 SIGNIFICANT DELAYS ADDRESSING YOUR ISSUE
23 - OPERATING SYSTEM VERSION
26 FAILURE TO PROVIDE THIS MAY RESULT IN YOUR ISSUE BEING IGNORED
28 FOLLOW THESE GUIDELINES:
30 - When reporting a crash, provide a backtrace
31 - When pasting configs, logs, shell output, backtraces, and other large chunks
32 of text, surround this text with triple backtics
38 - Include the FRR version; if you built from Git, please provide the commit
40 - Write your issue in English
48 A clear and concise description of what the bug is.
50 Put "x" in "[ ]" if you already tried following:
53 - [ ] Did you check if this is a duplicate issue?
54 - [ ] Did you test it on the latest FRRouting/frr master branch?
59 Describe the steps to reproduce the behavior.
60 Be as descriptive as possible.
66 3. Scroll down to '....'
72 Write here a clear and concise description of what you expected to happen when
73 using the reproduction steps you provided above
78 If applicable, add screenshots to help explain your problem.
83 Include your operating system type and version here
85 FAILURE TO PROVIDE THIS MAY RESULT IN YOUR ISSUE BEING IGNORED
87 <!-- e.g. Fedora 24, Debian 10] -->
89 <!-- [e.g. Linux 5.4, OpenBSD 6.6] -->
91 <!-- e.g. 6.0, 7.4 -->
94 **Additional context**
96 Add any other context about the problem here.