hi all
we have a 1036 running 6.29.1 and we are not sure what the stable software/firmware for it is.
We tried a few releases a few months ago (6.3x) and it crashed our network instantly. We are not sure if it was the software or the FW that crashed them, but we downgraded back to 6.29.1
There are many new fixes out there, but we want to know, with certainty, what is the release we can use to date that will be stable for:
Vlans, DHCP, NAT, simply FW rules, etc.
issues we have on 6.29.1: random crash when connecting switch with a newly provisioned VLAN, new VLAN not routing till a power cycle
i see people mentioning NTP for some reason. We use it. it seems to work fine on 29.1
Are we good to auto upgrade? or upgrade in stages?
need some affirmation on what is a well tested version to ‘upgrade into’ (we hopefully dont need to reset the router to factory and re-script it)
Thanks!
We have 400+ day uptime on our CCR1036’s running 6.19
We are doing iBGP, eBGP, ospf, ldp, L3VPN, L2VPN, vlans, QinQ vlans and using the firewall/mangle functions.
So if you want stability, you should find it on 6.19
We are about to start testing 6.35 as we really want to implement romon and get some of the fastpath features on our production network.
So your saying I should downngrsde from 6.29.1 to 6.19?
Do you have any info on the 6.35 reliability?
I can’t find anywhere discussion on stable newer firmware from the 2016 bugfix releases.
I’m saying 6.19 has been super stable for us and we use quite a lot of features. YMMV…
I do not have reliability info on 6.35 yet. We usually test for 3 months before we move a release on to our production network.
Do you know a thread dedicated to 1036 stability?
Is it possible Mk just keeps breaking their flagship router on every release?
The last one we tried turned all ports into hub ports and all data flooded to all ports.
The router is not new but is still in beta
The old firmware gave us negotiation trouble on our sfp so we had to go up to 29.1
I think you are best to email support@mikrotik.com with your problems.
Even on newer releases we have not seen the problems you are describing.
They are pretty slow on complex things and will ask us to test it and supout
No way we can do that on our production gear
It could have been a bad revision that got sorted. I think it was 6.30.x