In rc26, and it has been in CAPsMAN configuration, from the DHCP Server, which is activated in the other RB, has been confirmed a phenomenon in which the IP address is not passed.
Moreover, instead of immediately occur, but after the elapse of a few hours if you are using.

It has not been output, especially something like anxious to log.

If you have enabled local forwarding, it seems this phenomenon is likely to occur.

In rc26, and it has been in CAPsMAN configuration, from the DHCP Server, which is activated in the other RB, has been confirmed a phenomenon in which the IP address is not passed.
Moreover, instead of immediately occur, but after the elapse of a few hours if you are using.

It has not been output, especially something like anxious to log.

If you have enabled local forwarding, it seems this phenomenon is likely to occur.

Please provide more detailed info on the problem. What RouterOS version and wireless package you had were this all was working fine?
What setup you have on the CAPsMAN and the CAP?
Please send the support output files and also information how to reproduce this problem to support@mikrotik.com

Доброго дня Всем.

1. Очень серьёзная проблема, не могу от версии что обновился на 6.35rc19 ни дальше обновиться ни откатится назад. Пытался через НЕТИНСТАЛЛ 6.35.3 - не получилось. Не видит НЕТИНСТАЛЛ Микротик в состоянии BOOT

2. Около 2-х месяцев проблема с 2-йными сессиями в Микротик, во вложении скриншот. Авторизация у нас PPPoE через РАДИУС. Порой 2-х сессий так много, приходится по 2-3 раза в день перезагружать Микротик.

Problem001.jpg

Please make a support output file after the reboot and then another file when you see that the board has taken a lot of memory - this will help us to identify what causes the memory usage.
Send both files to support@mikrotik.com

Rc26
My hex increases the use of mem whitout reason until it hangs. Need to reboot to work again and do the same again.
12 hours more or less until it uses all the memory and need reboot.

No config changes before update. Only from rc 19 to rc 26

Update to include image.

Доброго дня Всем.

1. Очень серьёзная проблема, не могу от версии что обновился на 6.35rc19 ни дальше обновиться ни откатится назад. Пытался через НЕТИНСТАЛЛ 6.35.3 - не получилось. Не видит НЕТИНСТАЛЛ Микротик в состоянии BOOT

2. Около 2-х месяцев проблема с 2-йными сессиями в Микротик, во вложении скриншот. Авторизация у нас PPPoE через РАДИУС. Порой 2-х сессий так много, приходится по 2-3 раза в день перезагружать Микротик.

Problem001.jpg

English please

incahex, amokkatmt - Do you have some kind of tunnels on your devices? For example, L2TP and/or PPPoE?

Good day everyone.

1. Very serious problem, I can not from the version that was updated on 6.35rc19 no further update or rollback. Tried through NETINSTALL 6.35.3 - it did not work. He does not see NETINSTALL Mikrotik able BOOT

2. About 2 months is a problem with 2-ynymi sessions in Mikrotik, screenshot as an attachment. Authorization we PPPoE via RADIUS. Sometimes 2 sessions so much, we have 2-3 times a day to restart the Mikrotik.

Problem001.jpg

Good day everyone.

1. Very serious problem, I can not from the version that was updated on 6.35rc19 no further update or rollback. Tried through NETINSTALL 6.35.3 - it did not work. He does not see NETINSTALL Mikrotik able BOOT

2. About 2 months is a problem with 2-ynymi sessions in Mikrotik, screenshot as an attachment. Authorization we PPPoE via RADIUS. Sometimes 2 sessions so much, we have 2-3 times a day to restart the Mikrotik.

Problem001.jpg

Also have this issue on CCR1036-12G-4S.
Our real 800 pppoe clients turned into 2400 pppoe sessions with "kernel failure" random reboots and fail to up/down grade RouterOS. But netinstall worked for me. CCR just "kernel failure" and rebooting instead of flashing ROS. Same with restoring backups - "kernel failure". I have 3 supouts, 2 auto, and 1 created manually when uptime was 5 minutes. Where should I send this?

