The newsletter is here! Many new features and a new product!

- CAPsMAN full support release
- New MUM events
- RJ45 SFP
- Nv2 latency improvements
- Metal 9HPn
- New Cloud features
- RB953GS-5HnT
- CRS226-24G-2S+RM

View the PDF here: http://download2.mikrotik.com/news/mikr ... UN2014.pdf

Just a quick question, because it is not mentioned in the changelog.
The new auto option for tdma period size is included in both v6.14 and v6.15, but the newsletter specifically mentions the latency improvement as a v6.15 feature. Do I need to upgrade what I've currently upgraded to v6.14 ?

v6.14 had some critical upgrade bugs, so we quickly pulled it, and replaced with new v6.15. Essentially the versions are identical, only v6.15 fixes this upgrade bug, and an NTP bug.

You mention that to get the new driver you need to click “Enable CAPsMAN” in quickset.

quickset scares me. Is there another way to do it? Just enable the wireless-fp in packages?

You mention that to get the new driver you need to click “Enable CAPsMAN” in quickset.

quickset scares me. Is there another way to do it? Just enable the wireless-fp in packages?

yes, it does the same

I can't find the cloud services

Is mAP-2n delayed or cancelled?
I have seen it's photos on February and it is not available yet? I am very happy with CAPsMAN and I want to sell it to my clients with mAPs. When will it be available?

normis, does the company plan to release Mikrotik wireless solutions in the range of 6 GHz?

Normis, tests with wireless-fp in PDF brochure are on P2P link.
In multipoint is necessary upgrade AP and all clients to wireless-fp? Or just AP side?
If is necessary upgrade all clients, what about old clients which don´t support 6.x?

Due the lack of plain wording info;

If you don't want CAPsMAN, but yes you do want the new wireless improvements;

It is enough to just upload and/or enable the wireless-fp package?
You can leave all your pre-wireless-fp radio settings as they are?
Is it already working if loaded on the AP only?
Is it working if loaded on the CPE only?
Does it have to be installed on both AP and CPE?

New wireless package is about new drivers... is it not enough to just make sure you have last firmware upgrade?

Apart from the fact I have not seen a lot of 'in the field' results about the improvements, it would be nice to see or hear more from MT about the improvements in the new wireless-fp.

The test results of the newsletter bear not any facts because there is no comparison with same test setup for normal wireless package.
Its like stating my new car's tires are performing better in the rain and show a test in wet weather I can make the roundabout with 30 km/hour.... Is this good? Or is it moderate? I have no clue.....

WirelessRudy, CAPsMAN is a part of the Wireless-FP package. Can't get them separately. You do need to enable this package, but you will also get CAPsMAN.

it is enough just to enable the package and skip all the CAP stuff and run your wireless as you are used to.

Where is "Wireless-FP package" ? I have downloaded "all-packages" 6.15 and there is no that package.

Where is "Wireless-FP package" ? I have downloaded "all-packages" 6.15 and there is no that package.

Install using RouterOS big package, it is in there by default.

1) I have installed and working 6.15 at RouterBoard, so I want only add that ONE package (Wireless-FP)
2) Why i have to install "big" RouterOS package with all (unneeded) packages? I don't need them all, so I am installing only needed packages. What for all?!
3) WHY there is no separate Wireless-FP package at "all-packages" zip RouterOS file? Any reason or mistake?

Normis, tests with wireless-fp in PDF brochure are on P2P link.
In multipoint is necessary upgrade AP and all clients to wireless-fp? Or just AP side?
If is necessary upgrade all clients, what about old clients which don´t support 6.x?

Hello all,
I would also like to know answer to this question.

Thank you
Miroslav

Yes, the FP package is needed on all devices, if you want to see the latency improvement. The settings are only needed on the AP side.

Heya Normis; i have a 6km link now upgraded to the FP package - i didn't see any improvement to latency, but did for throughput (latency is a solid 2/3ms with TDMA Period Size 1 Distance 10km).

Is there anything else i need to do to achieve lower latency?

Yes, the FP package is needed on all devices, if you want to see the latency improvement. The settings are only needed on the AP side.

Thank you for your fast answer.
What settings on AP side do you mean?

Sorry - TDMA = Auto. I see.

Miroslav

Normis, please answer for ALL my THREE questions. Could You, please?

2. next version will include this package also in the ZIP file
3. next version will include this package also in the ZIP file

Normis, please answer for ALL my THREE questions. Could You, please?

You can download it separately. It is on download page: http://download2.mikrotik.com/routeros/ ... mipsbe.npk

Normis, in wireless-fp is still minimal cell radius 10km. Have you plan add smaller value?
A lot of P2P links is 1 - 5km

