keema
November 11, 2014, 2:10pm
99
voxframe:
I realize this is off topic… But Normis, please hear my thoughts.
This is crazy with the bugs being introduced. I too am experiencing random reboots on 1100 hardware, as well as CCR. No “custom” scripting or complicated configurations. No userman, no hotspot, etc.
I don’t have the time/ability to make supout files and send them and track progress etc.
There is a serious problem with your release methods for new firmware, and it needs to be addressed/organized better.
Right now it feels like your developers are guessing trying to patch bugs and release firmware in a hurry, and thus introducing more/bigger bugs. There needs to be a proper Alpha, Beta, Stable firmware flow, and right now there isn’t.
My advice
Introduce a PROPER firmware flow. ALPHA = v7 BETA = v6 STABLE =v5
Make ALPHA/BETA the same as Ubnt does. Only certain people who have accepted/approved can access the BETA files. Everyone else only sees STABLE.
NOTHING gets released to STABLE until completely cleared for at least a couple months.
This is a normal flow for any software company (That knows what they are doing anyway).
I don’t want CCR in my hands when it can only run BETA firmware!
I want you to MARK your new firmware as BETA, so people understand the most recent is NOT THE BEST!
This is very frustrating Normis, Mikrotik is the only company that does software development that I have ever seen work in such a backwards fashion. Again, even Ubnt can get this right. (And that is not a nice thing to say, because they can’t get a lot of things right)
Agreed 100%. Regarding supouts Normis. I cannot send it anymore as I have already downgraded my 1100AH2 to 6.20. Don’t you have a piece on stock where your testers can try? They should have done it before. I have no special config of this router.
What I’ve also noticed is that sometimes firewall src-nat masquerade rule is displayed as invalid and it doesn’t work. Disabling and enabling it a couple of times and it starts to work… :S When invalid I get this message:
— in/out interface matcher not possible when interface [pppoe-xxx-xxx] is slave - use master instead [eoip-xxx-xxx].
After a couple of disablings and enablings it stops being slave?!
http://forum.mikrotik.com/t/nat-masquerade-problem-in-6-20-1/82659/1
br,
keema