incahex, amokkatmt - Do you have some kind of tunnels on your devices? For example, L2TP and/or PPPoE?

Version 6.35rc29 has been released.

Changes since previous version:
*) RB3011 - fixed time keeping

I have wireless problems since 6.35rc28, didnt changed any config about that



Has anybody else these problems?

I have wireless problems since 6.35rc28, didnt changed any config about that



Has anybody else these problems?

With what wireless package you see this problem?
What configuration you have on the wireless and what wireless encryption you have enabled?
What is your wireless client hardware?

*) firewall - added experimental "action=route" in mangle prerouting - that forces packets to specific gateway by ignoring routing decisions (CLI only);

Happened here too with rc29 in x86 but stopped after a day. Normal behavior?
NTP SERVERS: 150.214.94.5 - 176.31.53.99

I use 6.35rc26 wireless-rep (AP mode), my laptop (WIN7 INTEL wireless 5300AGN) had a lot of PING loss, when I changed to WIRELESS-CM2, everything is normal.

*) snmp - fix getbulk result ordering with multiple request OIDs;

I use 6.35rc26 wireless-rep (AP mode), my laptop (WIN7 INTEL wireless 5300AGN) had a lot of PING loss, when I changed to WIRELESS-CM2, everything is normal.

Can reproduce this with 6.35rc31 on Basebox2. Switched back to WIRELESS-CM2 as well.

Version 6.35rc33 has been released.

*) lte - changed AT parsing because supported Huawei modems use unsolicit events instead of polling

I too am having wireless client issues since running 6.35rc33. Using a hAP AC in CAPsMAN mode and my clients keep loosing their connection to the network, connection stays up, but not traffic locally or to internet possible anymore. Reconnect of the wireless link immediately solves it. Running 6.35rc22 before this all worked perfectly well.

Hello
can any one have any clue what about this error

Untitled.png

heydude, what country setting you have specified in the CAPsMAN configuration as it selected 5740mhz as a center channel?

) winbox - added support for route action in mangle rules;

Version 6.35rc34 has been released.

Changes since previous version:
*) capsman - added 802.11g/n band;
*) chr - added support for VLAN on Hyper-V;
*) hotspot - fix possible deadlock;
*) hotspot - improved html page resistance against attacks;
*) l2tp & pppoe - fixed user traffic accounting when fastpath was used;
*) pppoe - fixed crash when removing <l2tp> pppoe service;
*) winbox - added init-delay option to routerboard settings;
*) winbox - added sfp-mac for GPON interfaces;
*) winbox - added support for route action in mangle rules;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

juanvi - Do you use wireless-rep package?

You must have at least 635rc34 and wireless-rep package on CAP device and also on CAPsMAN:

*) capsman - added 802.11g/n band;
*) wireless-rep - added 802.11g/n only band;

 by strods » 22 Mar 2016, 10:28


You must have at least 635rc34 and wireless-rep package on CAP device and also on CAPsMAN:

*) capsman - added 802.11g/n band;
*) wireless-rep - added 802.11g/n only band;

[juanvi@xxx] > caps-man provisioning set hw-supported-modes=
a  a-turbo  ac  an  b  g  g-turbo  gn

[juanvi@xxx] /caps-man> configuration set channel.band=
2ghz-b  2ghz-b/g  2ghz-b/g/n  2ghz-onlyg  2ghz-onlyn  5ghz-a  5ghz-a/n  5ghz-a/n/ac  5ghz-onlyac  5ghz-onlyn

Version 6.35rc35 has been released.

Changes since previous version:
*) chr - fixed kernel crash when virtual ethernet was not connected to anything in Hyper-V;
*) chr - implemented kernel crash saving to autosupout.rif (will utilize additional 24Mb of RAM);
*) romon - fix romon discovery after of romon ID change;
*) userman - fixed www crash;
*) wireless - fix crash on nstreme-dual interface stats update;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Version 6.35rc37 has been released.
*) lte - supported modems now use unsolicit events for network monitoring;