Normis, in wireless-fp is still minimal cell radius 10km. Have you plan add smaller value?
A lot of P2P links is 1 - 5km

This value has no effect for smaller cells, so there is no use in specifying small values.

I tried two P2P with SXT bridge (Nstreme). These lines were working well for months.
After upgrade to FP package both lines started disconnect every 30 sec. Signal 65/65, CCQ over 90%.

It seems FP package has big problem with Nstreme, because after disabling Nstreme lines are OK again.

Miroslav

I tried two P2P with SXT bridge (Nstreme). These lines were working well for months.
After upgrade to FP package both lines started disconnect every 30 sec. Signal 65/65, CCQ over 90%.

It seems FP package has big problem with Nstreme, because after disabling Nstreme lines are OK again.

Miroslav

enable debug logs and make supout.rif files, we can check why this happened. did you use v6.15 before? maybe the difference is not in the FP package, but RouterOS version in general?

I tried two P2P with SXT bridge (Nstreme). These lines were working well for months.
After upgrade to FP package both lines started disconnect every 30 sec. Signal 65/65, CCQ over 90%.

It seems FP package has big problem with Nstreme, because after disabling Nstreme lines are OK again.

Miroslav

enable debug logs and make supout.rif files, we can check why this happened. did you use v6.15 before? maybe the difference is not in the FP package, but RouterOS version in general?

I used v6.13 before.

Here are supout.rif and setting export file.
I did this first time, so let me know in case there is something wrong or missing.
Miroslav

My experience wit FP package (beside troubles with Nstreme):
I upgraded about 8 clients (411, 711, Sextant) - all OK.
I upgraded 6 SXTs (P2P bridge) - one of them didn't reboot (reboot infinitely again and again) after installing FP package. Only downgrade to 6.13 helped.
I upgraded one Grove (AP) - same as bad SXT - only downgrade helped.

It seems FP package is not ready yet.
What is your experiece?

Miroslav

I would like to understand what happens if I enable wireless-fp on the AP but not on the customers' RB... Does it work? Does it have issue or simply users won't get improvements?

No changes for clients that are using a standard wireless package.

Are you sure? I saw ping improvements...

wireless-fp is awesome!

NV2 latency has dropped from a very jittery pattern of 2ms, 5ms, 20ms, 2ms, 5ms, 35ms to a nice and stable 2ms. On top of this it seems to have better throughput when using WDS.

These last posts exactly show how statements on this forum should be taken.
One says it improves, where the other (MT) states it can't be in that specific situation, and then another uses wordings like 'it seems'..

The only way to make a statement if something is really improved (or worsened) is by giving the full details and characteristics of the link of subject and the exact changes made and how.

So, make of antenna.
Wireless parameters, before and after the change
Traffic parameters, before and after the change
How and when the results of a change are really measured.

Just throwing some statements like "it seem to have improved", my "signals are better", or "jitter seems to be less" makes not a lot of sense if we don't know if the underlying link characteristics not also have seen changed. Or, is the traffic flow and adjacent radio spectrum still the same?

All my links fluctuate at times. Due changing circumstances in the propagation or just the traffic. So, WITHOUT changing the software or its versions...... How do I now know a certain claimed software improvement is really true or not just the result of some other data changing???

Even MT's statements sometimes go wrong because real live working radio links in outdoor heavy usage spectrum environments might behave quite different to lab situations, or even between geographical areas.

The only way to make a statement if something is really improved (or worsened) is by giving the full details and characteristics of the link of subject and the exact changes made and how.

I was not trying to make a statement, just sharing my experience.

We have tested on a couple of less critical links,
- RB911+StationBox point to point link over 3km
- Omnitik to Omnitik bridge between a portacom and main office, txpower set to 10dBm
- RB800+JRC24DUPLEX point to point over 5km, txpower set to 9dBm

All links had improved jitter. We only tested throughput on the Omnitik bridge setup and it was improved over previous results, going from ~30mbit UDP to ~50mbit UDP.
Completely non-scientific, but hey we saw improvements.

YMMV....

I was not trying to make a statement, just sharing my experience.

Yes I know, I wasn't criticising you. I should have used different wordings, like; "making remarks".
I merely used your remark as example.

But yes, you gave more info now which gives me more confidence indeed somethings improved. If I now find more others in the forum sharing similar kind of experiences it gives me (us readers) even more confidence.

2. next version will include this package also in the ZIP file
3. next version will include this package also in the ZIP file

THERE IS new version, but THERES IS NO wireless-fp package inside "all-files" ZIP package!!! Why?!