v6.35rc [release candidate] is released, new wireless package!

[WirelessRudy]

@gius64

@taduikis

@jarda

ok, mikrotik thinks it will rise sales on consumer market, so that is it.

I know what would not as much rise but prevent from falling: improvement of current and future WiFi software or hardware. It becomes uncompetitive with todays user demand and trends and there’s already a list of inventions made. Because currently 4g lte provides numbers which majority of users only care of, and they even justify unresponsiveness, high lag and other related problems.. We desperately need to increase sector capacity, since currently I don’t get more than 30M total with 20-30 clients connected. And whats worse, I can’t even experiment and seek for best config, they feel shortages of service and immediately start looking who to kill. And I’m not joking, even at 4-5 AM there’s no total freedom for that recently.

I understand that with overcrowded 5GHz there’s no chance to get what you could with multi-band licensed freq and insane tx powers, but based on what 11n/ac competitors offer, it’s certainly not impossible to at least double the mentioned figure, which would be a life saver. For a while.

I might be naive, but I really hope something new and revolutionary might appear with these new wireless-smth packages every time they are introduced. Heck, I’d at least take changelog entries like “improved nv2 performance”

I’m with you I really hope MikroTik will introduce something new on wireless for point to multipoint!

And here’s another one…

[soulflyhigh]

@strods

Version 6.35rc2 has been released.

Changes since 6.35rc1:
*) chr - fixed high rate limitation;
*) ippool6 - fix potential crash;
*) routing - fixed rare kernel failure on different dynamic routing configurations;
*) wireless-rep - fix nv2 protocol.

• nv2 protocol seems to work now (clients can connect now at AP with nv2 - mipsbe rep 6.35rc2)

• background scan doesn’t work yet (tested on QRT-5), the same “state(6)” message appears… can anyone confirm that this feature works at all and show us some working example of it?

[ivicask]

@soulflyhigh

@strods

Version 6.35rc2 has been released.

Changes since 6.35rc1:
*) chr - fixed high rate limitation;
*) ippool6 - fix potential crash;
*) routing - fixed rare kernel failure on different dynamic routing configurations;
*) wireless-rep - fix nv2 protocol.

• nv2 protocol seems to work now (clients can connect now at AP with nv2 - mipsbe rep 6.35rc2)

• background scan doesn’t work yet (tested on QRT-5), the same “state(6)” message appears… can anyone confirm that this feature works at all and show us some working example of it?

Background scan worked since first version for me, simple tick background scan option, my clients didint lost connection, and my AP showed other WIFI networks in range, if thats whats not working for you.

[soulflyhigh]

@ ivicask
Yes, that doesn’t work for me on two different AP…
1st step - open wlan and click “Scan…” button (i’ve tried it on QRT-5 and RB433AH with UB5 wlan card)
2nd step - “regular” scan runs automatically and all clients loose connection to AP
3rd step - I stop scan by clicking on “Stop” button and tick “background scan” option
4th step - Then I click on “Scan” button in “Scanner” window and I’m always getting that “Couldn’t start-background scan not supported in this state(6)” error message no matter what I do… any ideas?

[ivicask]

@soulflyhigh

@ ivicask
Yes, that doesn’t work for me on two different AP…
1st step - open wlan and click “Scan…” button (i’ve tried it on QRT-5 and RB433AH with UB5 wlan card)
2nd step - “regular” scan runs automatically and all clients loose connection to AP
3rd step - I stop scan by clicking on “Stop” button and tick “background scan” option
4th step - Then I click on “Scan” button in “Scanner” window and I’m always getting that “Couldn’t start-background scan not supported in this state(6)” error message no matter what I do… any ideas?

Works on 2SHPN, in what mode is your routers now?Mine is AP Bridge, maybe doesnt work in some other modes, or just doesnt work on this models you have in general.

[soulflyhigh]

@ivicask
It is in AP bridge mode… I tried with setting it as station, with nv2 and nstreme, tried to connect to them from different winbox/ PC… the same thing happens.
Don’t think I’ve any 2SHPN in my network to test it (99% equipment in our network does work on 5GHz band, the rest are old R52s with sector 2.4GHz antennas).

Does anybody else have this problem with background scan?

Just for basics check - I installed latest RouterOS 6.35rc2 (download & install through winbox),
then manually downloaded wlan rep package for mipsbe from mikrotik site to my pc, uploaded it to those two routers, rebooted them again and then tried new features - I did things like that a million times before.
Background scan just won’t work.
Bizarre.

This is how it looks with station mode :
scr1.PNG

[ivicask]

@soulflyhigh

@ivicask
It is in AP bridge mode… I tried with setting it as station, with nv2 and nstreme, tried to connect to them from different winbox/ PC… the same thing happens.
Don’t think I’ve any 2SHPN in my network to test it (99% equipment in our network does work on 5GHz band, the rest are old R52s with sector 2.4GHz antennas).