Version 6.35rc40 has been released.

Changes since previous version:

[...]
*) winbox - added init-delay option to routerboard settings;

Version 6.35rc35 has been released.

Changes since previous version:
*) chr - fixed kernel crash when virtual ethernet was not connected to anything in Hyper-V;
*) chr - implemented kernel crash saving to autosupout.rif (will utilize additional 24Mb of RAM);
*) romon - fix romon discovery after of romon ID change;
*) userman - fixed www crash;
*) wireless - fix crash on nstreme-dual interface stats update;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Version 6.35rc41 has been released.

Changes since previous version:
*) bonding - fixed mac-address disappearance after reboot in specific setups;
*) chr - fixed reboots with license and queues;
*) quickset - fixed invalid date adjusted the signal threshold for the signal chart and refresh rate;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Where can I find previous version of rc files? Need 6.35rc19.

Version 6.35rc41 has been released.
..[CUT]..
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

It does not resolve the behavior to flapping at the RB3011 interface.

[Ticket #2016032466000172]

Version 6.35rc41 has been released.
..[CUT]..
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

It does not resolve the behavior to flapping at the RB3011 interface.

[Ticket #2016032466000172]

Version 6.35rc42 ..port flapping on 3011 persist (ports 6-10), device unusable

Version 6.35rc42 ..port flapping on 3011 persist (ports 6-10), device unusable

Also confirmed here.
Downgraded back to 6.35rc29 and the problem was resolved.

Where can I find previous version of rc files? Need 6.35rc19.

http://download2.mikrotik.com/routeros/ ... e-6.19.zip ?

http://download2.mikrotik.com/routeros/6.35rc19/all_packages-mipsbe-6.35rc19.zip

Where can I find previous version of rc files? Need 6.35rc19.

http://download2.mikrotik.com/routeros/ ... e-6.19.zip ?

actually...

Code: Select all

http://download2.mikrotik.com/routeros/6.35rc19/all_packages-mipsbe-6.35rc19.zip

change the "mipsbe" to the platform you need.

Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:


1. {Nice to have} Add "CCQ", P Throughput" and "Signal to Noise", "Encryption" and "Group Encryption" and "WMM Enabled" fields to CAPsMAN Registration Table.

2. {Feature} Add "Frequency Mode", "WMM Support", "Multicast Buffering", "Keepalive frames", "Adaptive Noise Immunity" and "AMPDU Priorities" to CAPsMAN Config Settings.

3. {BUG} Make "Multicast Helper=full" in CAPsMAN slave interfaces work (now the interfaces stay in default setting).

4. {BUG} Make "Country=no_country_set" work on CAPsMAN 5GHz 802.11ac interfaces (it works on 2.4GHz, but on 5GHz ones it results in "no supported band" error message, regardless of the band and frequency settings).

5. {Feature} Add a scan/freq usage feature in CAPsMAN, with an aption to run in the background. Right now, if one wants to scan, they have to detach the physical interface from the Manager, do the scan and re-attach it. [In the future, use this info to auto-adjust CAP channels and power levels.]

6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name "wlanXXX" where XXX is a number which is incremented every time the interface is disabled and re-enabled.

7. {Nice to have} Let the user rename the virtual interfaces on the CAPs, like he/she can do with physical interfaces.

Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:


1. {Nice to have} Add "CCQ", P Throughput" and "Signal to Noise", "Encryption" and "Group Encryption" and "WMM Enabled" fields to CAPsMAN Registration Table.

2. {Feature} Add "Frequency Mode", "WMM Support", "Multicast Buffering", "Keepalive frames", "Adaptive Noise Immunity" and "AMPDU Priorities" to CAPsMAN Config Settings.

3. {BUG} Make "Multicast Helper=full" in CAPsMAN slave interfaces work (now the interfaces stay in default setting).

4. {BUG} Make "Country=no_country_set" work on CAPsMAN 5GHz 802.11ac interfaces (it works on 2.4GHz, but on 5GHz ones it results in "no supported band" error message, regardless of the band and frequency settings).

5. {Feature} Add a scan/freq usage feature in CAPsMAN, with an aption to run in the background. Right now, if one wants to scan, they have to detach the physical interface from the Manager, do the scan and re-attach it. [In the future, use this info to auto-adjust CAP channels and power levels.]

6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name "wlanXXX" where XXX is a number which is incremented every time the interface is disabled and re-enabled.

7. {Nice to have} Let the user rename the virtual interfaces on the CAPs, like he/she can do with physical interfaces.

V6.35rc42 with cm2 package and capsman also results in regularly wifi latency spikes to 1 sec and 2 seconds.

Reverting back the CAPSMAN to v6.34.3 while leaving the caps on v6.35rc42 resolves this latency spike issue. We use centralised forwarding on CCR

On update from 6.35rc43 to 6.35rc45 my RB951G-2HnD got boot-loop
How i can recover him?

My two STX 5AC are death after upgrade to this version! No access, so no suppot.rif. Tomorrow netinstall.

Same thing here with RB2011UiAS-2HnD-IN. Tried many times to Netinstall. The router always tries Ethernet boot, fails then says kernel failure before rebooting itself.

*) rb3011 - make ether6-ether10 work if SFP module is present on bootup;

*) rb3011 - make ether6-ether10 work if SFP module is present on bootup;

