v4.16 released

Yes . since a long time ago . first i thought it is a problem in pppoe but mikrotik support said the problem was routing crash .
i have sent more than 30 supouts to them with different versions.

It’s bad becouse U and I have a problem, but it’s good becouse we’re not alone with that problem. I hope it get fixed someday.

I would like to ask if the 100% cpu issue is fixed in 4.16.
I have that problem in 433ah with v4.1 every 5 days.

My guess is that it is just a bug on the display and not actuall situation of 100% cpu usage since I don’t get any lags, I connect to winbox and I change everything fast, etc.

What do you sugest?Upgrading or is it safe for my equipment to stay in v4.1?

Do you run ospf in this routerboard?

No.I think (from the things I have read here) that routing crashes.As I don’t use routing this doesn’t affect the performance but it does effect the display of cpu usage.
PS: I updated yesterday a 433UAH from v3 to v4.16. No problems at all loosing the license.Waiting 5 days to see if the 100% cpu is still present.I will let you know.

What version are you using currently? We and a few others have had routing crash’s until it was fixed in 4.13

I have sent another autosupout about routing crash in 4.16 to mikrotik support . no progress

we’re using 4.13 on 450G’s and rc5.05 on our two x86 core routers.

we’re using 4.13 on 450G’s and rc5.05 on our two x86 core routers.

if you are using such old version, why are you reporting about crashes in v4.16?

its quite simple Normis. Becouse other users are still having the same problem, and most important, since 4.13 till 4.16 there’s no changelog about the routing crash. We have a quite large network with more than 30 points of presences and we cant update every day. Here we love mikrotik, and i changed my boss mind about cisco and juniper to put mikrotik here. but these routing crashed in our fully routed network is causing a lot of SLA problems. The Rc5 version crashed but restarts the routing proccess and we lost all our 8 ebgp sessions and our internet connectivity for about 2 minutes, and our pops running 4.13 get something like a proccess loop 100% cpu routing crash and we have to manualy reboot the router during the day.

can u assure that routing crash have been nailed down and fixed in 4.16? if yes i will update tonight. but i dont think so becouse other users reports about routing crash.

which other users? routing crash was fixed after v4.13, as the “other user” beccara confirmed. I know of no routing crashes, and we have no such reports in support.

OK gonna try the newer one but if you read the beccara post, u will see that his statement is about its have been fixed for him since 4.13 not after 4.13 and here 4.13 still crashes.

About the crashes u can talk with Maris, about the ticket #2010120266000564.

Thanks! I hope the newer 4.16 fixes the crashes!

THANKS
I did upgrade from 4.11 to 4.16 for 433ah
noticed
low performance with xr 2 and xr 5 wireless cards
diffuculties with connections for clients and PTP
with same sitting as before for 4.11
noticed that after upgraded to firmware 2.29
any suggestions

Sorry ill be very clear, we had routing crashs from a ospf/bgp setup we put in on ros 4.6 it was fixed for us in 4.13 for us, if you are having crashs with 4.13 it must be from another bug

We send a supout about routing crashing on an RB1100 on 12/26.

[Ticket#2010122666000055] RE: Router Stops Passing Traffic

Normis we also are having problems with ospf . We simply disabled it and are no longer using it.

please send supout.rif files to support, we have no other reports like this, maybe it’s an isolated situation or specific configuration

i use ospf since 4.13, but my setup is very simple.I have 7 x86 mt routers connected to switch and they exchanges routers via ospf without any problem.uptime from 3d to 15d. Just my 2 cents

Hey Normis,
v4.16 NV2 works great but the 2.4 side has to be dialed back to straight B to not have extreme latency. Any ideas?
On straight AP boards - 2 XR2s and RB433 - had to turn off NV2 wireless in packages and activate the normal wireless. Even then the straight B has to be used.

v3.30 has not had these issues.

What would you recommend?

Thank you,
Rod

Here is a link to more comments in the forms that I made.
http://forum.mikrotik.com/t/need-config-for-p-to-mp-backhaul-for-nv2/43438/1

4.16 cannot configure tx-power?

it always set to default if I set to 30db it shows 19db (default)

I think 4.16 mipsle wireless and wireless-nv2 broken…
established wireless link but cannot ping!