RouterOS 4.17
*) wireless-nv2 package now includes the same fixes as RouterOS v5rc11;
where is 5.0rc11?
in our testing systems
so how can we realise what’s changed in 4.17 nv2 as 5rc11 changelog is not published
anywhere??
you misread that. it means all changes until rc11. not only what’s in rc11, but also rc1-rc10
ie. wireless-nv2 package in v4.17 is now the same as wireless package in v5rc11
I agree, its misleading.
What did I misread???
4.17 now includes the same fixes as RouterOS v5rc11
so I’m asking what’s fixed in 5rc11 ??
I’m aware that 4.16 was somehow equal to 5.0rc8 because i see that 5.rc9
was a step forward prior to 4.16/Rc8 considering nv2.
I was using ros4.3@802.11n and this was most stable implementation for ptp links,
since i tried to upgrade links with 4.13, 4.16 and finally 5.0rc9/10
i notice disconnection strange behaviour and more and more problems.
for example, link that was stable for about Year after upgrade to 5.rc9 both sides,
started to drop connection every 5-10-15 minutes, after playing with every possible
parameters with no result I decided to switch ap to station and station to ap, and gues what…
now link disconnects every few hours.
how long it’ll take to make mtik wireless reliable and stable as for example ubnt/airmax…?
Normis, misreading or not, even here you state “all changes until rc11…”. In most readers perceptions this means that the changes embedded in v5rc11 are included in v4.17
So now we want to know what these are…
We also know that v5rc11 is already given out to some forum users to fix some of their problems. So users that at present have problems (like me) with either v4.16NV2 or v5rc10 are really anxious to see what is changed in v5rc11, and thus v4.17NV2, so we can decide if this new version is going to be of any help here…
So please don’t accuse readers of ´misreading´ if your own wordings are clearly confusing… 
What’s new in 5.0rc11 (2011-Mar-02 10:20):
*) wireless nv2 - fixed RB532 freeze;
*) wireless - fixed station-bridge mode;
(among other things not mentioned here)
Ok, “fixed RB532” freeze. Is the architecture of RB532 comparable to rb333? When I implement v5.0rc10 on rb333 it makes two client rb433AH’s completely freeze up. (NV2 links).
I don’t want to try to upgrade rb333 again with 5rc11 since it cost me two days to rebuild two towers after that…
What are the “(among other things not mentioned here)” items. Why can’t they be mentioned?
If you state something like this than don’t be surpriced we want to know! 
version is not ready yet, changelog is not ready yet, wait until it’s released.
no, RB333 (PPC) and RB532 (MIPS-LE) are different
Ok, thanks for the response.
Am eagerly waiting now for the 5rc11 change-log..
normis,
Did routing process issue had been detected and fixed? i gave access to all my routers to mikrotiks support, and i have no signal from Maris for a couple days. i hope they managed to find that issue.
Not yet, we are working on it!
Thanks mrz! and mikrotik team for all the support on this issue!
need Function for radio parameters “is necessary to apply for 5 minutes”
4.17:
fixed RB1100 ether11,12,13 and RB800 ether3 resetting problem;
We have this problem in 5rc10 on RB1100 as well. It happens when we mark packets in “/ip firewall mangle”:
jan/02 01:01:31 interface,info ether12 link down
jan/02 01:01:34 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:02:14 interface,info ether12 link down
jan/02 01:02:18 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:02:54 interface,info ether12 link down
jan/02 01:02:58 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:03:59 interface,info ether12 link down
jan/02 01:04:03 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:04:18 interface,info ether12 link down
jan/02 01:04:21 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:04:37 interface,info ether12 link down
jan/02 01:04:41 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:04:52 interface,info ether12 link down
jan/02 01:04:56 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:05:11 interface,info ether12 link down
jan/02 01:05:14 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:05:25 interface,info ether12 link down
jan/02 01:05:29 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:05:45 interface,info ether12 link down
jan/02 01:05:49 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:06:04 interface,info ether12 link down
jan/02 01:06:07 interface,info ether12 link up (speed 1000M, full duplex)
jan/02 01:06:23 interface,info ether12 link down
jan/02 01:06:26 interface,info ether12 link up (speed 1000M, full duplex)
Is this gonna be fixed in 5rc11 as well? Is it possible to send me a pre-version? It’s an annoying problem, I cannot activate my QoS-Setup with this bug.
thanks
Oliver
Bad work of the report nv2 wds distance of 45 km a frequent dying down of the traffic and throughput falling
Till 12 o’clock nv2 after 12 nstreme
rb800 5rc10
Yes, it will be fixed in 5.0rc11 as well.
please contact support about both issues.
When the wireless is using 100% usage - try to make the support output file as that autosuppout file is corrupted.