v6.37rc [release candidate] is released, only one wireless package!

Thu Jul 21, 2016 11:49 am

What's new in 6.37rc4 (2016-Jul-21 07:17):

Wireless is now unified to a single "wireless" package.
Update on some package configurations is dangerous!!!

*) wireless - "wireless-rep" renamed to "wireless";
*) wireless - "wireless-cm2" discontinued, uninstall it before update;
*) wireless - "wireless" package included in bundle "routeros" package;
*) check-for-updates - with bundle "routeros" package, will replace wireless package automatically;
*) check-for-updates - with one standalone wireless package, will replace wireless package automatically;
*) check-for-updates - with two or more standalone wireless packages, will result in no wireless packages installed, uninstall extra packages first;
*) ccr/crs - fixed SFP+ interface ddmi info reporting function. Info is now refreshed on regular intervals.
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424 );
*) ovpn - add special exception route for tunnel itself when using add-default-route;
*) ping - fixed freezing on "not running" interfaces;
*) resource - fixed free-memory reporting after disk eject;
*) x86 - fixed crash when igmp-proxy interface becomes "not running" while passing traffic;

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.

Thu Jul 21, 2016 2:23 pm

*) wireless - "wireless-rep" renamed to "wireless";

GREAT news ☺

*) ccr/crs - fixed SFP+ interface ddmi info reporting function. Info is now refreshed on regular intervals

Even better news !

kometchtech · Thu Jul 21, 2016 8:10 pm

Hi, MT support

Check for update cannot download the rc version of the mips and ARM files would be forgotten place?

My best regards.

CyberTod · Thu Jul 21, 2016 8:14 pm

*) wireless - "wireless-cm2" discontinued, uninstall it before update;

What does this mean ?
Are we going to be able to update boards that we are connected to via wireless ?

JimmyNyholm · Thu Jul 21, 2016 10:41 pm

*) wireless - "wireless-cm2" discontinued, uninstall it before update;

As before: Uninstall Error - can not uninstall bundled package (6)

I will try disable and upgrade....

minelli · Thu Jul 21, 2016 10:46 pm

When trying to download the version of the site get the following error.
Following is the url to the site sends and error.

Url

http://download.mikrotik.com/all_packages-mipsbe-6.37rc4.zip

Error:
404 - Not Found

noby · Thu Jul 21, 2016 11:08 pm

hello! so i get this error... https://s32.postimg.org/t6hcsxcyt/error_update.jpg

JimmyNyholm · Thu Jul 21, 2016 11:36 pm

*) wireless - "wireless-cm2" discontinued, uninstall it before update;

As before: Uninstall Error - can not uninstall bundled package (6)

I will try disable and upgrade....

Works. Disable, reboot, upgrade. Please do not write uninstall when that is not possible. or be more specific disable if package is bundled in your setup, uninstall if you have manually installed the package.

poizzon · Thu Jul 21, 2016 11:40 pm

via WinBox GUI ping, got ERROR : no address

killersoft · Fri Jul 22, 2016 1:01 am

Updated from 6.36 to 6.37rc4 on a RB951-2n.. Did the update over wireless, but of course it didn't not come back.
I see I should have updated it over Ethernet.

I had to manually enable 'Wireless' package and manually enable the wlan1 interface and re-program SSID/frequency etc.. So its like a fresh new interface (nothing was copied over from cm2)

Apart from that the update went ok.
Using it ok at the moment as a test box..

Fri Jul 22, 2016 7:08 am

We are sorry for any inconvenience. As we just released only one wireless package and there were actually four of them in the past, we are still updating our upgrade server so it would work correctly for any case.

When we will fix it only way that you can lose wireless connection will be if you have more than one wireless package outside of bundle package. You have to remove packages manually until only one standalone package is installed. Then (hopefully today) upgrade process must go automatically and you should not see "missing wireless package" errors any more.

CyberTod · Fri Jul 22, 2016 8:34 am

So we are to expect that the problems upgrading over wireless will be limited to the rc versions and when final comes out we will be able to do it with the upgrade process automatically uninstall absolete packages ?

Fri Jul 22, 2016 9:24 am

1) with bundle "routeros" package, upgrade will replace wireless package automatically;
2) with one standalone wireless package, upgrade will replace wireless package automatically;
3) with two or more standalone wireless packages, upgrade will result in no wireless packages installed, uninstall extra packages first.

So after we will adjust server only thing that you need to check before upgrade is #3,.

UsernameMT · Fri Jul 22, 2016 9:49 am

...

"Address List" - a very good
"Interface List" - excellent
...
Possible to make a "MAC List"?

Please!

Best regards!

Fri Jul 22, 2016 10:34 am

Upgrade now is fixed and if you have out of bundle single wireless package, then now you should be able to upgrade correctly.

Still - if you have more than one out of bundle wireless package, then you need to remove packages until only one is left and then upgrade.

CyberTod · Fri Jul 22, 2016 11:38 am

Thanks for clarification.
That sounds good enough and for someone like me who always installs bundled package this is a no issue. And I have installed wireless-rep as a separate on a few boards for testing, but only that I can reach by lan.

Fri Jul 22, 2016 1:47 pm

Version 6.37rc5 has been released.

Fixes in last RC:

*) address-list - allow DNS names with "_" symbol;
*) conntrack - fixed ipv6 timeout display;
*) conntrack - fixed removing icmpv6 connections;
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424 );
*) export - removed unnecessary "log-prefix" on firewall export;
*) firewall - fixed time based rules on time/timezone changes;

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.

UsernameMT · Fri Jul 22, 2016 2:34 pm

on old versions
this script:

:do {/ip firewall address-list add address=22.22.22.22 comment="Banned-X" list=list-X} on-error={ :put "failed add 22.22.22.22"};

on subsequent executions, return on-error={ :put "failed add 22.22.22.22"}

after version v6.36
this script:

:do {/ip firewall address-list add address=google.com comment="google.com" timeout=0 list="BAN-list"} on-error={:put "failed add google.com, already exists."};

does not return on-error, adds a duplicate (this bug only with the URL, when adding IP - returns on-error)

PS: when added through WinBox the same problem - it is possible to create a duplicate

ArmanIII · Fri Jul 22, 2016 5:07 pm

Version: 6.37rc5
Ping tool doesn't work from Winbox and WebFig. It shows: ERROR: no address
From terminal ( ping 8.8.8.8 ) it works without problem.

kamalrajali · Fri Jul 22, 2016 10:12 pm

wireless package

IntrusDave · Sat Jul 23, 2016 1:57 am

Version: 6.37rc5
Ping tool doesn't work from Winbox and WebFig. It shows: ERROR: no address
From terminal ( ping 8.8.8.8 ) it works without problem.

I can confirm this.

Safic · Sat Jul 23, 2016 12:30 pm

Version: 6.37rc5
Ping tool doesn't work from Winbox and WebFig. It shows: ERROR: no address
From terminal ( ping 8.8.8.8 ) it works without problem.

It's true. In terminal window ping works fine.

leroylim · Sat Jul 23, 2016 5:49 pm

The wireless-fp package v6.35.2 is still there after upgrading to 6.37rc.
Trying to uninstall it doesn't work.

Mon Jul 25, 2016 8:34 am

Ping tool in Winbox will be fixed with upcoming 6.37rc versions.
leroylim - Please generate supout file on your device and send it to support@mikrotik.com. Also explain what packages did you have on router before upgrade and how did you perform upgrade.

leandrosucesso · Mon Jul 25, 2016 10:06 pm

Help me please,

I updated my RB2011UiAS-2HnD for version 6.37rc5, then my wireless interface vanished.

Im not see my interface wireless in winbox.

Its bug this version?

notToNew · Tue Jul 26, 2016 12:01 pm

After upgrade to 6.35.4 to 6.37rc5, I experienced unreliable Wireless with the new wireless-packet with my samsung galaxy k-zoom cellphone (about s4 hardware).
I got disconnected 3 times in 30 minutes, seeing "packet flood"-errormessages in the log.
The Sony-phone from my wife worked without any issues.
My Sonos-Wireless-Multiroom-Speakers also had problems and reconnected often.
An older Laptop with an intel 2200BG even did not get any IP-Adress.

I downgraded to 6.36 with wireless-cm2, where both Cellphones, Sonos and the old Laptop worked again, so i hope you still maintain old
versions with wireless-cm2-package for a long time.

Edit1: Added my olf FW version

notToNew · Tue Jul 26, 2016 5:35 pm

I have a feature-request: Let a Firewall-Rule directly run a Script. (action=run-script)

Currently i have 2 choices:
1. Add an ip to a list and scan the lists for an added IP with an scheduled-script
2. parse the LOG

I do need it for example for automatically sending WOL-packets when acessing the nas from external.

pank · Tue Jul 26, 2016 6:39 pm

Update RB2011UiAS-2HnD to 6.37rc5,
old wireless-fp still there, can not uninstall (mark Uninstall, reboot, still there)
wireless can not enable (mark Enable, reboot, still disabled)

At first, I update it to 6.36, but wireless interface gone because wireless package can not enable,
I tried 6.37rc5 further, same situation.

After downgrade to 6.35.4, wireless back.

UsernameMT · Wed Jul 27, 2016 1:17 pm

Please, create v6.36.1 from bug fix:
http://forum.mikrotik.com/viewtopic.php ... 25#p548501

raffav · Wed Jul 27, 2016 1:35 pm

Please, create v6.36.1 from bug fix:
http://forum.mikrotik.com/viewtopic.php ... 25#p548501

Hi
Until what version your script worked?

Enviado de meu XT1580 usando Tapatalk

Wed Jul 27, 2016 2:00 pm

Note, there will be only one “wireless” package in the next RouterOS v6.37.

a) If using bundle package (routeros-xx.npk):
To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

b) If you are not using “routeros” bundle package and have two wireless packages installed, uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to 6.37 version.

UsernameMT · Wed Jul 27, 2016 2:05 pm

Hi
Until what version your script worked?

in version 6.36 added

What's new in 6.36 (2016-Jul-20 14:09):

*) firewall - allow to add domain name to address-lists (dynamic entries for resolved addresses will be added to specified list);

but MikrotikTeam, forgot

to add this new feature return "on-error=", if there is already such an entry in the address-lists (so creates duplicates in address-lists).
It is only when adding URL.

try it yourself to run the script several times on version 6.36:

:do {/ip firewall address-list add address=google.com comment="google.com" timeout=0 list="BAN-list"} on-error={:put "failed add google.com, already exists."};

it work bad - creates duplicate entries in the address list.

Now try this script

:do {/ip firewall address-list add address=22.22.22.22 comment="Banned-X" list="list-X"} on-error={ :put "failed add 22.22.22.22"};

it works good, this script creates only one entry in the address-lists

TonyJr · Wed Jul 27, 2016 8:29 pm

Hello,

I have just performed an upgrade from 6.36 to 6.37rc5, original packages were the routeros bundle with combined wireless-cm2 disabled, and the separate wireless-rep package installed and enabled.

The process works fine, however it takes approximately four times longer to complete. I was wondering if it had gone into a reboot loop but luckily I was patient. Would it be worth writing that the upgrade process may take longer than usual when dealing with the wireless package 'automatic migration', in the release notes?

[edit] I used the

/s p u d

and

 /s p u i

commands i.e. automatic upgrade rather than the manual process.

TonyJr

andreat · Thu Jul 28, 2016 11:05 am

Hello,
I've some features requests (don't know if this is the right place to post them):

If I place the same device in two (or more) differents network maps, this device shouldn't be polled twice (or more times), one time per every map.
If I disable a networkmap actually dude keeps polling and colling data for this map rather than pausing everything.
Bring back web interface.
Android client.

Thanks !

notToNew · Thu Jul 28, 2016 1:00 pm

Hello,
I've some features requests (don't know if this is the right place to post them):

Hi, I think, this ist the better place for dude-postings: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424

docmarius · Thu Jul 28, 2016 4:23 pm

Following the instruction for the single bundle upgrade one still will loose their wireless configuration, since the wireless package is disabled by default in RC5.

To be able to recover it do the following steps:
1. Make sure you use wireless-cm2 and have no other wireless package outside the bundle
2. Create a backup under files->backup
3. Upgrade via ethernet
4. Enable the wireless package - you will get some disabled wireless interface(s)
5. Restore the previous backed up config
You should now have your old configuration back and working with the "wireless" package

