v6.35rc has a new wireless package, that has the same features as wireless-cm2 package and will contain many new interesting features.
Few of the added functions are listed in the changelog below, more to come!
Documentation for the new wireless package is in progress. Please test new wireless-rep package before adding it to the production networks. Thank you very much for your feedback in the advance!
Package is available on download page with ‘All packages’ file.
What’s new in 6.35rc1 (2016-Jan-29 13:59):
*) route - do not show duplicate gateway on connected route;
*) wireless - added new package “wireless-rep”;
*) 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 for 802.11protocol;
*) wireless-rep - added support for saving wireless scan results to file;
*) wireless-rep - added support for wireless scan rounds setting;
*) wireless-rep - added WPS client support;
*) wireless-rep - added STEP feature for the scan-list;
how to configure wireless-repeater on one wirless interface.
it is done by command,
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.
Do you plan to merge all those new changes into ordinary wirelessXX.npk (without -cm2, -fp, -rep) package sometime in the future? It’s kinda difficult to do a mass upgrade when package name changes every year or so..
Do we need repeater function? It will be probably easier to configure than wds, maybe it will bring compatibility with other vendor’s APs, but do we really need it?
I am not against. Just asking… There were times I thought this would be very useful feature, but as the time went forward and I learned more and more, today I don’t think it is necessary. Wds is perfectly working and I am not missing the other vendor’s compatibility. So why? It’s bad idea to use one radio repeater anyway because it is not possible to align antennas against Ap and clients ideally at the same time. But ok, mikrotik thinks it will rise sales on consumer market, so that is it. I can forsee the topics here that the repeater is not as expected by consumers… Will never be.
How to run repeater mode?
Background scan, rounds, scan to file - all that feature works OK.
I see no options for station roaming. Is it “automagical” and it’s default enabled when I’m using new package, or I’m missing smthng?
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”
Set the fist wlan as an ap bridge and the second as pseudobridge. First we be the ap and the second the client
If i do the contrary i am unable to connect to the ap
*) wireless-rep - added support for wireless background scan;
I see opportunity to make auto frequency mode to work in background active scanning for noise and some algorithm to choice best channel or to make report in background it will be nice to see both options.
Now auto just scan when disable enable interface.
With new package TCP throughput is really impresive. There is a problem with nv2 connection. Client’s can’t connect, when protocol is set to nv2, only nstreme and 802.11 works. With nstreme, there is a problem with dynamic framin policy.
I really starting to like what you are doing.Don’t stop, and make it better
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 really hope MikroTik will introduce something new on wireless for point to multipoint!