Does anybody else have this problem with background scan?

Just for basics check - I installed latest RouterOS 6.35rc2 (download & install through winbox),
then manually downloaded wlan rep package for mipsbe from mikrotik site to my pc, uploaded it to those two routers, rebooted them again and then tried new features - I did things like that a million times before.
Background scan just won’t work.
Bizarre.

This is how it looks with station mode :

Yea, seams you did all good, btw i just tested this on all models we have in our company and for me its working on this models.

RB911G-5HPnD
RB2011UiAS-2HnD
RBcAP2n
2SHPn

[yottabit]

@normis

wireless-rep means repeater, yes. it also has a new wireless driver and many other new features, so It can’t be placed as default yet.

I would propose a new wireless package for testing should just be called something such as “wireless-test”, and stable wireless packages should be called, e.g., “wirelessV1” (wireless), “wirelessV2” (wireless-fp), “wirelessV3” (wireless-cm2), and eventually “wirelessV4” (stable version of today’s wireless-rep or wireless-test).

This makes it clear the upgrade path for additional functionality, and makes it clear there are backward-incompatible changes with each “V” version increment of the package.

[yottabit]

@normis

The repeater mode allows you to make a client and an AP both on the same physical interface. You don’t need two interfaces. That is the best about this new feature. It seems some of the above posters missed that.

Hi Normis,

What is required to have this work? Should only Virtual interfaces be used? Or main/physical interface set to Station mode and add Virtual AP to that?

[ivicask]

@yottabit

@normis

The repeater mode allows you to make a client and an AP both on the same physical interface. You don’t need two interfaces. That is the best about this new feature. It seems some of the above posters missed that.

Hi Normis,

What is required to have this work? Should only Virtual interfaces be used? Or main/physical interface set to Station mode and add Virtual AP to that?

I tried that and it didint work, virtual interfaces can be set to station, but they cant scan for networks..

[uldis]

background scan and repeater function can only work when wireless interface is running 802.11 wireless protocol.

[yottabit]

I tried that and it didint work, virtual interfaces can be set to station, but they cant scan for networks..

Did you try my second thought? Setting the main physical interface to Station and then adding a Virtual AP on top?

I gave away my test RBs recently so I don’t have any extras I can use to test this. I’ve been waiting for the hAP ac to finally be available to buy a couple to use for test devices.

[ivicask]

@uldis

background scan and repeater function can only work when wireless interface is running 802.11 wireless protocol.

I was running 802.11, background scan works for me, but im unable to connect to another WIFI AP while its set to AP mode, or dont know how to..

[honzam]

@uldis

background scan can only work when wireless interface is running 802.11 wireless protocol.

Very nice feature! Works well. No disconnect clients during sken.
Will be supported in future with NV2 protocol?

[PeterDoBrasil]

@sergejs

wireless repeater configuration can be done by,
setup-repeater command,
/interface wireless setup-repeater

there are parameters:
address – MAC address of AP to setup repeater for (optional)
ssid – SSID of AP to setup repeater for (optional)
passphrase – key to use for AP - if this is specified, command will
just scan for AP and create security profile based on info in beacon and
with this passphrase. If this IS NOT specified, command will do WPS to
find out passphrase.

New terminal says
[admin@MikroTik] > /interface wireless setup-repeater address=“4C:5E:0C:C4:41:BF” ssid=“5g.net 1”;
no such item (4)

[djdrastic]

It’s great to see MTK tackling some new wireless features.
Wireless often felt neglected in the MTK stable.
Any chance we’ll see any NV2 AC improvements going forward ?

[soulflyhigh]

@uldis

background scan and repeater function can only work when wireless interface is running 802.11 wireless protocol.

*) wireless-rep - initial support for station roaming for station mode in 802.11 protocol;
*) wireless-rep - added support for wireless repeater mode for 802.11 protocol;
*) wireless-rep - added support for wireless background scan;

Thanks for clarification, please correct this in the changelog.
Are there any plans for adding background scan feature for nstreme/nv2 ?

[taduikis]

You could have said that in the begining I’ve spent an hour or so and thought I was doing something wrong. I haven’t got a single AP running in plain 802.11, only in SOHO routers.. So no new function for me anyway nice to see something being done.

[WirelessRudy]

Is the default authenticate option gone? Is client now always to connect to units mentioned in the ‘Connect List’?
Def-auth missing.PNG
Can someone also explain when, and what, the Multicast Helper options do and the two new tickboxes might bring me for use…?

[andriys]

@WirelessRudy

Can someone also explain when, and what, the Multicast Helper options do and the two new tickboxes might bring me for use…?

Multicast helper option is described here.