@MT: It would be useful to release a 6.36.x bundle containing 2 wireless packages. The original "wireless-cm2" package AND the same cm2 renamed to "wireless". Then it would be easy just to enable "wireless" and disable "wireless-cm2". After the reboot one would have a working wireless config using the "wireless" package. After that, one could upgrade the bundle to 6.37 without any issues and everything could be done via WiFi without loosing access.

Fri Jul 29, 2016 11:15 am

Caution, if you are running routeros (bundle) with multiple wireless packages, install 6.36 version before upgrade to 6.37rc.

Version 6.37rc10 has been released.

>>> IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using “routeros” bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one “wireless” package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

>>> IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to “dfs=radar-detect” for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Changes since 6.37rc5:

!) dude - from now on dude will use winbox port and it will be changed automatically both in client loader and agent configuration.
!) wireless - DFS option is removed and forced to "dfs=radar-detect";
!) console - dfs-mode setting does not exist any more and all scripts with such setting will not be executed;
*) bridge - fixed kernel failure when set-priority action was used in bridge firewall;
*) dns - avoid unnecessary static entry saving in storage;
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424);
*) email - increased time which email tool can spend while sending message;
*) ethernet - added support for LAN9514 ethernet dongle;
*) firewall - check for duplicates when domain name is used in address field;
*) lte - added ability to send/receive sms using '/tool sms';
*) lte - added Pantech UML295, Vodafone K4201-Z, ZTE MF823/MF831 support;
*) lte - fixed access technology update;
*) lte - fixed at chat condition storage;
*) lte - fixed ip activation when CREG (circuit switched) state remains in not registered state;
*) modem - added dlink dwm-157 D support;
*) sms - moved incorrectly logged message from async to gsm topic;
*) sms - report error when unsupported modem is being used;
*) snmp - added script table which executes script and returns it's output on get request;
*) snmp - fixed packet corruption when multiple trap-targets were used;
*) tile - fixed rare kernel crash when fastpath is being active;
*) tile - fixed rare kernel crash when usb device is being attached;
*) traffic-flow - fixed kernel failure when traffic-flow target uses small mtu;
*) upnp - updated to make it work with more UPnP implementations (for example, latest Skype);
*) upnp - fixed nat rule dst-port by making it visible again;
*) vrrp - fixed transition to backup state when ipv6 mode and equal priorities are used;
*) wireless - display DFS flag in country info;

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.

Fri Jul 29, 2016 11:48 am

DFS mode setting is removed, and by default becomes forced to “dfs=radar-detect” for all
devices that use radar frequencies.

Does it mean that frequency option suddenly became useless for "all devices that use radar frequencies"? I.e. no chance to select band manually?

Fri Jul 29, 2016 12:02 pm

DFS mode setting is removed, and by default becomes forced to “dfs=radar-detect” for all
devices that use radar frequencies.
Does it mean that frequency option suddenly became useless for "all devices that use radar frequencies"? I.e. no chance to select band manually?

If in the 'frequency' field you had frequency that isn't in the radar frequency range then nothing will change - it will still use that frequency.

If in the 'frequency' field you had frequency that is in the radar frequency range then AP will start to look for radar in that specified frequency. If the radar is not detected then it will continue use that frequency. If a radar is detected, it will use the scan-list setting to look for a new frequency in the frequency list. If it selects a radar frequency range, it will start detecting the radar and if no radar is found it will start to work there.

zajadacz · Fri Jul 29, 2016 12:35 pm

What if I use routerboard in the country that does not requires use of DFS (eg. Uzbekistan)?
Will Mikrotik force use of DFS in such situations?

Fri Jul 29, 2016 12:43 pm

What if I use routerboard in the country that does not requires use of DFS (eg. Uzbekistan)?
Will Mikrotik force use of DFS in such situations?

Check "country info" command in the console to see if your country has any DFS frequencies. If it does not have, you will not be affected in any way. For example:

/interface wireless info country-info uzbekistan

Fri Jul 29, 2016 12:45 pm

That changelog thing is starting to get out of hand....

Are there any plans for mandatory county specification, or automatic discovery via /ip cloud?

Fri Jul 29, 2016 1:13 pm

It is your own responsibility to use correct country setting. Automatic discovery is never reliable, if you use IPv6 or VPN.

docmarius · Fri Jul 29, 2016 1:15 pm

Please no automatic stuff. You can not cover all situations!

raffav · Fri Jul 29, 2016 2:12 pm

It is your own responsibility to use correct country setting. Automatic discovery is never reliable, if you use IPv6 or VPN.

That rc, fix the ping tool bug?
Because isn't on the changelog

Enviado de meu XT1580 usando Tapatalk

zichovsky · Fri Jul 29, 2016 2:20 pm

DFS mode setting is removed, and by default becomes forced to “dfs=radar-detect” for all
devices that use radar frequencies. If your client devices use a scan list with a few

This is realy bad decision. Hoopefully it will not be backported, so 6.36 will be last usable ROS.
"radar-detect" currently react on ANY interference on same chanel (does not matter if it realy is radar or only other wireless network), so any AP on open space (radio tower) with "radar-detect" enabled will end in endless frequency search loop, even when there is realy no radar

I hope taht there will be country "other" (as concurrent manufactures have) with full spectrum width available and without DFS.
Let people, who install your devices, decide whether on that specific site is DFS needed (if it could interfere with radar) or not. In fact, it is their responsibility againt local authorities.

Fri Jul 29, 2016 2:21 pm

with "radar-detect" enabled will end in endless frequency search loop, even when there is realy no radar

That is not true. All countries in the EU, and the USA should have already been using this setting for a long time, and there are no problems like you describe.

I hope taht there will be country "other"

RouterOS already has a superchannel mode that does exactly this.

MartijnVdS · Fri Jul 29, 2016 2:28 pm

with "radar-detect" enabled will end in endless frequency search loop, even when there is realy no radar
That is not true. All countries in the EU, and the USA should have already been using this setting for a long time, and there are no problems like you describe.

The only thing I've experienced that's similar to the described problem is the fact that the AP doesn't come back immediately after config changes, but does a round of radar detection first (which can take a few minutes). But as far as I know, that's also part of the official regulations (and how often do you change AP interface settings anyway?)

zichovsky · Fri Jul 29, 2016 2:29 pm

with "radar-detect" enabled will end in endless frequency search loop, even when there is realy no radar
That is not true. All countries in the EU, and the USA should have already been using this setting for a long time, and there are no problems like you describe.

There are no problems, because all switched dfs to off

Yes, you are right that (legaly) in EU and USA it should be set to on, but as far I know, every local provider (CZ) have switched dfs off because of behavior I've described. (And does not matter if they use Mikrotik, Ubiquity, Cambium or anything other.)

docmarius · Fri Jul 29, 2016 2:33 pm

I'm still wondering who that genius that decided to overlap weather radar with ISM was.

Zorro · Fri Jul 29, 2016 3:42 pm

weather radars isn't worst thing. there was some air traffic radars sometimes there too.
and in some regions - paramedics used that band for walkie-talkie(&in their cars).
i think FCC-alike enforcements should apply to their jurisdictions(which is MT approach so far), not attempts to enforce/lock-down "on global scale" something on all reachable/affected vendors.

napismizpravu · Fri Jul 29, 2016 4:59 pm

DFS (radar detect always) > bad decision

Fri Jul 29, 2016 5:42 pm

What is the business reason to force the DFS on? Mikrotik should explain it really in details. There are rules that when radar is detected, the Ap should lower its tx power, sometimes, so there is not really necessary to leave the frequency. When radar is stopped, it can revert the tx power back to previous legal limit. How this is supported?

What if I take care about the weather radars and have already my radios correctly set from the real tx power point of view and positively know that they do not have any influence on the weather radars... Why the link should be dropped down just due to false positive radar detection? To whom it helps?

HaQs · Fri Jul 29, 2016 8:38 pm

DFS (radar detect always) > bad decision

Very bad

IntrusDave · Fri Jul 29, 2016 9:54 pm

On 922UAGS-5HPacD, the Current TX Power no longer displaying anything.

netwpl · Fri Jul 29, 2016 10:53 pm

After upgrade to 6.35.4 to 6.37rc5, I experienced unreliable Wireless with the new wireless-packet with my samsung galaxy k-zoom cellphone (about s4 hardware).
I got disconnected 3 times in 30 minutes, seeing "packet flood"-errormessages in the log.
The Sony-phone from my wife worked without any issues.
My Sonos-Wireless-Multiroom-Speakers also had problems and reconnected often.
An older Laptop with an intel 2200BG even did not get any IP-Adress.

I downgraded to 6.36 with wireless-cm2, where both Cellphones, Sonos and the old Laptop worked again, so i hope you still maintain old
versions with wireless-cm2-package for a long time.

same problem here! probably this happens since MT release the wireless-rep package.
OLD Phones like LG3 cant connect or if they can, they get about 1-2Mbit!
NEWer Phones like my Samsung G S7 edge works flawless.
i have now downgraded all my routers to 6.36 and wireless-cm package and everything works like a charm..
anyone can tell me whats wrong ? my 6.36 and wireless-cm config works:

/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa-psk,wpa2-psk eap-methods="" group-ciphers=tkip,aes-ccm group-key-update=30m interim-update=0s \
    management-protection=disabled management-protection-key="" mode=dynamic-keys mschapv2-password="" mschapv2-username="" name=default radius-eap-accounting=\
    no radius-mac-accounting=no radius-mac-authentication=no radius-mac-caching=disabled radius-mac-format=XX:XX:XX:XX:XX:XX radius-mac-mode=as-username \
    static-algo-0=none static-algo-1=none static-algo-2=none static-algo-3=none static-key-0="" static-key-1="" static-key-2="" static-key-3="" \
    static-sta-private-algo=none static-sta-private-key="" static-transmit-key=key-0 supplicant-identity=MikroTik tls-certificate=none tls-mode=no-certificates \
    unicast-ciphers=tkip,aes-ccm wpa-pre-shared-key=iwan2807 wpa2-pre-shared-key=....


/interface wireless
set [ find default-name=wlan1 ] adaptive-noise-immunity=none allow-sharedkey=no ampdu-priorities=0,1,2,3,4,5,6,7 amsdu-limit=8192 amsdu-threshold=8192 \
    antenna-gain=0 area="" arp=enabled arp-timeout=auto band=2ghz-b/g/n basic-rates-a/g=6Mbps basic-rates-b=1Mbps bridge-mode=enabled channel-width=20/40mh
    compression=no country=austria default-ap-tx-limit=0 default-authentication=yes default-client-tx-limit=0 default-forwarding=yes dfs-mode=none \
    disable-running-check=no disabled=no disconnect-timeout=3s distance=indoors frame-lifetime=0 frequency=auto frequency-mode=regulatory-domain \
    frequency-offset=0 guard-interval=any hide-ssid=no ht-basic-mcs=mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7 ht-supported-mcs="mcs-0,mcs-1,mcs-2,mcs
    -4,mcs-5,mcs-6,mcs-7,mcs-8,mcs-9,mcs-10,mcs-11,mcs-12,mcs-13,mcs-14,mcs-15,mcs-16,mcs-17,mcs-18,mcs-19,mcs-20,mcs-21,mcs-22,mcs-23" \
    hw-fragmentation-threshold=disabled hw-protection-mode=none hw-protection-threshold=0 hw-retries=7 interworking-profile=disabled keepalive-frames=enabl
    l2mtu=1600 mac-address=D4:CA:6D:A8:A0:05 max-station-count=2007 mode=ap-bridge mtu=1500 multicast-buffering=enabled multicast-helper=full name=wlan1 \
    noise-floor-threshold=default nv2-cell-radius=30 nv2-noise-floor-offset=default nv2-preshared-key="" nv2-qos=default nv2-queue-count=2 nv2-security=dis
    on-fail-retry-time=100ms preamble-mode=both radio-name=D4CA6DA8A005 rate-selection=advanced rate-set=default rx-chains=0,1 scan-list=default \
    security-profile=default ssid=... station-bridge-clone-mac=00:00:00:00:00:00 supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mb
    supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps tdma-period-size=2 tx-chains=0,1 tx-power-mode=default update-stats-interval=disabled vlan-id=1 vlan-mode=
    no-tag wds-cost-range=50-150 wds-default-bridge=none wds-default-cost=100 wds-ignore-ssid=no wds-mode=disabled wireless-protocol=802.11 wmm-support=ena
    wps-mode=push-button
