{"id":1326,"date":"2016-07-09T17:53:28","date_gmt":"2016-07-09T17:53:28","guid":{"rendered":"http:\/\/www.mtin.net\/blog\/?p=1326"},"modified":"2016-07-09T17:58:10","modified_gmt":"2016-07-09T17:58:10","slug":"an-open-letter-to-mikrotik-about-bug-fixes","status":"publish","type":"post","link":"https:\/\/www.mtin.net\/blog\/an-open-letter-to-mikrotik-about-bug-fixes\/","title":{"rendered":"An open letter to Mikrotik about bug fixes"},"content":{"rendered":"

This isn’t your typical “rag on Mikrotik” post. \u00a0I see some frustrations with the Mikrotik process, mainly in regards to getting ongoing bugs and issues fixed. Having a persistent bug continue for large amounts of times tends to make for a frustrating experience. \u00a0Mikrotik has made leaps and bounds in their Changelogs over the past couple of years, which has been a huge help in the decisions of what software versions to upgrade (or even downgrade) to. \u00a0But I think things get lost in the process. This results in ongoing bugs, which tend to get unburied if someone makes enough noise.<\/p>\n

One of the biggest things I would like to see is a public bug tracking system like Redhat’s Bugzilla tracking<\/a> system. \u00a0This would benefit the community as a whole and help users see some of the outstanding issues when they go to implement things. \u00a0Forums are a great tool, but due to the nature of them, you get a fair amount of mis-information and unrelated chatter. \u00a0Just because Joe says he is seeing a bug, doesn’t mean he has a confirmed bug. \u00a0Having a confirmed bug system that has information and able to have moderated comments would be beneficial in many ways:
\n1.Users with long term bugs they are experiencing or waiting on would be able to keep informed on open status of bugs.
\n2.Would cut down on the “non-scientific” nature of forums. Information could be specifically submitted in support of a confirmed bug. Bug reports normally include the conditions that need to be met or existing for the bug to manifest itself. Users can then confirm, under those specific\u00a0conditions, if they are experiencing a certain bug.
\n3.Bugs that are important to users will get reported more often. This should lead to the more important bugs being upvoted by the community thus getting them fixed earlier. If your particular bug has low numbers you have a reference as to why it’s not being addressed in a timely manner. Companies have to give resources to places they get the most bang for the buck.<\/p>\n

Not only would this keep Mikrotik accountable, but it would keep the community accountable. \u00a0Properly reporting bugs and reproducing them is a process. It takes effort on both the user and the developer. In the end, it makes for a better product.<\/p>\n

I have the utmost respect for Mikrotik and their staff. \u00a0Several folks there I consider friends. I think, before growing pains get too out of hand some sort of additional feedback options would be helpful for the community at large. Mikrotik is getting there. Things like making bug fix versions and release-candidate versions available, along with changelogs has been a huge help for planning and just keeping up on what’s being addressed.<\/p>\n

What prompted this was I had a client over the past weekend who started having OSPF issues. Many hours of troubleshooting later, and only talking to some other folks who were seeing the same issues, I was\u00a0able to determine a specific RouterOS version was to blame. \u00a0Being able to attach data to a specific bug report, or having Mirkotik open up a new bug based on information I submitted would have been a great help to others. \u00a0A forum of blog post would have been too general. Forums posts also tend to bring out the “I am seeing that too” and they are not meeting the same conditions you are.<\/p>\n

Mikrotik implement a bug tracking system! Bugzilla is even on GitHub.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

This isn’t your typical “rag on Mikrotik” post. \u00a0I see some frustrations with the Mikrotik process, mainly in regards to getting ongoing bugs and issues fixed. Having a persistent bug continue for large amounts of times tends to make for a frustrating experience. \u00a0Mikrotik has made leaps and bounds in their Changelogs over the past […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[24],"tags":[346,345,25,28,122,233],"jetpack_publicize_connections":[],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p6VLMf-lo","jetpack-related-posts":[{"id":1951,"url":"https:\/\/www.mtin.net\/blog\/interesting-mikrotik-gui-behavior\/","url_meta":{"origin":1326,"position":0},"title":"Interesting Mikrotik GUI behavior","author":"j2sw","date":"December 28, 2017","format":false,"excerpt":"While bringing up a BGP session for a client I kept trying to add our side of a \/126.\u00a0 It kept reverting to the network address.\u00a0 The video shows what happens when I tried to add ::12\/126 to the IPV6 addresses. After some second-guessing and then some Facebook chatting I\u2026","rel":"","context":"In \"bug\"","block_context":{"text":"bug","link":"https:\/\/www.mtin.net\/blog\/tag\/bug\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.mtin.net\/blog\/wp-content\/uploads\/2017\/12\/Screen-Shot-2017-12-27-at-11.09.42-PM-3.png?fit=550%2C388&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":2554,"url":"https:\/\/www.mtin.net\/blog\/common-questions-masquerade-vs-src-nat-action-mikrotik\/","url_meta":{"origin":1326,"position":1},"title":"Common Questions: masquerade vs src-nat action Mikrotik","author":"j2sw","date":"October 26, 2018","format":false,"excerpt":"One of the common questions I get is what is the difference between Masquerade and SRC-NAt? Which should I use? The quick answer is to use SRC-NAT if your gateway IP is static, and use masquerade if it can change. The Mikrotik Wiki Entry Firewall NAT action=masquerade is unique subversion\u2026","rel":"","context":"In "Mikrotik"","block_context":{"text":"Mikrotik","link":"https:\/\/www.mtin.net\/blog\/category\/mikrotik\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.mtin.net\/blog\/wp-content\/uploads\/2014\/09\/2014-08-05-19.26.03.png?fit=650%2C650&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":263,"url":"https:\/\/www.mtin.net\/blog\/new-software-features\/","url_meta":{"origin":1326,"position":2},"title":"New Software Features","author":"j2sw","date":"April 23, 2015","format":false,"excerpt":"RoMON another blog post will follow on this. Need to use Winbox 3 FastTrack FastPath + Connection Tracking FastTrack Accelerates packet processing for specific connection tracking entries Full NAT support Works with IPv4\/TCP and IPv4\/UDP \u00a0","rel":"","context":"In "Mikrotik"","block_context":{"text":"Mikrotik","link":"https:\/\/www.mtin.net\/blog\/category\/mikrotik\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":76,"url":"https:\/\/www.mtin.net\/blog\/mikrotik-6-16-and-6-17-released\/","url_meta":{"origin":1326,"position":3},"title":"Mikrotik 6.16 and 6.17 Released","author":"j2sw","date":"July 20, 2014","format":false,"excerpt":"From the ChangeLogs What's new in 6.17 (2014-Jul-18 15:14): *) CCR1009 - fixed crash, only affects CCR1009; What's new in 6.16 (2014-Jul-17 13:12): *) 802.11ac support added in wireless-fp package for QCA9880\/9882 rev2 (-BR4A) chips; *) ip cloud now allows to set which IP to use - detected (public) or\u2026","rel":"","context":"In "Mikrotik"","block_context":{"text":"Mikrotik","link":"https:\/\/www.mtin.net\/blog\/category\/mikrotik\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":64,"url":"https:\/\/www.mtin.net\/blog\/router-os-6-15-released\/","url_meta":{"origin":1326,"position":4},"title":"Router OS 6.15 Released","author":"j2sw","date":"June 12, 2014","format":false,"excerpt":"Big bug fix if you are upgrading from V5.x What's new in 6.15 (2014-Jun-12 12:25): *) fixed upgrade from v5 - on first boot all the optional packages were disabled; *) fixed problem where sntp server could not be specified in winbox & webfig; *) metarouter - make openwrt work\u2026","rel":"","context":"In "Mikrotik"","block_context":{"text":"Mikrotik","link":"https:\/\/www.mtin.net\/blog\/category\/mikrotik\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2152,"url":"https:\/\/www.mtin.net\/blog\/mikrotik-and-3cx-phone-system\/","url_meta":{"origin":1326,"position":5},"title":"Mikrotik and 3CX phone system","author":"j2sw","date":"March 20, 2018","format":false,"excerpt":"I have had this bookmarked for awhile.\u00a0 It helped out today so I figured I would share it. Applies to other phone systems doing HTTP\u00a0configs. http:\/\/developers-club.com\/posts\/257643\/","rel":"","context":"In "Mikrotik"","block_context":{"text":"Mikrotik","link":"https:\/\/www.mtin.net\/blog\/category\/mikrotik\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.mtin.net\/blog\/wp-content\/uploads\/2017\/01\/ethernet.jpeg?fit=1200%2C775&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.mtin.net\/blog\/wp-content\/uploads\/2017\/01\/ethernet.jpeg?fit=1200%2C775&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.mtin.net\/blog\/wp-content\/uploads\/2017\/01\/ethernet.jpeg?fit=1200%2C775&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/www.mtin.net\/blog\/wp-content\/uploads\/2017\/01\/ethernet.jpeg?fit=1200%2C775&ssl=1&resize=1050%2C600 3x"},"classes":[]}],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/posts\/1326"}],"collection":[{"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/comments?post=1326"}],"version-history":[{"count":2,"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/posts\/1326\/revisions"}],"predecessor-version":[{"id":1328,"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/posts\/1326\/revisions\/1328"}],"wp:attachment":[{"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/media?parent=1326"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/categories?post=1326"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mtin.net\/blog\/wp-json\/wp\/v2\/tags?post=1326"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}