Good luck. All of these issues have been battles MT has faced for 5+ years. Their responses are open ended, shoulder shrugs, and a bunch of maybes. Don't get me wrong, I've got more than $400k tied up in MikroTik gear. I am in support of an independent Bug Tracker/Suggestion box...but I don't think that MT would really care or listen.
Regards, Chuck On Tue, May 17, 2011 at 11:55 AM, Andrew Cox <[email protected]> wrote: > Perhaps an invite-only system would be the way to go? > > Personally I feel the right thing to do here is give Mikrotik the suggestion > and opportunity to offer something, if they're not interested then go ahead; > I'd contribute. > > I've already approached and discussed the option of paid corporate support > with them (which they feel they can't justify at this time) however > a definitive listing of known issues (to avoid) and/or workarounds would be > invaluable in the absence of the other. > > Kind Regards, > > Andrew Cox > Senior Network Administrator > AccessPlus / BigAir Universe Broadband > www.accessplus.com.au | www.bigair.com.au > > > > On 18 May 2011 01:15, Jon Paul Kelley <[email protected]> wrote: > >> I agree. There is no sense in each one of us having to rediscover the >> wheel, if one of us already have discovered it. A bug tracker is the way to >> go. >> >> Great suggestion. >> >> >> >> On 5/17/2011 10:44 AM, Andrew Cox wrote: >> >>> Ahhhh so it's SNMP that's causing the crash. :-D >>> Makes sense now! >>> >>> But yes, I agree there's something that's needed. >>> I can understand that mikrotik may not want everyone to know about every >>> little bug that comes across their desk, that said.. we need to know what >>> the causes are so we can avoid them. >>> >>> Kind Regards, >>> >>> Andrew Cox >>> Senior Network Administrator >>> AccessPlus / BigAir Universe Broadband >>> www.accessplus.com.au | www.bigair.com.au >>> >>> >>> >>> On 17 May 2011 21:38, Jon Auer<[email protected]> wrote: >>> >>> Bugtracker++ >>>> With many bug trackers you can tag a problem as being specific to a >>>> version (or range of versions). That could be handy for finding >>>> versions that are workable. >>>> >>>> >>>> On Tue, May 17, 2011 at 2:35 AM, Tristram Cheer >>>> <[email protected]> wrote: >>>> >>>>> I'm not so sure, the forums are difficult in that they have a low SNR, A >>>>> >>>> bug >>>> >>>>> tracker is better suited to being able to confirm bugs (via submitted >>>>> exchanges with MT support confirming them) >>>>> >>>>> On 17 May 2011 18:31, Chupaka<[email protected]> wrote: >>>>> >>>>> I think, it should be either forum or wiki. Because in that place the >>>>>> >>>>> most >>>> >>>>> important thing will be accumulating information about known bugs in, >>>>>> mostly, previous versions - actual bugs of current version are easily >>>>>> available in recent official forum topics. >>>>>> >>>>>> >>>>>> 2011/5/17 Tristram Cheer<[email protected]> >>>>>> >>>>>> I think a real bug tracker would work the best to be honest >>>>>>> >>>>>>> On 17 May 2011 18:16, Butch Evans<[email protected]> wrote: >>>>>>> >>>>>>> On Tue, 2011-05-17 at 16:41 +1200, Tristram Cheer wrote: >>>>>>>> >>>>>>>>> So there's been a bit of talk on the forums recently about the >>>>>>>>> >>>>>>>> stablity >>>>>> >>>>>>> of >>>>>>>> >>>>>>>>> ROS 5 and as such the changelogs and known issues that MT don't >>>>>>>>> >>>>>>>> release. >>>>>>> >>>>>>>> When a client like ourselves identifies and issue like the SNMP >>>>>>>>> >>>>>>>> memory >>>>>> >>>>>>> leak >>>>>>>> >>>>>>>>> today MT don't let everyone know and as a result quite a few >>>>>>>>> >>>>>>>> people >>>> >>>>> are >>>>>> >>>>>>> left >>>>>>>> >>>>>>>>> with odd problems they can't explain (When was the last time you >>>>>>>>> >>>>>>>> thought >>>>>>> >>>>>>>> SNMP would be the cause of your major router crashing issue?) >>>>>>>>> >>>>>>>>> So an Idea, Just like we have this list for MT talk outside of >>>>>>>>> >>>>>>>> MT's >>>> >>>>> somewhat >>>>>>>> >>>>>>>>> twitchy delete finger forum why dont we start a bugtrack where >>>>>>>>> >>>>>>>> everyone >>>>>> >>>>>>> can >>>>>>>> >>>>>>>>> submit problems and update us with what support tells them etc >>>>>>>>> >>>>>>>> etc, >>>> >>>>> That >>>>>>> >>>>>>>> way >>>>>>>> >>>>>>>>> we would have a resource we could turn to for open issues before >>>>>>>>> >>>>>>>> we >>>> >>>>> start >>>>>>> >>>>>>>> down the path of contacting support? >>>>>>>>> >>>>>>>> Do you want a real bugtracker, a forum, a wiki or something else? >>>>>>>> >>>>>>> I'd >>>> >>>>> be happy to set up whatever you like. >>>>>>>> >>>>>>>> -- >>>>>>>> ******************************************************************** >>>>>>>> * Butch Evans * Professional Network Consultation* >>>>>>>> * http://www.butchevans.com/ * Network Engineering >>>>>>>> >>>>>>> * >>>> >>>>> * http://store.wispgear.net/ * Wired or Wireless Networks >>>>>>>> >>>>>>> * >>>> >>>>> * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! >>>>>>>> >>>>>>> * >>>> >>>>> * NOTE MY NEW NUMBER: 702-537-0979 * >>>>>>>> ******************************************************************** >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Mikrotik mailing list >>>>>>>> [email protected] >>>>>>>> http://www.butchevans.com/mailman/listinfo/mikrotik >>>>>>>> >>>>>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>>>>>> RouterOS >>>>>>>> >>>>>>>> -------------- next part -------------- >>>>>>> An HTML attachment was scrubbed... >>>>>>> URL:< >>>>>>> >>>>>>> >>>> http://www.butchevans.com/pipermail/mikrotik/attachments/20110517/f6aacd7c/attachment.html >>>> >>>>> _______________________________________________ >>>>>>> Mikrotik mailing list >>>>>>> [email protected] >>>>>>> http://www.butchevans.com/mailman/listinfo/mikrotik >>>>>>> >>>>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>>>>> RouterOS >>>>>>> >>>>>>> -------------- next part -------------- >>>>>> An HTML attachment was scrubbed... >>>>>> URL:< >>>>>> >>>>>> >>>> http://www.butchevans.com/pipermail/mikrotik/attachments/20110517/0d0d88e5/attachment.html >>>> >>>>> _______________________________________________ >>>>>> Mikrotik mailing list >>>>>> [email protected] >>>>>> http://www.butchevans.com/mailman/listinfo/mikrotik >>>>>> >>>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>>>> RouterOS >>>>>> >>>>>> -------------- next part -------------- >>>>> An HTML attachment was scrubbed... >>>>> URL:< >>>>> >>>> >>>> http://www.butchevans.com/pipermail/mikrotik/attachments/20110517/40aff1c1/attachment.html >>>> >>>>> _______________________________________________ >>>>> Mikrotik mailing list >>>>> [email protected] >>>>> http://www.butchevans.com/mailman/listinfo/mikrotik >>>>> >>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>>> >>>> RouterOS >>>> _______________________________________________ >>>> Mikrotik mailing list >>>> [email protected] >>>> http://www.butchevans.com/mailman/listinfo/mikrotik >>>> >>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>> RouterOS >>>> >>>> -------------- next part -------------- >>> An HTML attachment was scrubbed... >>> URL:< >>> http://www.butchevans.com/pipermail/mikrotik/attachments/20110518/944cb63e/attachment.html >>> > >>> >>> _______________________________________________ >>> Mikrotik mailing list >>> [email protected] >>> http://www.butchevans.com/mailman/listinfo/mikrotik >>> >>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>> RouterOS >>> >> >> _______________________________________________ >> Mikrotik mailing list >> [email protected] >> http://www.butchevans.com/mailman/listinfo/mikrotik >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> RouterOS >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://www.butchevans.com/pipermail/mikrotik/attachments/20110518/32652c42/attachment.html> > _______________________________________________ > Mikrotik mailing list > [email protected] > http://www.butchevans.com/mailman/listinfo/mikrotik > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS > _______________________________________________ Mikrotik mailing list [email protected] http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