/interface wireless manual-tx-power-table
set wlan1 manual-tx-powers="1Mbps:17,2Mbps:17,5.5Mbps:17,11Mbps:17,6Mbps:17,9Mbps:17,12Mbps:17,18Mbps:17,24Mbps:17,36Mbps:17,48Mbps:17,54Mbps:17,HT20-0:17,
    :17,HT20-2:17,HT20-3:17,HT20-4:17,HT20-5:17,HT20-6:17,HT20-7:17,HT40-0:17,HT40-1:17,HT40-2:17,HT40-3:17,HT40-4:17,HT40-5:17,HT40-6:17,HT40-7:17"
/interface wireless nstreme
set wlan1 disable-csma=no enable-nstreme=no enable-polling=yes framer-limit=3200 framer-policy=none
/interface wireless align
set active-mode=no audio-max=0 audio-min=0 audio-monitor=00:00:00:00:00:00 filter-mac=00:00:00:00:00:00 frame-size=200 frames-per-second=1 receive-all=no \
    ssid-all=no
/interface wireless sniffer
set channel-time=200ms file-limit=10 file-name="" memory-limit=10 multiple-channels=no only-headers=no receive-errors=no streaming-enabled=no \
    streaming-max-rate=0 streaming-server=0.0.0.0
/interface wireless snooper
set channel-time=200ms multiple-channels=yes receive-errors=no

Zorro · Sat Jul 30, 2016 12:30 am

since american FCC insisting on and MT depend on american chips and sdk a lot(let alone impact of licensing issues &/or access to relevant IP/patent to use in ROS) - they had no options than to comply.
radar detection isn't bad, just implementation not really flawless, yet. same about DFS itself.
but always better to had option(if you're not under fcc jusrisdiction)to configure things Manually(even temporally to troubleshoot/locate "issues" with links).

PtDragon · Sat Jul 30, 2016 5:40 am

How radar detect works at all?
How to disable restriction because i don't want it shut the signal in case it senses something that can be not a radar?
Or now for AP i'm stuck with pre-enforcment version forever?

marekm · Sat Jul 30, 2016 11:02 am

Mikrotik, please don't force DFS on those who know what they're doing. I know the weather radar in my area (near GDN airport) is at 5650 MHz (confirmed by spectral scan - high narrow peak visible), and I never use channels 128 and 132. DFS disabled, no false positives, no downtime on each wireless settings change, no harm to and from the radar (it works both ways, our 1W vs their 250kW). Mostly UBNT radios so far, but I was considering using more MT radios because of your (until now) less restrictive policy.

Bigfoot · Sat Jul 30, 2016 11:14 am

Hi
look like the Ping is not working, On 6.36 it works and on 6,37rc10 not.
Can someone please confirm,

MartijnVdS · Sat Jul 30, 2016 2:10 pm

Mikrotik, please don't force DFS on those who know what they're doing. I know the weather radar in my area (near GDN airport) is at 5650 MHz (confirmed by spectral scan - high narrow peak visible), and I never use channels 128 and 132. DFS disabled, no false positives, no downtime on each wireless settings change, no harm to and from the radar (it works both ways, our 1W vs their 250kW). Mostly UBNT radios so far, but I was considering using more MT radios because of your (until now) less restrictive policy.

You can still make a scan-list with those frequencies excluded, and set the AP to a frequency that's free of radar. DFS shouldn't detect radar on the other frequencies, and not initiate a channel switch.

InoX · Sat Jul 30, 2016 6:03 pm

!) wireless - DFS option is removed and forced to "dfs=radar-detect";

I have replaced all ubnt radios with mikrotik because of this. Now I will stick to 6.36.
There is a 10min wait time in 5600-5650Mhz and 30min wait time if radar detected.
Good luck!

npero · Sat Jul 30, 2016 6:34 pm

!) wireless - DFS option is removed and forced to "dfs=radar-detect";
I have replaced all ubnt radios with mikrotik because of this. Now I will stick to 6.36.
There is a 10min wait time in 5600-5650Mhz and 30min wait time if radar detected.
Good luck!

I not try yet, but if change mode to superchannel and country to no_country DFS is also active ? In my logic must be disabled because no country selected.

lekozs · Sat Jul 30, 2016 6:44 pm

Mikrotik, please don't force DFS on those who know what they're doing. I know the weather radar in my area (near GDN airport) is at 5650 MHz (confirmed by spectral scan - high narrow peak visible), and I never use channels 128 and 132. DFS disabled, no false positives, no downtime on each wireless settings change, no harm to and from the radar (it works both ways, our 1W vs their 250kW). Mostly UBNT radios so far, but I was considering using more MT radios because of your (until now) less restrictive policy.

OK...
...is there anybody here, with greater knowledge, who can explain to me, how on earth a 200mW radio, made by MikroTik, could cause interference to a - more than one million times stronger - 250,000W Radar?!?

Cha0s · Sat Jul 30, 2016 6:53 pm

It would be nice if Mikrotik explained why they introduce (or to be more accurate, remove) features without any apparent reason.

They did it with dynamic entries on 6.36 in address lists (no explanation whatsoever) and now with DFS (again, no explanation whatsoever) despite many users opposing to those changes.

Especially with address lists, they had plenty of time and complaints to revert it during the RC phase but they completely ignored everyone.

Are they trying to stop us from upgrading to newer versions or what?!

Not giving explanations about these moves doesn't help anyone. People that use Mikrotik and Routerboards do it because they know what they want.
It's not some locked down/backdoored ZTE modem-router-coffee maker that our ISP pushed down our throats.
We select this software/hardware for a reason. Mikrotik has to be more transparent to its clients... if they care to keep them that is.

Sob · Sat Jul 30, 2016 7:29 pm

... how on earth a 200mW radio, made by MikroTik, could cause interference to a - more than one million times stronger - 250,000W Radar?!?

In short, radars are very sensitive. They send strong pulses and listen for much weaker reflected signals. Tiny radios are no match for them when it comes to transmitting power, but they can be stronger than reflected signals. And that's a problem, because it confuses radars. They are getting better at filtering wifi signals, but it's not perfect and probably never will. Unfortunately for wifi users, radars are considered to be primary users of these frequencies. So MikroTik probably has no choice, other than force radar detection where required, otherwise regulators would kick their asses...

IntrusDave · Sat Jul 30, 2016 7:32 pm

If you understand a bit more about DFS, and understand that many countries will ban ALL of a company's products if they do not comply - maybe you will not be so upset about it. Weather and Air Traffic radar covers a lot more area than many people think.

Dynamic Frequency Selection
DFS is a spectrum-sharing mechanism that allows wireless LANs (WLANs) to coexist with radar systems. It automatically selects a frequency that does not interfere with certain radar systems while operating in the 5 GHz band. DFS is a feature of ETSI BRAN HIPERLAN/2 and IEEE Standard 802.11h.

Overview
In some regions (predominantly Europe), it is important to ensure that WLAN equipment does not interfere with certain radar systems that are the primary users in the 5 GHz band. The DFS feature of the AP software searches for radar pulses in the frequency channel where it is operating, or during the autochannel scan. It constantly monitors errors in the received frames and analyzes the timing patterns for periodicity. If the pattern matches a radar signal, it instructs the WLAN equipment to discontinue operation on that channel as quickly as possible. The WLAN equipment reboots, then begins to operate on another frequency after checking that the new frequency is free of radar signals.

Operation
DFS detects radar interference and moves the wireless network to another frequency with no interference. It maintains a list of channels where radar has been detected in the NOL (non-occupancy list). The AP avoids using these channels for at least 30 minutes after detecting radar on them. When DFS is enabled, the AP:

Looks for radar detection before securing a frequency channel.
Scans continuously for radar signal patterns during normal operation.

Radar Signal
A conventional radar signal is a burst of pulses of a high frequency signal. When one burst is over, it is repeated after some duration, called sweep time. ITU has defined several different types of radar based on different frequencies, the number of pulses in a burst, and pulse repetition frequency within the burst. The sweep time is a result of radars that slowly rotate through 360 degrees, so that in a 30-second sweep period, the AP may be hit by the radar signal only for fraction of a second. During this hit, the AP sees a few pulses separated by a time interval (called the period), which is anywhere from 250 microseconds to 20 milliseconds. Each pulse can be 2 microseconds or smaller in width.

diode · Sat Jul 30, 2016 7:37 pm

Hi Mikrotik Gurus,

Is the radar scan active for all channels 100-140 (5500-5700), or just for 120-128 (5600-5640) ? What about channel 52 - 64 ?

will the dfs change also be in 6.36.1 ?

thanks maria !

IntrusDave · Sat Jul 30, 2016 7:37 pm

In short, radars are very sensitive. They send strong pulses and listen for much weaker reflected signals. Tiny radios are no match for them when it comes to transmitting power, but they can be stronger than reflected signals. And that's a problem, because it confuses radars. They are getting better at filtering wifi signals, but it's not perfect and probably never will. Unfortunately for wifi users, radars are considered to be primary users of these frequencies. So MikroTik probably has no choice, other than force radar detection where required, otherwise regulators would kick their asses...

Well stated.
To add to this - Apple has pulled all of their Wireless routers from stores, as the FCC deadline for DFS was July 1.

IntrusDave · Sat Jul 30, 2016 7:39 pm

Hi Mikrotik Gurus,

Is the radar scan active for all channels 100-140 (5500-5700), or just for 120-128 (5600-5640) ? What about channel 52 - 64 ?

will the dfs change also be in 6.36.1 ?

thanks maria !

Most of the world requires it on 50~144
https://en.wikipedia.org/wiki/List_of_W ... 29.5B17.5D

napismizpravu · Sat Jul 30, 2016 9:07 pm

DFS permanently switched > motivation hack outside the system RouterOS = DFS deactivate + license free

MikroTik lost money or it is well secured antihack, autodestruct routerboard (Inspiration agent 007)?

[Google translate]

InoX · Sun Jul 31, 2016 12:30 am

Who cares about x86 and wireless + DFS?

MaHr · Sun Jul 31, 2016 1:27 am

Hi,
I'm trying to test this release and it worked, but I am afraid, that if superchannel option it will be still available, that is it same as DFS-mode=none. For meaningfull use of this feature, must be superchannel feature removed, I think. By the way, radar detecting function working fine. If radar is present in the antenna direction, that is detected and radar channel isn't used for exact time and use next free frequency channel.

But I still get problem with wireless snooper via console, if I run command:
[admin@MikroTik] /interface wireless> snooper snoop wlan1
CHANNEL                           USE        BW NET-COUNT NOISE-FLOOR STA-COUNT
5560/20/a/DP                       0%      0bps         0        -111         0
5580/20/a/DP                       0%      0bps         0        -111         0
5600/20/a/DP                     0.1%   8.8kbps         1        -112         1
5620/20/a/DP                       0%      0bps         0        -112         0
-- [Q quit|D dump|C-z pause|n networks|s stations|down]

and press s I can see station, but without used frequencies

Flags: A - active, N - access-point
#       FREQ ADDRESS           SIG SNR OF-FREQ OF-TRAF        BW SSID
0 AN         00:1E:DA:EE:AE:DA -92 20      0%     50%   4.5kbps XXXXXXX
1 A          00:0C:42:7A:C9:BD -90 22    0.2%    8.2%   8.0kbps
2 A          4C:5E:0C:84:ED:99 -90 22    1.3%   46.8% 50.1kbps
3 A          4C:5E:0C:82:6D:E1 -85 27    0.2%    9.8%   9.6kbps
-- [Q quit|D dump|C-z pause|n networks|s stations|down]

or if I press n as networks list is still without frequencies:

#        FREQ ADDRESS           SSID            STAS OF-FREQ OF-TRAF        BW
0 AFB         00:1E:DA:EE:AE:DA XXXXXXX            1    0.1%    100%   9.2kbps
-- [Q quit|D dump|C-z pause|n networks|s stations|down]

I think, that it worked fine in version 6.19. In column FREQ was frequency presented s ie. 5600MHz, now values are missing, but we are using this for getting automatic information about frequencies of clients and APs. Now we are without this information due this small bug.
Many thanks for solved this.
Martin

diode · Mon Aug 01, 2016 2:51 pm

Are there any mikrotik DFS long time users around ?

does the inband monitoring of radar sometimes dedect radars just cause of the damaged pakets a weak link is transmitting on mikrotik ?

damaged pakets -> could be radar pulses -> radar dedected, even if not present

back in 2003, 2004 exactly that was the main problem with DFS, making 5 GHz praktically unusable with Lancom devices. After a few hours radar was dedected on all channels, and link went down. only practical solution was moving to a DFS free country. Since then I dont have any DFS experiences.

BTW, weather radars in austria
5625 Rauchenwarth,NÖ
5600 Feldkirchen,OÖ
5640 Zirbitzkogel,Stmk
5625 Patscherkofel,T
5610 Valluga, T