Does this resolve the port flapping issue that appeared on some rc after rc29?

If yes, did anyone manage to upgrade to the latest rc without 'bricking' their board?
There are a few reports not being able to boot afterwards.

Anyone lose wireless on 6.35rc45?

It completely disappeared on a 951Ui-2HnD. Reboot and resetting didn't help. Downgrading to stable fixed it.

Upgrading to RC again now to see if it happens again.

Upgrading to ROS v6.35rc45 has caused so many problems (bricking units), packages missing that I have spent the past few days just cleaning up the mess.
I have downgraded all but one router (that I can't reach now) to v6.34.4. So far, so good.
I realize this is rc revisions but is someone at Mikrotik deliberately trying to sabotage the firmware?
Think I'll stick with non-rc for a while till I'm convinced Tik is releasing nonvolatile firmware.

RC are essentially "Nighty Builds", don't rely on them in important networks.

Then they are not RC. Similar naming problem as "Current".

And I am thinking "Current" is maybe 2 things in one: Feature + RC

Nightly -> Beta -> RC -> Feature -> Bugfix

Big thanks to MikroTIK to transfer to 3 stage release (RC, Current, bugfix) it is sufficient for all my needs.

Big thanks to MikroTIK to transfer to 3 stage release (RC, Current, bugfix) it is sufficient for all my needs.

It is much, much better than older approach.

Stop this debate and enjoy RC releases! Feel proud yourselves because you're helping Mikrotik in making best networking products ever seen! They let us be a part of the developement with the RC channel! As the others do?

The problem is not that it is RC, but that it is NOT.

It is not even beta, because Current is beta-level, IMHO.

Nightly -> Beta -> RC -> Feature -> Bugfix

I also had the problem that the router couldnt reboot after the update (2011UiAS-2HnD)
Unplugged power and after replug the router startet.

I know it was my fault that i didnt checked the forum before installation but i dont understand why mikrotik still deliver this update when there are much more problems then normal.
It would be enough to disable the update and wait for next release.

I also had the problem that the router couldnt reboot after the update (2011UiAS-2HnD)
Unplugged power and after replug the router startet.

I know it was my fault that i didnt checked the forum before installation but i dont understand why mikrotik still deliver this update when there are much more problems then normal.
It would be enough to disable the update and wait for next release.

I threw my router in the trash, 2011UiAS-2HnD

I have 2x 951Ui-2HnD that are non-responsive after updating to v6.35rc45. One of them came back up partially, it had the the entire RoS Package disabled in it. I made a supout.rif and re-enabled the package and now it is completely non-responsive.

Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;

This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.

Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;

This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.

So if we are in rc43-45, we have to downgrade first ?

Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;

This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.

So if we are in rc43-45, we have to downgrade first ?

no, best way is to use netinstall

When everyone who bricked a device by update would send it to mikrotik back for warranty repair, it would make mikrotik to think and test twice before releasing harmful versions to public.

Thanks to all, that mikrotik made from 6.2 to 6.32 & 6.34.4 . There is some great impruvements of stability was made.

I also has problem with 6.35 rc44 or rc45 on my 951G with boot loop.
It was fixed with netinstall & some PXE server.
Now I am on 6.34.4 and do not shure to go back to RC.

Can be PXE server be integrated to netintall for easy recover? Or write some more in manual? For idiots.

Dear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G

Dear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G

It IS supported on all RB7xx

Dear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G

It IS supported on all RB7xx

It works on our RB750GL but not on our RB750G

I found one on old board shelf, just betweer RB230 and RB532. , Yes you are right, this board is using same CPU as RB4xx series, so fastpath is not supported. you need ar72xx CPU at least ar71xx doesn't have the support.

I'd really appreciate a working config that I can dig through to understand.

My other problem is finding a sequence of steps to get from the factory-default RBmAPL-n2D WISP AP configuration to one where the (only) Ethernet interface is on the LAN without losing Winbox connectability. (I can always use the magic button to restore the factory-default configuration, but then I'm right back where I started.) Once I'm controlling the router firmly through its Ethernet interface, I should be able to reconfigure the wlan interface without losing control.

# RouterOS Hotel Setup
# Created 2016-04-10 by Jacob McDonald
# Revised n/a

# This config was built using a model RouterBOARD 962UiGS-5HacT2HnT (“hAP ac”).
# This router has 1x 2.4 GHz radio and 1x 5 GHz radio, but this configuration does not depend on two radios.
# This config uses the 2.4 GHz radio base interface in Station-Pseudobridge mode to connect to another Wi-Fi AP,
# and creates a Virtual AP virtual interface on top to serve 2.4 GHz stations. A 5 GHz AP is also configured, and
# the 5 GHz AP would provide better performance since the 2.4 GHz radio wouldn’t have to share air-time serving
# stations in AP mode and forwarding the traffic to the other AP in station mode.

# The split-mode radio configuration only works with RouterOS 6.35 (rc and higher), using the testing radio
# package “wireless-rep”. This package is not included in the main software package, but can be extracted from
# the extras package and installed a la carte.
# RotuerOS Software: http://www.mikrotik.com/download

# 1. Install the base package from System -> Packages, or by uploading the .npk to the root filesystem and reboot.
# 2. Extract the wireless-rep.npk package from the extras .zip archive, upload to the root filesystem, and reboot.
# 3. Third, upgrade the RouterBOARD firmware: System -> RouterBOARD -> Upgrade, and reboot.

# Change the wireless security profiles in “/interface wireless security-profiles” below:
#   default: set for your desired AP password (LAN)
#   wlan-WAN: set to the AP password for the Wi-Fi network you wish to use as WAN
#   none: this is a profile for using a Wi-Fi network as WAN with no authentication, typical in hotels

# Change between “wlan-WAN” and “none” security-profile as-needed by changing the setting in the
# “/interface wireless wlan1-WAN” config.

# Using the WebUI, Winbox, or CLI, perform Scan on the wlan-WAN interface, and select Connect to the AP you wish
# to use as WAN. This will adopt the frequency, bandwidth, and protocol settings automatically.

# This config will use the DHCP-supplied DNS servers from the WAN interface, which will be necessary to pass
# through the captive portal.

# apr/10/2016 20:31:47 by RouterOS 6.35rc48
# software id = XZFF-04CI
#
/interface bridge
add name=bridge1
/interface ethernet
set [ find default-name=ether1 ] name=ether1-WAN
/interface wireless
set [ find default-name=wlan2 ] band=5ghz-a/n/ac disabled=no mode=ap-bridge name=wlan2-5G-LAN ssid="Magrathea 5G" wireless-protocol=802.11
/ip neighbor discovery
set ether1-WAN discover=no
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys supplicant-identity=MikroTik wpa2-pre-shared-key=h2g2h2g2
add authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys name=wlan-WAN supplicant-identity="" wpa-pre-shared-key=hdyfrc4la1 wpa2-pre-shared-key=hdyfrc4la1
add name=none
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n disabled=no distance=indoors frequency=2442 mode=station-pseudobridge name=wlan1-2G-WAN security-profile=wlan-WAN \
    ssid=skyconway_com-2231 wireless-protocol=802.11
add disabled=no keepalive-frames=disabled mac-address=E6:8D:8C:49:23:FA master-interface=wlan1-2G-WAN mode=ap-bridge multicast-buffering=disabled name=wlan3-2G-LAN ssid=Magrathea \
    wds-cost-range=0 wds-default-cost=0 wps-mode=disabled
/ip neighbor discovery
set wlan1-2G-WAN discover=no
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=dhcp ranges=192.168.88.3-192.168.88.254
/ip dhcp-server
add address-pool=dhcp authoritative=yes disabled=no interface=bridge1 name=dhcp1
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=sfp1
add bridge=bridge1 interface=wlan2-5G-LAN
add bridge=bridge1 interface=wlan3-2G-LAN
/ip address
add address=192.168.88.1/24 interface=ether2 network=192.168.88.0
/ip dhcp-client
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no interface=ether1-WAN
add default-route-distance=2 dhcp-options=hostname,clientid disabled=no interface=wlan1-2G-WAN
/ip dhcp-server network
add address=192.168.88.0/24 gateway=192.168.88.1 netmask=24
/ip dns
set allow-remote-requests=yes
/ip firewall filter
add chain=input protocol=icmp
add chain=input connection-state=established
add chain=input connection-state=related
add action=drop chain=input in-interface=ether1-WAN
add action=drop chain=input in-interface=wlan1-2G-WAN
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1-WAN
add action=masquerade chain=srcnat out-interface=wlan1-2G-WAN
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=bridge1 type=internal
add interface=ether1-WAN type=external
add interface=wlan1-2G-WAN type=external
/system clock
set time-zone-name=UTC
/system identity
set name=rbtest
/system leds
set 1 interface=wlan2-5G-LAN
/system ntp client
# These are from us.pool.ntp.org
set enabled=yes primary-ntp=108.61.73.243 secondary-ntp=216.229.4.69
/tool mac-server
set [ find default=yes ] disabled=yes
add interface=ether2
add interface=ether3
add interface=ether4
add interface=ether5
add interface=sfp1
add interface=wlan2-5G-LAN
add interface=wlan3-2G-LAN
/tool mac-server mac-winbox
set [ find default=yes ] disabled=yes
add interface=ether2
add interface=ether3
add interface=ether4
add interface=ether5
add interface=sfp1
add interface=wlan2-5G-LAN
add interface=wlan3-2G-LAN

Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:

6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name "wlanXXX" where XXX is a number which is incremented every time the interface is disabled and re-enabled.

Did someone try to this new feature?
>> wireless background scan
I wanted to script a background scan for known Wifi-APs and if found, connect to it automatically.
The Microtik is in a car, and I know several Wifi along the road (while stopping the car!).
The Idea was: Scan for known ssid's (or MAC..) and if found one, set wlan2 to the known credentials.

Why not use the existing wireless "connect list" feature ?

Version 6.35rc49 has been released.
...
*) tunnels - fixed performance slowdown on any other tunnel disable/enable;
...