Do you think it would be possible to maybe stop entirely what you folks are doing in terms of advancing ROS with new features etc... I think the most at this point that ROS users wish for in 2012, is that all resources in MT engineering solve the current problems that ROS has been having since the introduction of 5.xx .
Port flapping - This has NEVER been fixed..! Attempts at masking the problem, but MT cant even recreate it, thus they cant fix it. But we are several with the issue since who knows when.
Ethernet ports locking up - Never been fixed or acknowledged as a problem just like the port flapping. Recent RB 411,433,435,493 board are locking up on ethernet ports. In the early 5.xx releases, it seemed to only affect ethernet port 2, but the issue affects all ports and even when downgrading there are still lockups.
Ethernet port mismatch - 5.xx. In my case, I can rarely get ethernet ports to match up. Either one is in full, other auto, or vice versa, they always report the wrong info.. If I do get 2 boards on the same settings, then there is major packet loss.. The only way there is no packet loss is when one is on auto and other with no auto. Combination's like that, but never works when set as suppose to with above mentioned boards.
Its obvious that the major issues that are bringing my company down in stability and customers, is 5.xx. I have a few hundred RB's in service and my network was stable as a rock with first Gen 133's and 433's with 3.xx, precisly 3.30. Went 2 full years without a software related issue. 4.17 was not bad accept that power/signal levels were down compared to 3.30 and some links were not as stable, therefore they got turned back to 3.30. I have some critical RB's that could really use 5.xx tdma, but I couldnt DARE upgrade them or touch them.. Im wayyy 2 scared. Bench testing means nothing as most of these port related issues happen only with some good traffic.
My company has gone from the most stable wireless network most ppl have ever seen and they cant beleive its wireless... Too, the most unreliable wireless network they have ever seen... Customers dropping like flies, ppl getting second connections, VoIP going to other providers and ifcourse, loss in revenue... I just cant understand why MT cant test there software and release it only when its actually stable. Like STABLE!!.
In my short experience with MT, I can only say that there are 2 versions that are actually stable. Well 2 and a half. 2.95, 3.30 and 80% 4.17.
There are issues in these newer RB ports that werent there in the past. Even new boards running 3.30 are having these ethernet port issues.. There has to be something that changed in hardware or code for ethernet ports since the days of 3.xx and 2.xx. Please go back to that hardware and or code.. PLEASE... Im not even ranting here. Im expressing my sincere disappointment in ROS since 5.xx. If I would have know that my network would go from yeahh to neahh in less than a year due to ROS, I would never have built the network based on MT.
MT has great vision, great features, the best in my opinion.. But they in my opinion are going downhill. If a company cant release software that is stable in ALL circomstances, than whats the point.. If you folks cant test your SW enough before releasing it as stable, then dont release.. If you want to continue to release SW and rely on the community to test it and report bugs, then release as beta!..
Tell me ONE release that you have made in the last 2 years that hasnt had a medium to major bug in it.?? Every single release has an issue.. I understand that it cant always be perfect, but why is it other companies can release software with a hell of alot less bugs than MT? Since 5.xx were talking serious issues here, the damn ports dont pass any traffic.! Like thats major.! loll
If I were the CEO of MT. I would be embarrased that we couldnt find the issue. I would stop all other development and focus on resolving this issue and only this issue.! Whats the point in developing further if theres always a hidden major bug that is following each release.! You folks should also quit telling ppl to submit tickets when its issues that have clearly already been submitted.. You folks always say the forum is not for official support so we shouldnt rely on it and submit a ticket with file. Fine, thats how bugs are found, but you folks also should not rely on community members for testing your releases when they are depending on your product for the food on there table. Thats your responsibility to test, test, test and re test., Or atleast release as beta, then ppl like me cant complain.
Im having so many port related issues and my network is so un reliable now, that when im down, my customers dont even call anymore. They just sit there and hope its not too long, or they just leave all together like they have been doing.
DO you folks not feel embarrassed at all??
I personnel could not sleep at night knowing that ppl are having serious issues with your product and you cant even find the problem.. PPl are depending and paying you. You folks just hope the problem goes away, or just that ppl affected just get tired of repeating themselves. You are willing to let those ppl go and hope that the ppl not having issues continue to buy your products. The problem is, that eventually, they will have the same issues also if not fixed.
To my knowledge, there has never been a specific comment on what they think the problem is in regards to port flapping or freezes. Do you folks even have an idea? Or you think there is no problem? I cant understand how a group of extremely intelligent ppl that have developed some great stuff in the past cant figure this one out... These issues will effectively ruin your rep and sales. Some of us have to convince ourselves not to move our entire network to UBNT. I even trying to acquire licenses and 10k equipment to replace MT.. But I love MT.! But since 5.xx, it SUCKS HARD!
Im sure if the entire team actual took our problems seriously, it would be resolved 100% in a matter of days.
Ifcourse I will get deleted again.! WIll I have to resort to signing up again with different usernames and or IPs to get this message across to the roght ppl?.. I hope not. Cause I LOVE MT.. But this cant go on.! IT CANT.
TEST AND FIX YOUR ISSUES REGARDING ETHERNET PORTS. Ifcourse theres now the kernal failure issues...
I give up...
AM I the only one this frustrated at MT? This post is only to hopefully motivate the team in fixing thiese important issues and no more.. I dont want war here, I dont want excuses, I dont want to be deleted. I just want MT to work like it use too. You know, when you could impress 20 year engineers with your products and its flexibilty and reliability..
AM I asking too much?