Weather radar is on channels 120-128 nearly worldwide, in europe you need to stay away from these channels based on DFS2, practically you definitly should if you don't have a channel list of the radars of your country ...

The other radars, that could be theoretically on any channel in austria are from the military, but the austrian military also has the 5,8 GHz ISM band nearly completly alone, besides many other bands.

BW

visalink · Mon Aug 01, 2016 5:05 pm

please do not include DFS permanently switched in version 6.36.x, probably this will be my last updated.

notToNew · Mon Aug 01, 2016 5:26 pm

Hm, missing the changelog for rc11?!?

pe1chl · Mon Aug 01, 2016 9:07 pm

with "radar-detect" enabled will end in endless frequency search loop, even when there is realy no radar
That is not true. All countries in the EU, and the USA should have already been using this setting for a long time, and there are no problems like you describe.

If that was true...
We have MikroTik AP in use on a 220m AGL site and the DFS is not stable!
We know the frequency of the local weather radar but when we set the MikroTik to free channel choice and DFS it is
only hopping around and the connection is lost every minute. It never finds a channel where it will stay. With DFS off
and a properly chosen channel (far away from the radar) it works OK.
This means (like others have written) we will no longer be able to update past the 6.36 version...

Zorro · Mon Aug 01, 2016 9:57 pm

with "radar-detect" enabled will end in endless frequency search loop, even when there is realy no radar
That is not true. All countries in the EU, and the USA should have already been using this setting for a long time, and there are no problems like you describe.
If that was true...
We have MikroTik AP in use on a 220m AGL site and the DFS is not stable!
We know the frequency of the local weather radar but when we set the MikroTik to free channel choice and DFS it is
only hopping around and the connection is lost every minute. It never finds a channel where it will stay. With DFS off
and a properly chosen channel (far away from the radar) it works OK.
This means (like others have written) we will no longer be able to update past the 6.36 version...

in such cases - most customers HAD TO stick with legacy firmware thus.
atleast UNTIL MikroTik improve radar-detection, of course.
thats quite common situation, btw.
even in complteletely radar-free rural areas(say 1200km away from closest industrial instalalation and ~450km from closest (tiny)airport(without radars of Any kind, including weather))its may perform quite jerky and and in urban areas... oh god, its like circus in all-brands routers (not only SOHO gear suffer).
my point is: its perhaps too early move. unsafe, yet to Enforce that. just opinion.

UsernameMT · Tue Aug 02, 2016 6:58 am

up

http://forum.mikrotik.com/viewtopic.php ... 01#p548501
http://forum.mikrotik.com/viewtopic.php ... 57#p549357

hknet · Tue Aug 02, 2016 7:20 am

What is the business reason to force the DFS on? Mikrotik should explain it really in details. There are rules that when radar is detected, the Ap should lower its tx power, sometimes, so there is not really necessary to leave the frequency. When radar is stopped, it can revert the tx power back to previous legal limit. How this is supported?

What if I take care about the weather radars and have already my radios correctly set from the real tx power point of view and positively know that they do not have any influence on the weather radars... Why the link should be dropped down just due to false positive radar detection? To whom it helps?

The business reason is simply to stay in business within the EU and USoA. Lots of wireless ISPs were/are using frequencies without taking care of other services running in the same frequency spectrum, therefore legislation is now enacted that wireless devices without frequency protection enforcing will be removed from the markets.
Kindest Regards,
hk

Tue Aug 02, 2016 9:06 am

To everyone talking about DFS.

If your country has no DFS rules, RouterOS will not do anything. Each country has separate DFS config defined.
If you have some special permission to use the radar frequencies, or there is some other reason you need to turn off DFS and not follow the rules, upon your own risk - don't set a country, or use wireless mode "superchannel".

Tue Aug 02, 2016 9:10 am

Maybe true but just a speculation. Mikrotik should give real official statement to this. There are already hardlocked device versions for USA and there is also a customizable locker tool available at mikrotik website so dealers can lock devices they are selling to special wireless parameters to fulfil local regulations before the devices are sold. There is no obvious reason to make problems to everyone as many of us wrote here.

So my question again: To whom it helps?

Tue Aug 02, 2016 9:12 am

so dealers can lock devices

Can, but don't. Many dealers don't want to install anything, this way, the process is much simplified.
All devices follow local regulations, if the user sets their country. If the user has reasons to use custom settings, they can use "superchannel". Everyone wins.

Tue Aug 02, 2016 9:15 am

To everyone talking about DFS.

If your country has no DFS rules, RouterOS will not do anything. Each country has separate DFS config defined.
If you have some special permission to use the radar frequencies, or there is some other reason you need to turn off DFS and not follow the rules, upon your own risk - don't set a country, or use wireless mode "superchannel".

Thank you at least for this.

My previous post was send simultaneously with yours...

How could I switch the DFS on even if it is not mandatory when you fully remove that option...?

IntrusDave · Tue Aug 02, 2016 9:16 am

I think Normis' response was pretty clear. Each country has rules that much be followed, if the products are to be sold in that country. *MOST* countries require DFS in the UNI-II channels. I don't understand why this is a problem for so many people. If you don't want to use DFS, use channels that do not require DFS.

IntrusDave · Tue Aug 02, 2016 9:22 am

How could I switch the DFS on even if it is not mandatory when you fully remove that option...?

I believe Czech Republic is enabled on all channels

/interface wireless info country-info "czech republic" 
  ranges: 5725-5875/a,an20,an40,ac20,ac40,ac80,ac160(14dBm)
          2402-2482/b,g,gn20,gn40(20dBm)
          2417-2457/g-turbo(20dBm)
          5170-5250/a,an20,an40,ac20,ac40,ac80,ac160(20dBm)/passive
          5250-5330/a,an20,an40,ac20,ac40,ac80,ac160(23dBm)/passive
          5490-5710/a,an20,an40,ac20,ac40,ac80,ac160(27dBm)/passive
          5190-5310/a-turbo(20dBm)
          5180-5300/a-turbo(20dBm)
          5520-5680/a-turbo(27dBm)/passive
          5510-5670/a-turbo(27dBm)/passive
          902-927/b,g,g-turbo,gn20,gn40(30dBm)

Zorro · Tue Aug 02, 2016 9:32 am

Maybe true but just a speculation. Mikrotik should give real official statement to this. There are already hardlocked device versions for USA and there is also a customizable locker tool available at mikrotik website so dealers can lock devices they are selling to special wireless parameters to fulfil local regulations before the devices are sold. There is no obvious reason to make problems to everyone as many of us wrote here.

So my question again: To whom it helps?

well just above janisk clearly explained that already i think.
but be aware that setting country/mode, other than actual - you're breaking law and subject of fines/penalties or even inprisonment in most countries.
its ironical that most installations that violate radar scan option(sometimes even with "modded firmware". which isn't simle for SOHO gear, consisting notable percentage in such)are in education and healthcare in EU. and as for disabling DFS whatsoever - its more NA thing(especially in USA), i guess cuz bogus bands/channel list, not recoginised/interoperable with by many devices with DFS enabled.

IntrusDave · Tue Aug 02, 2016 9:48 am

Most devices in the the USA simple don't support the UNI-II channels. Apple recently pulled all of it's wireless routers from retail and online sales because they did not comply with the new FCC rules. On the other hand, because the notebooks may travel the world, they support every channel that that the hardware in them can use. Personally, I use Channel 100 (5500MHz). I use it because no one anywhere near me has hardware that supports it. I also know that the airport that is 5 miles south of me is between 5600 and 5700.

I think most wireless guys should have an analyzer. The Metageek WiSpy is a great package and will let you visualize radar or any other signals in the 2.4 and 5G range.

docmarius · Tue Aug 02, 2016 11:18 am

6.37.rc11:
I confirm NTP is working correctly as a stand alone time source with a GPS receiver.

Good job MT Team

Tue Aug 02, 2016 1:37 pm

v6.37rc11 was released!

What's new in 6.37rc11 (2016-Aug-01 09:00):

>>> IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

>>> IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Changes since 6.37rc10:

*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424);
*) log - logs loaded from disk after reboot didn't have correct topics;
*) lte - fixed band setting for sxt lte;
*) lte - process initial state change to deregistred, when lockup occurs;
*) lte - reset if sms storage set fails;
*) modem - added d-link dwm-222 support;
*) modem - added logging for usb config switching;
*) ntp - fixed ntp server when local-clock used (like usb gps module);

pe1chl · Wed Aug 03, 2016 4:41 pm

To everyone talking about DFS.

If your country has no DFS rules, RouterOS will not do anything. Each country has separate DFS config defined.
If you have some special permission to use the radar frequencies, or there is some other reason you need to turn off DFS and not follow the rules, upon your own risk - don't set a country, or use wireless mode "superchannel".

Ok but the problem is not that we would not want to use DFS, the problem is that DFS is so unpredictable and/or can be unstable.
This is not a MikroTik-specific thing, we have also observed this on Ubiquiti and TranZeo equipment.
Apparently the detection is misled, or the receiver is overdriven by a Radar on one channel even when it is receiving on another.
Maybe the DFS code could have more debugging info. E.g. in TranZeo it is possible to see on what channels radar was detected,
how many times on each channel, and when last. (this table is only kept between reboots)
This way it is possible to investigate problems and maybe send them to MikroTik, to see what can be done to overcome the problem.

korniza · Thu Aug 04, 2016 11:41 am

I face the following problem on RB2011UiAS running v6.37rc10: ping tool using gui did not run and there is an error "Error: No Address".
I use winbox 3.4. Does anyone face the same issue?

Thu Aug 04, 2016 3:32 pm

As MT now apperently try to be more compliant ... where is ATPC? The main competition does it now. It is a valuable feature with micro cells as it is a very good idea to turn down TX-Power on CPEs which are very close to the AP. Not doing ATPC we have to turn down power to 27db EIRP in 5.5 and 24 in 5.8.

slav0nic · Fri Aug 05, 2016 12:43 pm

rc11, hap ac, in Webfig - Quicksetup 2Ghz wifi setting Frequency list have only 5180-5765 values

Fri Aug 05, 2016 12:46 pm

What's new in 6.37rc12 (2016-Aug-05 05:31):

>>> IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

>>> IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Changes since 6.37rc11:

*) defconf - fixed default configuration when wireless package is used;
*) package - fixed upgrade to 6.37 from older RouterOS versions where multiple wireless packages were included in bundle "routeros" package;
*) ping - fixed freezing on "not running" interfaces;
*) winbox - fixed ping tool (introduced in 6.37rc1);
*) wireless - improved driver support for RB953, hAP ac, wAP ac;
*) wireless - send deauth to data frames in scan mode;

lekozs · Fri Aug 05, 2016 1:24 pm

To everyone talking about DFS.

If your country has no DFS rules, RouterOS will not do anything. Each country has separate DFS config defined.
If you have some special permission to use the radar frequencies, or there is some other reason you need to turn off DFS and not follow the rules, upon your own risk - don't set a country, or use wireless mode "superchannel".
Ok but the problem is not that we would not want to use DFS, the problem is that DFS is so unpredictable and/or can be unstable.
This is not a MikroTik-specific thing, we have also observed this on Ubiquiti and TranZeo equipment.
Apparently the detection is misled, or the receiver is overdriven by a Radar on one channel even when it is receiving on another.
Maybe the DFS code could have more debugging info. E.g. in TranZeo it is possible to see on what channels radar was detected,
how many times on each channel, and when last. (this table is only kept between reboots)
This way it is possible to investigate problems and maybe send them to MikroTik, to see what can be done to overcome the problem.

I agree with @pe1chl !

Here are my findings...
I put a BaseBox 5 with a 16dBi dual pol sector antenna on a 12 story building just to play with this DFS thing...
Updated the device to v6.36 together with the wireless-rep package, and opened up the scan-list to the _complete_ 5GHz range EXCEPT the known radar frequencies (5600-5660MHz)
I turned on the DFS with radar-detect... and... this is what I got:

Note: there are NO active users on this AP!
I am sure this area is NOT radar-infested, (I'm from a poor country... the government can't afford radars here...

)
...however, as you can see, the RB is practically unusable. It always sees some phantom radar, and searches for another "clean" frequency...
I am standing by those people who are asking NOT to force the DFS with radar-detect on...

pe1chl · Fri Aug 05, 2016 2:26 pm

