happened to me in beta of 5.18… and again in rc1 of 5.19… in a 435g
upgraded the firmware from 2.39 to 2.41 and later upgraded ros to 5.19 rc2 and its working…
had to netinstall back to 5.18 and upgrade firmware before going to 5.19 rc2
Honzam,
If you are using p2p bridge with NV2, then try these wireless settings:
Channel width - 20Mhz - IMO this setting is the most important for connection stability..
HT AMSDU Limit - 8192
HT AMSDU Threshold - 8192
HT AMPDU Priorities - 0,1,2,3,4,5,6,7
HT Guard Interval - any
Adaptive Noise Immunity - Select proper for ap/client Enabled NV2 Security
Lost my cert - and can’t import it again (Ticket#2012071166000339)
Upgrade to 5.15 - same issue
Upgrade to 5.16 - same issue
Upgrade to 5.17 - imported my cert
Because of my experiments I downgraded RB433UAH from 5.18 to 5.17, to not lose cert. In 5.17 ↔ 5.17 I noticed same jitter in SSTP and back to 5.18 on RB433UAH.
As result
RB1100AH - 5.17
RB433UAH - 5.18 - very unstable(Ticket#2012071766000542) - 5-7 reboots per day with 100%CPU load. I this it depends of traffic maybe, because night it alive. Uptime was 20-39 minutes. Sent ~ 10 supout.rif
Supout.rif file have no indications of any software related issues. Please, check
your power/grounding/ examine board for visual damage.
RB433UAH - 5.19 - very unstable.
Now
RB433UAH - found my config before downgrade(from ROS 5.18).
Restore my config on 5.19 and now uptime is 1d 18h
@Chupaka
Month ago Normis promised me (by mail) that MT will try to fix it.
This bug exists only for sub-menu pages, eg. System/Users,
but not for top-menu pages, eg. Queues.
For me it’s very useful to permanently hide some Webfig pages from end users.
We have upgrated to 5.19 and mikrotik doesnot came back.
see attached picture.
all our 1500 clients and bgp are down now.
I think Mikrotik must release more stable versions.
Thank you
I have RouterOS upgrade v.5.19 very not stable. ( RB411AH + R52HN )
after 4-5 hours of online suddenly becomes hangs.
power off-on the router normaly again.
previously using version 5:18 no problem.
what’s wrong …???
thank’s for solution.
What exactly hangs? Can you ping it - what do you see on the serial console if you have access to it?
Do you see a kernal panic - any autosupout.rif file generated?
router can’t ping. I can’t get access to the router. the only way is to turn off the power and turn it on again.
problem has been resolved after a downgrade to 5.18. Current router is working properly.
7h of works routerboard is up and working fine.
I have the same problem but on X86 machine, router can’t ping. I can’t get access to the router
the only way is to turn off the power and turn it on again,
I have only few packages: advanced-tools, dhcp, ntp, ppp, routing, seciurity, system.
this is not first time that mikrotikls distribute version with status/comment “stable” for version that give users a very serious errors with stability.. This policy is very disappointing
if ur trying on x86 maybe its unstable because its never tested on this pc but there is always support
5.17 and 5.18 are stable (except something wrong with nstreme since v5) but there are always bugs and there will be because
Mikrotik is always trying to import a new futures witch need time and money witch in some case is bad
like IP6, UBQ (airmax products) still don’t support IPV6
to the point I dont need to use IP6 protocol for P2P link just I need working nstreme or nv2 like in UBQ case Airmax
Upgraded to 5.19 on a RB750 , and have had it on multiple occasions had all the LED’s flash to green and just flat out will not respond until a power cycle.Unsure if it is hardware/software/firmware related.