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.
It would be great to have a list of improvements on different wireless packages. On the forum you always write that wireless-cm2 has improvements while wireless-fp is “legacy”, but what are these improvements?
It would be good to know what are your plans about replacing wireless packages to schedule massive upgrades on users!
On the DHCP Server/Leases Tab in Winbox, there is no way to get the dynamic leases on top.
And just a reminder - a missing bus field on USB Power reset in Winbox on multi bus systems like the RB922…
It’s clear “wireless-fp” is somewhat incompatible with “wireless-cm2”. However both of them provide superset of features included in plain old “wireless” (and thus may be considered backwards-compatible with “wireless”). As I understand, “wireless-rep” can also be considered backwards-compatible with “wireless-cm2”, but just is not stable enough yet to just replace the latter.
Can you please consider renaming “wireless-cm2” to “wireless”- this way you will ease a lot of pain while upgrading, while still stay compatible with the previous releases. You can do the same with “wireless-rep” later when it stabilizes, provided you do not invent CAPsMANv3 or similar thing that breaks compatibility.
We are considering many ways how we should proceed with these packages.
This is first rc release where we give our wireless-rep package. It will take a while for this package to be considered as stable.
Name of package wireless-rep is “repeater” ?
Well, I think that “wireless.npk” package should somehow be “default” package that is the latest stable. That way you don’t really have to know the sequence and keep tracking what is what. Of course there’s issues with compatibility, but you can always have any other package if you need something special or historic?
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.
Sure it can’t. As I mentioned above, I had a problem where 6.35rc1 AP with -rep package in NV2 didn’t work.
Is there any chance for working sniffer or snooper similiar to scan? Background sniffing will be very useful.
How to run background scan? Example?
Can you give some more details how to exactly setup this, i tried entering just /interface wireless setup-repeater and got “no such item (4)”.
I have 2.4ghz Metal 2SHPn, its currently set in WISP mode(AP BRIDGE).But i have nearby WIFI network to which i would want to connect at the same time.
I upgraded to new package and its enabled in packages list.
Any help how to run this scenario?
I wonder if its intended to provide spectral scan/history support in the future for the AC chipsets within this new package?
hotspot - fixed login by mac-cookie when roaming among hotspot servers
How it works? Can I distribute MAC-cookie to another router?
New wireless-rep package now can be found under extra packages at our download site (choose release candidate 6.35rcX):
http://www.mikrotik.com/download
I have the same problem, background scan doesn’t work even from terminal …
/interface wireless> scan 0 background=yes
failure: background scan not supported in this state
It doesn’t work from winbox 3.1 with this method
When you press “Scan” it starts a scan which interrupts the wireless link. You have to stop it and then start a background scan when the link is running, otherwise you’ll get that error.
- I’m getting the same error “Couldn’t start-background scan not supported in this state(6)”
Also, Nv2 doesnt work with this rep package, period.
Mikrotik guys, any comment regarding those issues?
background-scan.PNG
A nice feature 
Not tried it yet. But can we join two APs in repeater mode to be mutually AP and client on both ways together each to the other? Just curious of it…
Like we have multiple virtual AP, will we see also multiclient repeater mode one day?
(don’t take it seriously too much, just playing with the ideas)
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.
Wow! This new wireless-rep is fantastic! All my UDP packets are consistent, I have not lost a single packet! Amazing work guys!