Ok in the above I see the DFS actions apparently are logged, I did not remember that from our DFS
experiments (where the only thing I was chasing was that I lost the connection every couple of minutes
and when it came back we were on a different frequency all the time).
So that part of my request can be disregarded, although maybe some debug values could be added when
available from the hardware (like the strength of the detected radar, and/or the impulse length?).

Zorro · Sat Aug 06, 2016 9:40 pm

generally i noticed that in last versions(last ~5 major versions or so)of ROS6 port-scan detection stopped working :/ thats not good, IMO.
also it think both DFS and especially radar-detection - should be bit more careful and slower(extra-math behind decision-making would make sense).

diablothebest · Mon Aug 08, 2016 8:32 am

We have strange problem with NAT.
We have big PS4 net behind nat, and peoples plays togather in Destiny!
But after 6.36 and 6.37 they cant connect to another players. Port used by this game is UDP 3074. Im create filter rule to forward this port and looks fine now. We dont have any block rule for udp.

UsernameMT · Mon Aug 08, 2016 10:13 am

http://forum.mikrotik.com/viewtopic.php ... 50#p550398
I can not use the 10 devices, because waiting the working firmware. WHEN?

Mon Aug 08, 2016 1:34 pm

http://forum.mikrotik.com/viewtopic.php ... 50#p550398
I can not use the 10 devices, because waiting the working firmware. WHEN?

It's a bit weird to see complains like this in a topic dedicated to a test version of software. And yes, I followed your other links, and all of them appear to be talking about 6.37rc. The RC versions are only made available for testing purposes, you are NOT supposed to be using these in production, so what 10 devices that you cannot use you are talking about?

Mon Aug 08, 2016 2:19 pm

What's new in 6.37rc13 (2016-Aug-08 07:39):

>>> IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

>>> IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Changes since 6.37rc12:

*) disk - do not do unnecessary sector writes;
*) lte - added initial deregistration only for bandrich modems;
*) partitions - added ability to add comments;
*) partitions - fixed crash on repartition when there is not enough free space;
*) usb - added support for SMSC95XX USB Ethernet dongle on mipsbe;
*) webfig - allowed user password changing (broken in v6.36);

UsernameMT · Mon Aug 08, 2016 4:16 pm

It's a bit weird to see complains like this in a topic dedicated to a test version of software. And yes, I followed your other links, and all of them appear to be talking about 6.37rc. The RC versions are only made available for testing purposes, you are NOT supposed to be using these in production, so what 10 devices that you cannot use you are talking about?

in my post:
http://forum.mikrotik.com/viewtopic.php ... 57#p549357
i write - "in version 6.36"
version 6.36 - "6.36 (Current)"
please tell me, what topic to write bugs version 6.36 Current, I duplicates my posts in this topic.

PS: for MTteam: if I did write in the wrong topic, you just ignored me, could not say where i need write about the problem?!!
PPS: I had never imagined that the topic "[current] is released" can continue the discussion of bugs!

notToNew · Mon Aug 08, 2016 4:55 pm

And just because of this you think you can not run your devices?
You can check in the script itself to see it the domain is already in the list....

Mon Aug 08, 2016 5:27 pm

please tell me, what topic to write bugs version 6.36 Current, I duplicates my posts in this topic.
PS: for MTteam: if I did write in the wrong topic, you just ignored me, could not say where i need write about the problem?!!
PPS: I had never imagined that the topic "[current] is released" can continue the discussion of bugs!

Is your router unusable with working old configuration applied when it uses IP not domain names ?

If yes then you have 10 unusable devices.

You have switched to new funcionalities and you are complaining about it.
Yes, it could be irritating that configuration with DNSes does not work same way as with IP but it does not make your router unusable despite fact that DNS names lists seem to work different that IP ones.

Chupaka · Mon Aug 08, 2016 5:40 pm

by the way, in current RC you cannot add duplicate domain names too

EDinATL · Mon Aug 08, 2016 7:26 pm

I had some trouble accessing the rc13 just now via the winbox system packages, so I just downloaded it from the site and all is fine so far. Other than that, I just wanted to say thanks for all the work and time you guys are putting in! Much love from Atlanta, GA, USA!

John39 · Mon Aug 08, 2016 11:24 pm

I have a few in stock mikrotik rb 2011, only one of them when you install any version 6,37 rc wireless interface disappear, what would that do to avoid it. Removing packages, endless flashing does not help, at 6.36 on the site interface.

IntrusDave · Tue Aug 09, 2016 7:07 am

Bug: MIKROTIK-MIB-mtxrHlProcessorFrequency (SNMP Processor Frequency) reads 0 on the RB3011

Tue Aug 09, 2016 9:26 am

where i need write about the problem?!!

support@mikrotik.com

UsernameMT · Tue Aug 09, 2016 11:36 am

where i need write about the problem?!!
support@mikrotik.com

Thank you so much!

Why then created it ?:
http://forum.mikrotik.com/viewtopic.php?f=21&t=110425
http://forum.mikrotik.com/viewtopic.php?f=21&t=110419

PS: замечательно, начерта темы форума созданы тогда? я описал явный БАГ прошивки, который стыдно допускать даже (просто по невнимательности его сделали). И ппц исправлять его еще месяц мля (сначала ждал пока релизнеться сама прошивка, теперь жди пока они исправят элементарнейший баг в ней). Попробуй создай дублированных сотню тысяч записей, а потом ручками и глазками выбирай их и удаляй. Вообще до сего момента, не понимал почему ВЕЗДЕ (от слова ВООБЩЕ ВЕЗДЕ) хаят техподдержку микротика, ... теперь понял...

dash · Tue Aug 09, 2016 11:36 am

Hi guys, I want to report an issue with the capsman upgrade policy. I am currently running a ROS 6.37rc12 but this bug exists since the cap upgrade setting was introduced.

Bug description: When using 'require same version ' then caps act like having the 'suggest same version ' setting set,- and vice versa...
Example: With require same version i get a log entry: "upgrade failed, Provision as same version only suggested."

But It should be the other way around. Thanks for your great work. Keep it going...

John39 · Tue Aug 09, 2016 12:27 pm

Смотрю тут пишут по русски, поэтому рискну и я.
Есть у меня несколько микротиков rb2011, с прошивкой 6.36 проблем нет, однако при прошивке его прошивкой 6.37 пропадает беспроводной интерфейс, пакет установлен, интерфейса нет. Проблема только на одном, с остальными проблем нет.
Откатываешь на 6.36, все в порядке. Как побороть?

UsernameMT · Tue Aug 09, 2016 12:34 pm

Смотрю тут пишут по русски, поэтому рискну и я.
Есть у меня несколько микротиков rb2011, с прошивкой 6.36 проблем нет, однако при прошивке его прошивкой 6.37 пропадает беспроводной интерфейс, пакет установлен, интерфейса нет.
Откатываешь на 6.36, все в порядке. Как побороть?

по русски тут пишут, когда в гневе,

и не хватает английских слов, чтобы культурно изложить свои мысли, вопросу на русском навряд ли тут помогут, только англоязычное написание применяй. по поводу беспроводки, смотри выше, тут вроде в этой теме с первой страницы, озвучивают проблему и её решение
http://forum.mikrotik.com/viewtopic.php ... 99#p551539
сам не вникал, у меня Девайс3011, по этому не сталкивался, да и вообще тут один совет, не юзай RC используй только стабильные выпуски. Попробуй пользоваться форумом "форум наг ру", если решение существует, то там помогут.

Tue Aug 09, 2016 1:17 pm

Please DO use English ... not all understand what you are writing. Both of you.
If you do not know enough words in English to curse as you write then ... "speech is silver and silence is golden"

Tue Aug 09, 2016 1:32 pm

Проблема только на одном, с остальными проблем нет.

Check you firmware (bootloader) version. Try upgrading in case current-firmware and upgrade-firmware versions differ.

/system routerboard print
/system routerboard upgrade

Chupaka · Tue Aug 09, 2016 2:24 pm

Why then created it ?:
http://forum.mikrotik.com/viewtopic.php?f=21&t=110425
http://forum.mikrotik.com/viewtopic.php?f=21&t=110419

because it's just an announcements and there's a note on the bottom? "If you experience version related issues, then please send supout file from your router to support@mikrotik.com"

я описал явный БАГ прошивки, который стыдно допускать даже (просто по невнимательности его сделали)

я уже не говорю, что с таким "багом" address-lists существовали далеко не одну мажорную версию (с 2.9 по 6.??) - и всё было хорошо

И ппц исправлять его еще месяц

не исправлять, а дорабатывать новую функциональность, разве нет?

а то, что кто-то её начал использовать, самостоятельно допридумывав желаемое поведение и не проверив его на практике - ну так это у этого человека проблема с программированием, не надо его допускать к написанию скриптов, если его никто не контролирует

вот вы месяц ждёте доработки - вы ведь правда уже давно подправили свой скрипт, чтобы он корректно работал в текущих условиях?

Попробуй создай дублированных сотню тысяч записей, а потом ручками и глазками выбирай их и удаляй.

вы такой смешной. почему создавали записи скриптом, а удаляли вручную? клин клином вышибать надо. т.е. скриптом

Вообще до сего момента, не понимал почему ВЕЗДЕ (от слова ВООБЩЕ ВЕЗДЕ) хаят техподдержку микротика, ... теперь понял...

потому что люди не умеют читать, но имеют богатую фантазию и преувеличенные надежды на форум сообщества пользователей? хотя вопросительный знак, пожалуй, лишний

Tue Aug 09, 2016 2:33 pm

Chupaka's post at a glance .... "do not complain, do your work"

Chupaka .... молодец !!!

John39 · Tue Aug 09, 2016 3:04 pm

Check you firmware (bootloader) version. Try upgrading in case current-firmware and upgrade-firmware versions differ.

Version 3.33

diablothebest · Tue Aug 09, 2016 3:12 pm

Нифга тут коры начались!

Use script to remove all old entries!

UsernameMT · Tue Aug 09, 2016 4:51 pm

...

не с одним предложением твоим не поспорю

всё верно пишешь... но блин я могу переписать свои скрипты, добавив предварительную проверку уже имеющейся записи, но сотня тысяч таких записей будет идти ещё дольше, а она и так долго происходит и без этого

Кстати, использование возврата ошибки, это нормальная функциональность, которая и присутствует во всем остальном в том же микротике...
ну и опять мы приходим всё к тому же

, приделай костыли, так как это микротик....
по поводу удалять скриптом, я всё ещё придерживаюсь, что "производителю" проще/правильнее исправить свой косяк, чем мне костЫлить стандартный скрипт - к сожалению тут меня не переубедить.
Опять же, сейчас настроишь приспособившись к этой проблеме, а потом исправят, надумаешь перепрошить, и ппц, всё слетит и начнешь заного... нет уж ....
...писал конечно же, потому что, как обычно - наболело...

Мужик, с уважением к тебе.

PS: i stop talking.

Tue Aug 09, 2016 5:10 pm

@UsernameMT: Problem is already fixed in v6.37rc

nescafe2002 · Tue Aug 09, 2016 5:31 pm

Issue in auto update.. affected versions are 6.37rc12 and 6.37rc13.

[admin@MikroTik] /system package update> set channel=release-candidate 
[admin@MikroTik] /system package update> print 

error - contact MikroTik support and send a supout file (10)
[admin@MikroTik] /system package update> export 
# aug/09/2016 16:30:15 by RouterOS 6.37rc13
#
#error exporting /system package update

Edit:

Issue gone after reboot.. thanks raffav

Edit 2:

However, after opening 'System', 'Packages', 'Check For Updates' the issue is reintroduced:

Edit 3:

Without Winbox, the issue occurs after setting (and changing) channel:

[admin@MikroTik] > /system package update
[admin@MikroTik] /system package update> print
            channel: release-candidate
  installed-version: 6.37rc13
[admin@MikroTik] /system package update> set channel=release-candidate
[admin@MikroTik] /system package update> print
            channel: release-candidate
  installed-version: 6.37rc13
[admin@MikroTik] /system package update> set channel=current
[admin@MikroTik] /system package update> print
            channel: current
  installed-version: 6.37rc13
     latest-version: 6.36
             status: New version is available
[admin@MikroTik] /system package update> set channel=release-candidate
[admin@MikroTik] /system package update> print

error - contact MikroTik support and send a supout file (10)
[admin@MikroTik] /system package update>

Edit 4:

Issue is fixed within rc13 (external cause?)

raffav · Tue Aug 09, 2016 6:00 pm

Issue in auto update.. affected versions are 6.37rc12 and 6.37rc13.

[admin@MikroTik] /system package update> set channel=release-candidate 
[admin@MikroTik] /system package update> print 

