Table of Contents
Reporting bugs
Bug or no bug?
In case you are unsure if what you found is a bug, or if you have other issues that are not bugs, please use the forum, IRC or mailing list.
Issue trackers
Report bugs pertaining OpenWrt functionality and device support using our issue trackers:
| Issue tracker | Description |
|---|---|
| github.com/openwrt/openwrt | Core |
| github.com/openwrt/packages | Packages |
| github.com/openwrt/luci | LuCI |
If you are unsure, please use the Packages tables to know where you should report the bug.
When reporting bugs, please be sure to specify:
- Name the tree/revision/version
- Name the affected device
- What does it do that it should not do / what does it not do that it should do
- Steps to reproduce
- What you have already done to workaround/fix the problem
- Any additional info you think is important
Remember, the better is your bug report, the more likely it is that it will be worked on, How to Report Bugs Effectively is recommended reading.
Reporting a bug is important as it raises awareness of an issue, but it does not constitute a claim that anyone has to work on fixing it.
Reporting security bugs
Please see the “Vulnerability reporting” section on the security page for more information on how to report a security vulnerability.
Reporting user interface issues
In the context of an ui issue, clear steps to reproduce would be:
- Describing the initial state (starting of a fresh config, sysupgraded from older version with retaining settings)
- Briefly mentioning the steps taken in which order, e.g.:
- What page browsed to
- What buttons pressed
- Any settings/options checked/typed/selected
- What button selected to save/apply
- Clearly note error