error - contact MikroTik support and send a supout file (10)
[admin@MikroTik] /system package update> export 
# aug/09/2016 16:30:15 by RouterOS 6.37rc13
#
#error exporting /system package update

i get the same error but, after a while the system reboot and the new version show up

tested on on RB433, BASEBOX2 and CRS125

Thu Aug 11, 2016 2:14 pm

--- IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

--- IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Changes since 6.37rc13:

*) capsman - fixed upgrade policy;
*) capsman - report radio-name in registration table;
*) dns - allow to set query-server-timeout and query-total-timeout only greater than 0s;
*) dns - fixed lockup when dynamic dns server address 0.0.0.0 was received;
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424);
*) firewall - added additional matchers for firewall raw rules;
*) health - do not show psu and fan information for passive cooling devices;
*) sstp - allow to specify proxy by dns name;
*) sstp - fixed disconnects on transmit for multicore systems;
*) traffic-flow - allow ipv6 src address to be optional;
*) webfig - do not crash if radius server does not give out encryption keys;
*) winbox - added src-address field for traffic-flow target;
*) winbox - fixed disconnect when no windows were opened for a while in unsecure mode;
*) winbox - hide ethernet flow control settings for interfaces which does not support them;
*) winbox - make queue tree default queue type default-small;

John39 · Thu Aug 11, 2016 5:08 pm

Today, I installed a new version of the firmware , but my problem with the wireless interface is lost it does not solve .
Сегодня установил новую версию прошивки, однако моей проблемы с пропадающим беспроводным интерфейсом это не решает.

diablothebest · Thu Aug 11, 2016 5:47 pm

Так он у тебя вообще исчез?
Пробовал делать полный сброс без конфы?

John39 · Thu Aug 11, 2016 5:56 pm

Так он у тебя вообще исчез?
Пробовал делать полный сброс без конфы?

Да, совсем исчез, сброс делал без конфы, шил голый, все равно интерфейса нет.
Yes, absolutely disappeared , dumping did not confit, sewed naked, still no interface .

raffav · Thu Aug 11, 2016 5:58 pm

Hi,

i think is not fair to post using a non english language

Zorro · Thu Aug 11, 2016 6:13 pm

Hi,

i think is not fair to post using a non english language

"not make easier to communicate" maybe, "not fair" - definitely no.
having thousands of languages on Earth have nothing with "fairness". and "fairness" have nothing with "making sense".
its not sport or trade to care much about "fairness".
and if he/person was not fluent in English - its somewhat simpler to let them native language, than trying to understand them thru prism of google translate or whatever they tend to use.
after all - there was several ppl who still remember Russian language over there, even in Latvia.

patrick7 · Thu Aug 11, 2016 6:32 pm

Just ignore them, or they will continue posting in russian.

diablothebest · Thu Aug 11, 2016 8:56 pm

Can you try reflash your device with NetInstall tool?
Прошивал через НетИнсталл роутер?

John39 · Thu Aug 11, 2016 10:44 pm

Can you try reflash your device with NetInstall tool?
Прошивал через НетИнсталл роутер?

No.

John39 · Thu Aug 11, 2016 11:23 pm

Попробовал netinstall, интерфейса нет.
Tried netinstall, interface no.

Zorro · Fri Aug 12, 2016 1:12 am

Попробовал netinstall, интерфейса нет.
Tried netinstall, interface no.

try to downgrade ROS to say ROS 6.35, restart, install all "wireless, disable, all but "wireless-cm2", restart router, remove all but wireless-cm2 package. install ROS 6.36, install ensure that "wireless-rep was operational and enabled. if so - remove other packages, restart.
and now - try to upgrade to 637rc15, perhaps.

jondavy · Fri Aug 12, 2016 1:20 am

please add CCQ to CapsMan registration-table

John39 · Fri Aug 12, 2016 7:54 am

try to downgrade ROS to say ROS 6.35, restart, install all "wireless, disable, all but "wireless-cm2", restart router, remove all but wireless-cm2 package. install ROS 6.36, install ensure that "wireless-rep was operational and enabled. if so - remove other packages, restart.
and now - try to upgrade to 637rc15, perhaps.

Спасибо, но где я могу скачать ROS 6.35?
Thank you, but where I can download the ROS 6.35?

UsernameMT · Fri Aug 12, 2016 9:14 am

но где я могу скачать ROS 6.35?
Thank you, but where I can download the ROS 6.35?

http://www.mikrotik.com/download/archive

If reflash on older version will not help, write to technical support.
And write in "english language" only, otherwise all offended (ignore) if you do not use international "english language".

John39 · Fri Aug 12, 2016 10:08 am

try to downgrade ROS to say ROS 6.35, restart, install all "wireless, disable, all but "wireless-cm2", restart router, remove all but wireless-cm2 package. install ROS 6.36, install ensure that "wireless-rep was operational and enabled. if so - remove other packages, restart.
and now - try to upgrade to 637rc15, perhaps.

Попробовал сделать как вы сказали. Установил 6.35.4, беспроводных пакетов стало 2, один отключил, cm оставил, второй пакет не удаляется. Установил 6.36, все работает, установил 6.37.15, беспроводной интерфейс пропал.
I tried to do as you say. Installed 6.35.4, wireless packet was 2, one disabled, cm left, the second package is not removed. Installed 6.36 , it works , installed 6.37.15 , the wireless interface is missing.

Fri Aug 12, 2016 10:52 am

John39

I have already asked you to not use Russian. Please consider your behavior.

John39 · Fri Aug 12, 2016 12:47 pm

John39
I have already asked you to not use Russian. Please consider your behavior.

Я уверен что форум создан для помощи, о которой я и прошу и язык не должен являться препятствием для этого. Я вижу здесь много русскоязычных пользователей, более того, если вы не в курсе, то в Латвии большинство жителей разговаривает на русском языке, уверен, что русскоговорящим удобнее читать на русском языке, нежели читать кривой гугл перевод. Именно по этой причине я пишу по русски, но учитывая ваши требования я дублирую на английском языке, который в отличии от русского вы должны понимать. И еще, что б делать замечания другим, нужно быть идеальным самому, но как я вижу и вы тоже пишите на польском http://forum.mikrotik.com/viewtopic.php ... 85#p544985 .

I am sure that the forum is designed to help, which I ask, and the language should not be an obstacle to this. I see there are a lot of Russian-speaking users, moreover, if you do not know, the majority of residents in Latvia speaks in Russian, I am sure that Russian-speaking easier to read in Russian, rather than read the Google translation of the curve. It is for this reason that I am writing in Russian, but considering your demands I duplicate in the English language, which is in contrast to Russian, you need to understand. And yet, what would make remarks to others, you need to be perfect, but as I see you, too, write in Polish http://forum.mikrotik.com/viewtopic.php ... 85#p544985 .

Fri Aug 12, 2016 1:09 pm

A. I do read and understand Russian and it is not a problem for me.
B. I am using English on this forum.
C. Nobody is perfect but please translate my Polish text and you will see that I have written in Polish: This forum is in English language so please use it.
D. We have most of users not from Eastern Europe so please do not dazzle them with cyrillic alphabet ... what if Chinese users choose to use they iconic language or Middle East choose to write Arabic right to left ?
E. Please follow rules.

Fri Aug 12, 2016 1:14 pm

This is not a latvian forum. Only around 0,001% of the users here are from Latvia

nescafe2002 · Fri Aug 12, 2016 4:03 pm

@John39, could you try installing the wireless package from the "Extra packages" bundle manually?

John39 · Fri Aug 12, 2016 8:50 pm

@John39, could you try installing the wireless package from the "Extra packages" bundle manually?

I've done it , it does not solve the problem .

IntrusDave · Sun Aug 14, 2016 12:31 pm

hAP AC (internation) goes into a reboot loop when 6.37rc15 is installed.
Net install with 6.37rc15 continues the loop.
Net install with 6.36 boots stable.

Zorro · Sun Aug 14, 2016 2:08 pm

weird. then its must be something in router config, relate to wi-fi interface, preventing from properly exporting/upgrading it and transitioning to newer version.
and thus i presume it may be very interesting to MT to take a look into, considering possible impact on other customers.
downgrading bootloader to actual 3.31(where hell he get 3.33 ?)make sense or even trying to 3.22/3.23(depend platform).

nastitek · Mon Aug 15, 2016 2:28 am

HAP AC LITE

CPU 100% constant utilization
Winbox 3.4 cannot connect after a few hours - this may be due to high utilization
HotSpot settings keeps breaking - disabling dhcp for this interface until allowing LAN dhcp as its dhcp source/pool
LAN IP changes (under quickset) using recently added dhcp pool.

Mon Aug 15, 2016 11:39 am

What's new in 6.37rc16 (2016-Aug-15 07:48):

--- IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

--- IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Changes since 6.37rc15:

*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424);
*) l2tp - fixed kernel failure when fastpath handles l2tp packets;
*) switch - added comment field for CRS switch VLANs;
*) switch - fixed configuration reload on CRS switches;

palhaland · Tue Aug 16, 2016 8:41 am

issues found on v6.27rc16 (running on mAP lite)

Love the new version with only one wireless package!

However I found some issues

Wireless interface
/interface wireless connect-list does not work on virtual station. (on mAP2nd) When running with logging the network is listed (correct frequency), but the wireless interface claim that there is no network that satisfy the connect list.

Scripting
This code works in command line but not in script;

{
:local $scanList "scanList.csv"
:local wlanInterface "wlan1"
:local j [:execute {/interface wireless scan [find name=$wlanInterface] background=yes duration=5 rounds=1 save-file=$scanList;}]
}

Where as this code works in both command line and script:

{
:local $scanList "scanList.csv"
:local wlanInterface [/interface wireless find name="wlan1"]
:local j [:execute {/interface wireless scan $wlanInterface background=yes duration=5 rounds=1 save-file=$scanList;}]
}

update 17.08.2016: there are no issues with scripting, the reason why it did not work was because the variables used was only in the local scope, it has to be in the global scope

TonyJr · Tue Aug 16, 2016 6:20 pm

*) sstp - fixed disconnects on transmit for multicore systems;

Thank you for this fix - site-to-site VPN is now stable between a CCR1009-8G-1S-1S+-PC and a CRS109-8G-1S-2HnD with 6.37rc16. I had thought the problem was with my configuration, until I saw the changelog. The connection would previously disconnect every few minutes if under any load - Link Downs would often have numbers in the thousands, now it is 0.

TonyJr

Ulypka · Wed Aug 17, 2016 2:22 pm

After upgrade from v6.37rc10 to v6.37rc16 openvpn server dosn't work.

emils · Wed Aug 17, 2016 2:38 pm

Ulypka, please send supout.rif file to support@mikrotik.com

Ulypka · Wed Aug 17, 2016 9:19 pm

emils, I'm so sorry it was my mistake unrelated to ovpn.

Thu Aug 18, 2016 2:11 pm

What's new in 6.37rc19 (2016-Aug-18 06:46):

--- IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

--- IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Changes since 6.37rc16:

*) arm - show cpu frequency under resources menu;
*) arp - fixed crash that caused Ethernet frames to go out via wrong interface;
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424);
*) pppoe - fixed kernel crash caused by dial-on-demand when used with fastpath;

Thu Aug 18, 2016 3:41 pm

issues found on v6.27rc16 (running on mAP lite)

Love the new version with only one wireless package!

However I found some issues
Wireless interface
/interface wireless connect-list does not work on virtual station. (on mAP2nd) When running with logging the network is listed (correct frequency), but the wireless interface claim that there is no network that satisfy the connect list.

I was unable to reproduce this problem.
Please provide us more information on that and also the wireless debug logs. Also make sure you select the correct security-profile in the connect-list.

Thu Aug 18, 2016 3:46 pm

Is the [Ticket#2016081022001387] solved already in this rc?

Ciambot · Thu Aug 18, 2016 3:50 pm

--- IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Oh my God!

Thu Aug 18, 2016 3:52 pm

--- IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Oh my God!

If you are in some place where you can use the radar frequencies ... Use Superchannel mode and it won't matter

pe1chl · Thu Aug 18, 2016 3:59 pm

If you are in some place where you can use the radar frequencies ... Use Superchannel mode and it won't matter

The problem is not using the radar frequencies, the problem is the (mis?)detection of radar on other frequencies when
at a high site near to radar. Do you mean that when switching from "regulatory - domain" to "superchannel" you can
still turn off the DFS? And will this remain in place or will it be the next feature to go?

Fortunately we use separate routers and APs that are only bridge, so we can still update routers and keep APs on old firmware
until there is a good solution. As it is now, DFS does not work for us on SXT, Metal5 etc.

napismizpravu · Thu Aug 18, 2016 5:02 pm

6.37rc19 Do not use RB433UAH hide all interfaces wireless (winbox, web) ethernet random refresh, wireless no configuration (remembers previous settings, broadcasts), ....downgrade previous build 6.37rc15

Thu Aug 18, 2016 5:04 pm

6.37rc19 Do not use RB433UAH hide all interfaces wireless (winbox, web) ethernet random refresh, wireless no configuration (remembers previous settings, broadcasts), ....downgrade previous build 6.37rc15

Most likely your wireless package got disabled, this can sometimes happen if you have installed multiple wireless packages. No need to downgrade, just need to re-enable correct wireless npk.

napismizpravu · Thu Aug 18, 2016 5:21 pm

6.37rc19 Do not use RB433UAH hide all interfaces wireless (winbox, web) ethernet random refresh, wireless no configuration (remembers previous settings, broadcasts), ....downgrade previous build 6.37rc15
Most likely your wireless package got disabled, this can sometimes happen if you have installed multiple wireless packages. No need to downgrade, just need to re-enable correct wireless npk.

It's not this way
wireless packages activate build 6.37rc19 ( wireless AP view air)
build 6.37rc15 upgrade to 6.37rc19 > downgrade 6.37rc15 (works)

Thu Aug 18, 2016 5:30 pm

It's not this way
wireless packages activate build 6.37rc19 ( wireless AP view air)
build 6.37rc15 upgrade to 6.37rc19 > downgrade 6.37rc15 (works)

You most definately need to send supout.rif file from rc19 to support@mikrotik.com

napismizpravu · Thu Aug 18, 2016 5:55 pm

You most definately need to send supout.rif file from rc19 to support@mikrotik.com

macgaiver: why he wrote it? post+1? your is spamer

palhaland · Thu Aug 18, 2016 6:03 pm

issues found on v6.27rc16 (running on mAP lite)

Love the new version with only one wireless package!

However I found some issues
Wireless interface
/interface wireless connect-list does not work on virtual station. (on mAP2nd) When running with logging the network is listed (correct frequency), but the wireless interface claim that there is no network that satisfy the connect list.
I was unable to reproduce this problem.
Please provide us more information on that and also the wireless debug logs. Also make sure you select the correct security-profile in the connect-list.

This is with frequency set to auto on the ap-bridge

831	Aug/18/2016 16:38:04	memory	wireless, debug	wlan2: no network that satisfies connect-list, by default choose with strongest signal	
832	Aug/18/2016 16:38:04	memory	wireless, debug	wlan2: failed to select network	
833	Aug/18/2016 16:38:04	memory	wireless, debug	wlan2: must select network	
834	Aug/18/2016 16:38:04	memory	wireless, debug	empty

This is with frequency set to the correct frequency:

985	Aug/18/2016 16:41:21	memory	wireless, debug	<mac address>: on 2462 AP: yes SSID <correct network name> caps 0x1431 rates 0xCCK:11 OFDM:12-54 BW:1x SGI:1x HT:0-23 basic 0xCCK:11 MT: no	
986	Aug/18/2016 16:41:21	memory	wireless, debug	<mac address>: on 2462 AP: yes SSID <correct network name> caps 0x1431 rates 0xCCK:11 OFDM:12-54 BW:1x SGI:1x HT:0-23 basic 0xCCK:11 MT: no	
987	Aug/18/2016 16:41:21	memory	wireless, debug	<mac address>: on 2462 AP: yes SSID <different network name> caps 0x1431 rates 0xCCK:11 OFDM:12-54 BW:1x SGI:1x HT:0-23 basic 0xCCK:11 MT: no	
988	Aug/18/2016 16:41:21	memory	wireless, debug	<mac address>: on 2462 AP: yes SSID caps 0x1431 rates 0xCCK:11 OFDM:12-54 BW:1x SGI:1x HT:0-23 basic 0xCCK:11 MT: no	
989	Aug/18/2016 16:41:21	memory	wireless, debug	<mac address>: on 2462 AP: yes SSID caps 0x1431 rates 0xCCK:11 OFDM:12-54 BW:1x SGI:1x HT:0-23 basic 0xCCK:11 MT: no	
990	Aug/18/2016 16:41:21	memory	wireless, debug	wlan2: no network that satisfies connect-list, by default choose with strongest signal	
991	Aug/18/2016 16:41:21	memory	wireless, debug	wlan2: failed to select network	
992	Aug/18/2016 16:41:22	memory	wireless, debug	wlan2: must select network

# aug/18/2016 16:46:13 by RouterOS 6.37rc16
# software id = G2LP-VRHH
#
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-eC \
    disabled=no distance=indoors frequency=2462 mode=ap-bridge ssid=\
    MikroTik-149006 wireless-protocol=802.11
add disabled=no mac-address=<mac-address> master-interface=wlan1 mode=\
    station-pseudobridge name=wlan2
/ip neighbor discovery
set ether1 discover=no
/interface wireless security-profiles
add authentication-types=wpa-psk,wpa2-psk management-protection=allowed mode=\
    dynamic-keys name=profile1 wpa-pre-shared-key=<password> \
    wpa2-pre-shared-key=<password>
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp disabled=no interface=wlan1 name=defconf
/interface wireless connect-list
add interface=wlan2 security-profile=profile1 ssid=<network name>
/ip address
add address=192.168.88.1/24 comment=defconf interface=wlan1 network=\
    192.168.88.0
/ip dhcp-client
add comment=defconf dhcp-options=hostname,clientid disabled=no interface=ether1
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no \
    interface=wlan2
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 name=router
/ip firewall filter
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept established,related" \
    connection-state=established,related
add action=drop chain=input comment="defconf: drop all from WAN" in-interface=\
    ether1
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" \
    connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related" \
    connection-state=established,related
add action=drop chain=forward comment="defconf: drop invalid" connection-state=\
    invalid
add action=drop chain=forward comment=\
    "defconf:  drop all from WAN not DSTNATed" connection-nat-state=!dstnat \
    connection-state=new in-interface=ether1
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" out-interface=\
    ether1
/system clock
set time-zone-name=Europe/Oslo
/system logging
add topics=wireless,debug
/system routerboard settings
set cpu-frequency=650MHz protected-routerboot=disabled
/tool mac-server
set [ find default=yes ] disabled=yes
add interface=wlan1
/tool mac-server mac-winbox
set [ find default=yes ] disabled=yes
add interface=wlan1

By only adding the SSID to connect to and the security profile, it connects immediately
/interface wireless wlan2 set ssid=<wireless network> security-profile=profile1

voody77 · Thu Aug 18, 2016 6:23 pm

6.37rc19 Do not use RB433UAH hide all interfaces wireless (winbox, web) ethernet random refresh, wireless no configuration (remembers previous settings, broadcasts), ....downgrade previous build 6.37rc15
Most likely your wireless package got disabled, this can sometimes happen if you have installed multiple wireless packages. No need to downgrade, just need to re-enable correct wireless npk.

At start hap ac wireless interfaces is work. run 2-5 minuts - result: hide all wireless interfaces in inbox menu on 6.37rc19 and networks not working!

raffav · Thu Aug 18, 2016 6:36 pm

6.37rc19 Do not use RB433UAH hide all interfaces wireless (winbox, web) ethernet random refresh, wireless no configuration (remembers previous settings, broadcasts), ....downgrade previous build 6.37rc15

for me is ok

[raffaello@RJ-AT-MK02 - CAP1] > interface wireless print without-paging 
Flags: X - disabled, R - running 
 0 X  ;;; COMERCIAL --- wireless
      name="Wap45_comercial" mtu=1500 l2mtu=1600 mac-address=02:15:6D:68:40:71 arp=enabled interface-type=virtual master-interface=wlan1 mode=ap-bridge ssid="comercial_answer" vlan-mode=no-tag vlan-id=1 
      wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=no default-forwarding=no default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no 
      security-profile=comercial_answer 

 1 X  ;;; DIRETORIA --- wireless
      name="Wap75_diretoria" mtu=1500 l2mtu=1600 mac-address=02:15:6D:68:40:74 arp=enabled interface-type=virtual master-interface=wlan1 mode=ap-bridge ssid="diretoria_answer" vlan-mode=no-tag vlan-id=1 
      wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no 
      security-profile=diretoria_answer 

 2 X  ;;; LOGISTICA --- wireless
      name="Wap85_logistica" mtu=1500 l2mtu=1600 mac-address=02:15:6D:68:40:70 arp=enabled interface-type=virtual master-interface=wlan1 mode=ap-bridge ssid="logistica_answer" vlan-mode=no-tag vlan-id=1 
      wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no 
      security-profile=logistica_answer 

 3 X  ;;; VISITANTE --- wireless
      name="Wap145_visitante" mtu=1500 l2mtu=1600 mac-address=02:15:6D:68:40:6F arp=enabled interface-type=virtual master-interface=wlan1 mode=ap-bridge ssid="visitante_answer" vlan-mode=no-tag vlan-id=1 
      wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no 
      security-profile=visitante_answer 

 4 X  ;;; MOBILE-RJ --- wireless
      name="Wap146_mobile-rj" mtu=1500 l2mtu=1600 mac-address=02:15:6D:69:38:B0 arp=enabled interface-type=virtual master-interface=wlan1 mode=ap-bridge ssid="answer_mobile" vlan-mode=no-tag vlan-id=146 
      wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no 
      security-profile=mobile_answer 

 5 X  ;;; TI --- Wireless
      name="Wap155_TI" mtu=1500 l2mtu=1600 mac-address=02:15:6D:68:40:75 arp=enabled interface-type=virtual master-interface=wlan1 mode=ap-bridge ssid="TI_answer" vlan-mode=no-tag vlan-id=155 wds-mode=disabled 
      wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no security-profile=TI_answer 

 6 X  ;;; TI --- Wireless Mobile
      name="Wap156_MOBILE" mtu=1500 l2mtu=1600 mac-address=02:15:6D:69:38:AF arp=enabled interface-type=virtual master-interface=wlan1 mode=ap-bridge ssid="W_TI" vlan-mode=no-tag vlan-id=1 wds-mode=disabled 
      wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=no default-forwarding=no default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=yes security-profile=TI_Mobile 

 7 X  ;;; managed by CAPsMAN
      ;;; channel: 2412/20/g(21dBm), SSID: diretoria_answer, CAPsMAN forwarding
      name="wlan1" mtu=1500 l2mtu=1600 mac-address=D4:CA:6D:14:01:F3 arp=enabled interface-type=Atheros AR5413 mode=ap-bridge ssid="answer_wireless" frequency=auto band=2ghz-b/g channel-width=20mhz 
      scan-list=default wireless-protocol=802.11 antenna-mode=ant-a vlan-mode=no-tag vlan-id=97 wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=disabled default-authentication=no 
      default-forwarding=no default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=yes security-profile=TI_answer compression=no

[raffaello@RJ-AT-MK02 - CAP1] > system package print 
Flags: X - disabled 
 #   NAME                                                                                         VERSION                                                                                        SCHEDULED              
 0   routeros-mipsbe                                                                              6.37rc19                                                                                                              
 1   system                                                                                       6.37rc19                                                                                                              
 2   ipv6                                                                                         6.37rc19                                                                                                              
 3   wireless                                                                                     6.37rc19                                                                                                              
 4   hotspot                                                                                      6.37rc19                                                                                                              
 5   dhcp                                                                                         6.37rc19                                                                                                              
 6   mpls                                                                                         6.37rc19                                                                                                              
 7   routing                                                                                      6.37rc19                                                                                                              
 8   ppp                                                                                          6.37rc19                                                                                                              
 9   security                                                                                     6.37rc19                                                                                                              
10   advanced-tools                                                                               6.37rc19

raffaello@RJ-AT-MK02 - CAP1] > system resource print 
                   uptime: 6m35s
                  version: 6.37rc19 (testing)
               build-time: Aug/18/2016 06:45:52
              free-memory: 104.7MiB
             total-memory: 128.0MiB
                      cpu: MIPS 24Kc V7.4
                cpu-count: 1
            cpu-frequency: 680MHz
                 cpu-load: 4%
           free-hdd-space: 492.1MiB
          total-hdd-space: 512.0MiB
  write-sect-since-reboot: 237
         write-sect-total: 45367767
               bad-blocks: 0.2%
        architecture-name: mipsbe
               board-name: RB433UAH
                 platform: MikroTik

napismizpravu · Thu Aug 18, 2016 6:53 pm

raffav I use „Extra packages” (all_packages...) the terminal I was not looking, important WinBox

raffav · Thu Aug 18, 2016 7:03 pm

raffav I use „Extra packages” (all_packages...) the terminal I was not looking, important WinBox

ok
so maybe the problem is on the extra packages, my winbox is ok too
I don't lost any wifi configuration or interfaces

Fri Aug 19, 2016 10:26 am

You most definately need to send supout.rif file from rc19 to support@mikrotik.com
macgaiver: why he wrote it? post+1? your is spamer

Cause only ones that can help you are reachable via that mail, to make sure that RC20 doesn't have this problem.

Fri Aug 19, 2016 11:18 am

What's new in 6.37rc20 (2016-Aug-19 06:35):

--- IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

--- IMPORTANT! DFS MODE CHANGES:

DFS mode setting is removed, and by default becomes forced to "dfs=radar-detect" for all
devices that use radar frequencies. If your client devices use a scan list with a few
specific frequencies that could conflict with radar frequencies, you could lose the
connection. It is recommended to widen the scan list range, use default scan list, or
change the AP frequency

Changes since 6.37rc19:

*) address-list - fixed crash (introduced in 6.37rc17);
*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424);
*) export - updated default values in /system routerboard settings menu;
*) sfp - enabled eeprom printout in /interface ethernet monitor;
*) sfp - removed "sfp-rate-select" as command was not relevant to currently supported hardware;
*) trafficgen - fixed crash (introduced in 6.37rc17);

pe1chl · Fri Aug 19, 2016 10:22 pm

*) snmp - added script table which executes script and returns it's output on get request;

Please explain how to use this feature, because I cannot find it in the user interface...

raffav · Fri Aug 19, 2016 11:06 pm

Very strange thing on a RB450G when I do a port knock using tcp the RB reset all interface and lost connection
using rc19 version

port knock is 2 top sequencie 2468 and 55027

can any one using rc19 tray to se if the rb crash

Zorro · Sun Aug 21, 2016 11:23 pm

there was presumed some changes in 3.34 bootloader ?

Thu Aug 25, 2016 10:18 am

What's new in 6.37rc21 (2016-Aug-25 06:15):

--- IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

--- IMPORTANT! DFS CHANGES:

DFS configuration in RouterOS has been redesigned, now device looks at specified country
settings (/interface wireless info country-info <country> ), and apply corresponding
DFS mode for each frequency range automatically, making dfs-mode setting unnecessary.

Please, check that your frequencies work with correcponding DFS settings before upgrade.

Changes since 6.37rc20:

*) dude - (changes discussed here: http://forum.mikrotik.com/viewtopic.php?f=8&t=110424);
*) hotspot - show comments from user menu also in active menu;
*) tunnel - ipv6 link-local address is now generated from tunnel local-address;
*) vlan - do not allow to add new vlan interface with mtu higher than l2mtu;
*) wireless - updated brazil country settings;

heaven · Thu Aug 25, 2016 12:17 pm

Hi Guys, I have 2 Mikrotik in my network (RB2011 & hAP AC Lite). All my routers have release candidate firmware. The RB2011 is a capsman controller and hap ac is a cap with 2 more virtual cap.
When RB2011 was restart after upgrade or another cause the cap in hap ac has registered new/dynamic wlan number in cap. It's very uncomfortably because I have some bridges and all each networks (wlans) uses different bridges.
For example.
on the hAP AC
Bridge -> Ports:
br1 - wlan0
br2 - wlan2
br3 - wlan3
Wireless by controller capsman:
wlan0 - general cap
wlan2 - 1st virtual cap
wlan3 - 2nd virtual cap

after restart of capsman controller (RB2011), cap (hAP AC) registered new wlans:
Wireless capsmann controlled:
wlan0 - general cap
wlan25 - 1st virtual cap
wlan26 - 2nd virtual cap.

in Bridge -> Ports
br1 - wlan0
br2 - unknown
br3 - unknown

how to solve this problem or maybe developer have a liitle time to do a static virtual caps wlans number?) Thanks.

raffav · Thu Aug 25, 2016 12:52 pm

Don't use dynamic enable
Use enable only

Enviado de meu XT1580 usando Tapatalk

heaven · Thu Aug 25, 2016 12:59 pm

Don't use dynamic enable
Use enable only

Enviado de meu XT1580 usando Tapatalk

wrong(. every time cap have a new number of virtual cap wlan on reconnect. if it's was be so easy i'm not write here. but thank you for your answer).

raffav · Thu Aug 25, 2016 1:22 pm

Don't use dynamic enable
Use enable only

Enviado de meu XT1580 usando Tapatalk
wrong(. every time cap have a new number of virtual cap wlan on reconnect. if it's was be so easy i'm not write here. but thank you for your answer).

Sorry, but sometimes is wrong there,
My cap number don't change when devices is rebooted

Edit:
Now I got it
I understand another Dynamic number [emoji57]

The caps number on the cap device it Is normal to increase ( Why need to be like that I don't know)

The trick is to use data path settings so the caps interface go to the correct bridge

Enviado de meu XT1580 usando Tapatalk

napismizpravu · Thu Aug 25, 2016 1:52 pm

info: RB433UAH this works build 6.37rc21 (all_packages...)
upgrade 6.37rc15 :>>> 6.37rc21

6.37rc19 no works

Thu Aug 25, 2016 1:56 pm

What's new in 6.37rc22 (2016-Aug-25 09:01):

--- IMPORTANT! WIRELESS PACKAGE CHANGES:

If you are not using "routeros" bundle package and have two wireless packages installed,
uninstall one wireless package before upgrade to 6.37. For other cases simply upgrade to
6.37 version.

There will be only one "wireless" package in RouterOS v6.37. If using bundle package to
upgrade, click "Check for updates" in your RouterOS configuration interface, or head to
our download page: http://www.mikrotik.com/download.

--- IMPORTANT! DFS CHANGES:

DFS configuration in RouterOS has been redesigned, now device looks at specified country
settings (/interface wireless info country-info), and applies corresponding
DFS mode for each frequency range automatically, making dfs-mode setting unnecessary.

Please, check that your frequencies work with corresponding DFS settings before upgrade.

Changes since 6.37rc21:

*) ethernet - fixed rare kernel failure on non-switch ethernet reset;
*) simple queues - fixed issue which caused additional/unnecessary CPU load;

Thu Aug 25, 2016 2:03 pm

*) simple queues - fixed issue which caused additional/unnecessary CPU load;

Can you be more specific? What simple queue configurations are affected? how much?

heaven · Thu Aug 25, 2016 2:06 pm

Don't use dynamic enable
Use enable only

Enviado de meu XT1580 usando Tapatalk
wrong(. every time cap have a new number of virtual cap wlan on reconnect. if it's was be so easy i'm not write here. but thank you for your answer).
Sorry, but sometimes is wrong there,
My cap number don't change when devices is rebooted

Edit:
Now I got it
I understand another Dynamic number [emoji57]

The caps number on the cap device it Is normal to increase ( Why need to be like that I don't know)

The trick is to use data path settings so the caps interface go to the correct bridge

Enviado de meu XT1580 usando Tapatalk

I try fistly write br number in datapath but nothing(.

patrick7 · Thu Aug 25, 2016 2:12 pm

Feature request:
Allow unset at every place where it's possible to set an empty value (example: bgp update source, unset update-source does not work, set update-source=none is needed. firewall log prefix, set log-prefix="" works, but unset log-prefix does not work.).

Thu Aug 25, 2016 2:13 pm

macgaiver - Simple Queue hashing algorithm had an issue which caused hash rebuilds. This caused additional CPU load. This fix affects all Simple Queue configurations but improvement depends on queue count and complexity.

This issue was found on Intel based x86 installation with ~6500 Simple Queues. Load after upgrade went down from 70-80% to 20-30%.

pe1chl · Thu Aug 25, 2016 2:36 pm

Feature request:
Allow unset at every place where it's possible to set an empty value (example: bgp update source, unset update-source does not work, set update-source=none is needed. firewall log prefix, set log-prefix="" works, but unset log-prefix does not work.).

unset something is not the same as setting an empty value for it. it may work out the same in some cases, but be different in others.
maybe you would want a "reset" function that sets it to its default value, which may be unset, empty or none.

Thu Aug 25, 2016 2:44 pm

unset is available only for parameters that can be unset, log-prefix is not one of them.

Type in the terminal "unset 0 <tab>" and see all acceptable parameters that can be unset.

patrick7 · Thu Aug 25, 2016 2:45 pm

Don't agree.

[admin@cr1.zrh1] /routing bgp peer> :put [get 6 update-source ]

As you can see, update-source is nothing (=empty). In WebFig, it's possible to click an arrow to make this field disappearing (like unset).

[admin@cr1.zrh1] /routing bgp peer> set 6 update-source=1.2.3.4
[admin@cr1.zrh1] /routing bgp peer> :put [get 6 update-source ]
1.2.3.4

Now we have the update source "1.2.3.4". I want to do the same as in the GUI, unset this value:

[admin@cr1.zrh1] /routing bgp peer> unset 6 update-source
input does not match any value of value-name

So why should I use

[admin@cr1.zrh1] /routing bgp peer> set 6 update-source=none
[admin@cr1.zrh1] /routing bgp peer> :put [get 6 update-source ]

? In my oppinion, "none" is not correct. Every BGP update message NEEDS a source address. None means "no source address". Unset would just be right for that (= tell the router to not use a specific address, like "unspecified").

If I say that a configuration value should be "none", I expect this "none" to be in the configuration, which is not. It's also not possible to clear this value with set update-source="".

Thu Aug 25, 2016 2:54 pm

Parameter is for custom update-source. What custom update-source to use? None. So perfectly valid option. And as I mentioned in previous post, unset works on specific parameters which can be seen by typing unset 0 <tab>, update-source is also not one of them.

patrick7 · Thu Aug 25, 2016 2:59 pm

Don't really see the sense behind that, but ok......
In my opinion, it should also be possible to unset (make empty) "custom" values. Because in the configuration you don't see the "none" so it's like "empty" or "not set".

alexjhart · Fri Aug 26, 2016 1:27 am

*) snmp - added script table which executes script and returns it's output on get request;

Please explain how to use this feature, because I cannot find it in the user interface...

I too am looking for more information. Don't see anything in the wiki yet?

Motorbreath · Fri Aug 26, 2016 1:27 pm

I get a pretty different signal strenght between 6.36.2 and 6.37rc22, all the settings are the same...can someone please explain?

Edit: It's a pretty significant drop in Signal Strenght on 6.37rc22, was the same with previous 6.37rc's. As soon as I get back to 6.36.2 everything is back to normal.

pukkita · Fri Aug 26, 2016 2:21 pm

Have you tried resetting the wireless config and redoing it? Is your RB firmware up to date?

Motorbreath · Fri Aug 26, 2016 3:24 pm

Have you tried resetting the wireless config and redoing it? Is your RB firmware up to date?

Yes, tried resetting config, and the RB fw is up to date. Mikrotik responded that it could be a new way signal strenght is calculated...

pukkita · Fri Aug 26, 2016 11:59 pm

I think I noticed that, but related to chain numbers... maybe the case as you have only one chain. Have you tested the link to see if there are actual performance differences?

Motorbreath · Sat Aug 27, 2016 12:27 am

I think I noticed that, but related to chain numbers... maybe the case as you have only one chain. Have you tested the link to see if there are actual performance differences?

performance seems to be the same, all signal led lights are still on my Groove...

Noise floor goes to -92 dBm, signal to noise 37 dB on 6.37rc22 and on the current 6.36.2 it's -97 dBm and 48 dB signal noise... I am back on stable version for now

Kevo · Sat Aug 27, 2016 6:19 am

48db signal to noise sounds just about impossible in the real world on unlicensed freq. We have licensed links running under -50 that don't see 48db SNR. I would guess the first set of numbers are more accurate.

Motorbreath · Sat Aug 27, 2016 9:51 am

48db signal to noise sounds just about impossible in the real world on unlicensed freq. We have licensed links running under -50 that don't see 48db SNR. I would guess the first set of numbers are more accurate.

So we (using Groove) had false info for wireless signal strenght this whole time? MikroTik, what did you change for the RC versions so it shows different signal quality? A bug, or?

pukkita · Sat Aug 27, 2016 12:01 pm

To enhance those wireless values precision. They're crucial in order to tune and troubleshoot wireless links.

Remember a 3dB diference is actually a double increase or a half decrease...