MikroTik

Posted: **Wed Mar 02, 2022 10:05 am**

RouterOS version 6.49.4 has been released in public "stable" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 6.49.4 (2022-Feb-25 09:33):

*) capsman - improved stability when running background scan on CAP;
*) lora - fixed "antenna-gain" parameter unit;
*) ssl - disabled RC4 and 3DES ciphers for "www-ssl", "www-api" and OVPN services;
*) traffic-flow - do not handle NAT events when "nat-events" is disabled;
*) wireless - added "3gpp-info" parameter to interworking configuration;
*) wireless - added EAP-AKA to interworking's realm configuration;
*) wireless - correctly preserve WMM priority when receiving packets;
*) wireless - updated "philippines" regulatory domain information;

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

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 some problem has appeared on device

Please keep this forum topic strictly related to this particular RouterOS release.

Posted: **Wed Mar 02, 2022 11:50 am**

I cant get ipv6 address in my PC after update:

/ipv6 address
add address=::ba69:f4ff:fec5:5ded from-pool=ipv6-pool interface=bridge1
/ipv6 dhcp-client
add interface=pppoe-out1 pool-name=ipv6-pool rapid-commit=no request=prefix \
    use-peer-dns=no
/ipv6 nd
set [ find default=yes ] advertise-dns=no interface=pppoe-out1 ra-interval=\
    10s-30s
add hop-limit=64 interface=bridge1 ra-interval=10s-30s
/ipv6 nd prefix default
set preferred-lifetime=2m valid-lifetime=5m

In ipv6 dhcp client i get correct prefix.

Posted: **Wed Mar 02, 2022 3:41 pm**

/ipv6 nd
set [ find default=yes ] advertise-dns=no interface=bridge1 ra-interval=\
    10s-30s

Posted: **Wed Mar 02, 2022 5:05 pm**

Rolling back to the previous issue with the previous statements, everything worked properly.
In changelog I do not see anything related to ipv6 to affect it.
Are there any other changes besides those announced in changelog?

Posted: **Wed Mar 02, 2022 5:59 pm**

Installed on Audience, LED is now green instead of blue?

edit: ah it's incorrectly assuming it's in an Audience network, due to a wireless bridge to a hAP Lite .

Posted: **Thu Mar 03, 2022 12:18 pm**

Updated soft- and firmware on these models without any issues:
CCR1009-7G-1C-1S+
CCR2004-1G-12S+2XS
CRS112-8P-4S
RBcAPGi-5acD2nD (cAP ac)
RB1100AHx4
RB750GL
RBD52G-5HacD2HnD (hAP ac2)
x86

Posted: **Thu Mar 03, 2022 6:57 pm**

Updated soft- and firmware on these models without any issues:
CCR1009-7G-1C-1S+
CCR2004-1G-12S+2XS
CRS112-8P-4S
RBcAPGi-5acD2nD (cAP ac)
RB1100AHx4
RB750GL
RBD52G-5HacD2HnD (hAP ac2)
x86

Thanx for reporting...

Posted: **Fri Mar 04, 2022 4:50 am**

Updated SXT LTE Kit and hAP ac². No new issues found, yet!

Posted: **Fri Mar 04, 2022 7:10 am**

Updated my CCR1036-12G-4S and No issues were found.

Posted: **Fri Mar 04, 2022 10:19 am**

no bootloop on arm (like RBD52G aka hAPac2) seen on 6.49.3, all went fine on a bunch of devices (arm, mipsbe)

Posted: **Fri Mar 04, 2022 10:41 am**

CHR no issues

Posted: **Fri Mar 04, 2022 11:03 am**

Remote RB433 survived upgrade

Posted: **Fri Mar 04, 2022 11:41 am**

*) traffic-flow - do not handle NAT events when "nat-events" is disabled;

Thank you! This saves a lot of crap in our netflow server log!

Posted: **Fri Mar 04, 2022 11:21 pm**

@bbs2web
Did you get any further with your issue "I have an odd situation in that two virtual RouterOS instances, both running 6.49.4 (x86), support IPSec AES hardware offloading differently. Any ideas on where I could hunt?" in the 6.49.3 release topic?
I have the same issue, and it still occurs in this version 6.49.4...

Posted: **Sat Mar 05, 2022 9:37 am**

denisun - Are you sure that it is working again after a downgrade to 6.49.3? And again not working if you once more upgrade to 6.49.4? No, there are no hidden changes in this version.
hecatae - So then the LEDs are working as expected?
bajodel - Glad to hear that, but please note that upgrade happens on the old version, not on the one that you install on the router. So in 99% of cases when an upgrade fails to install new packages - the old version is to blame.

Posted: **Sat Mar 05, 2022 10:02 am**

denisun - Are you sure that it is working again after a downgrade to 6.49.3? And again not working if you once more upgrade to 6.49.4? No, there are no hidden changes in this version.

Yes it works for all previous versions without problem.

Posted: **Sat Mar 05, 2022 11:22 am**

denisun - Then please provide two supout files to support@mikrotik.com. One from v6.49.3 where everything is working properly and one from v6.49.4 where it is not.

Posted: **Sat Mar 05, 2022 2:50 pm**

hecatae - So then the LEDs are working as expected?

No, it randomly changes between blue and green, gone back to 7.1.3 as at least that stays permanently blue regardless.

Posted: **Sat Mar 05, 2022 6:22 pm**

denisun - Then please provide two supout files to support@mikrotik.com. One from v6.49.3 where everything is working properly and one from v6.49.4 where it is not.

I have update to 6.49.4 with the above conf for nd and work ok.
Unfortunately I have no longer the ability to produce a suppout file for the previous version.
But I have the conf in .rsc and .backup file.

Posted: **Sun Mar 06, 2022 12:48 am**

Hi MikroTik

we need on wireless snooper find list

Posted: **Mon Mar 07, 2022 3:16 pm**

hAP ac -- no issues.

Posted: **Mon Mar 07, 2022 3:35 pm**

CRS305
CRS326
CRS317
CHR
no issues

Posted: **Mon Mar 07, 2022 4:20 pm**

RB3011 Software updated OK, but needed power cycle after firmware update :(

Posted: **Mon Mar 07, 2022 9:58 pm**

No info in changelog, but in this version is smaller number of disconnections in 60Ghz multipoint

Posted: **Mon Mar 07, 2022 11:09 pm**

It has been there since 6.49, but no information found so far.
DHCP problems are seen since 6.38. Related somehow or not?
When and how to use it ? Are the 2 release notes lines saying the same ? Otherwise, how to set the 2nd ?

*) winbox - added "dhcp" option to "multicast-helper" setting;
*) wireless - added override for multicast-to-unicast translation of DHCP traffic;

.
Or is this some enhancement of 6.40? "*) wireless - always use "multicast-helper" when DHCP is being used;"

Posted: **Thu Mar 10, 2022 4:43 pm**

Does CAPsMAN fully support QCA9984 at ROS 6.49.4?
I am testing Audience, the QCA9984 works great, the four stronger antennas too.
The clients cannot connect to CAP AP when an extension channel is enabled.
I have tested that the AP works fine with XXXX without CAPsMAN.
The problem disappears when wlan3 is excluded from CAP.
Any ideas how to resolve the problem?

Test#1 the almost default configuration with no limit of extension-channel

/caps-man configuration
add country="united states capac" datapath.client-to-client-forwarding=yes datapath.local-forwarding=yes mode=ap name=test security=
    test ssid=test

Result#1 the channel: 5765/20-Ceee/ac+5570/80/DP and no connections

/interface wireless monitor wlan3
           ;;; managed by CAPsMAN
      channel: 5765/20-Ceee/ac(25dBm)+5570/80/DP(14dBm)
  noise-floor: -101dBm

Test#2 the extension channel limited to XX

/caps-man configuration
add channel.extension-channel=XX country="united states capac" datapath.client-to-client-forwarding=yes datapath.local-forwarding=yes mode=ap name=\
    test security=test ssid=test

Result#2 the channel: 5785/20-eC/ac and no connections

/interface wireless monitor wlan3
           ;;; managed by CAPsMAN
           ;;; channel: 5785/20-eC/ac(25dBm), SSID: Cheerful Wi-Fi, local forwarding
      channel: 5785/20-eC/ac(25dBm)
  noise-floor: -107dBm

Test#3 the extension channel disabled

/caps-man configuration
add channel.extension-channel=disabled country="united states capac" datapath.client-to-client-forwarding=yes datapath.local-forwarding=yes mode=ap name=\
    test security=test ssid=test

Result#3 the channel 5785/20/ac and iPhone 12 is connected

/interface wireless monitor wlan3
              ;;; managed by CAPsMAN
              ;;; channel: 5785/20/ac(25dBm), SSID: Cheerful Wi-Fi, local forwarding
         channel: 5785/20/ac(25dBm)
     noise-floor: -107dBm
  overall-tx-ccq: 92%

/caps-man registration-table print where comment=iPhone-Piotr
 # INTERFACE                                                   SSID                                                  MAC-ADDRESS       UPTIME                RX-SIGNAL
 0 ;;; iPhone-Piotr
   MikroTik-1                                                  test                                        C6:ED:21:xx:xx:xx 7m35s660ms                  -66

Test#4 the wlan3 is excluded from CAPsMAN and extension channel XXXX

/interface wireless
set [ find default-name=wlan3 ] band=5ghz-onlyac channel-width=20/40/80mhz-XXXX country="united states capac" disabled=no frequency=5745 mode=ap-bridge security-profile=test ssid=test

Result#4 a client connected despite the extension channel 5745/20-Ceee/ac

/interface wireless monitor wlan3
                 status: running-ap
                channel: 5745/20-Ceee/ac(25dBm)
      wireless-protocol: 802.11
            noise-floor: -106dBm
         overall-tx-ccq: 68%
     registered-clients: 1
  authenticated-clients: 1
       current-distance: 1
            wmm-enabled: yes
    notify-external-fdb: no

BTW Unfortunately the available channels are limited.

/interface wireless info hw-info
interface: wlan3
      ranges: 5500-5825/5/a,an20,an40,ac20,ac40,ac80,ac160,ac80-80
   tx-chains: 0,1,2,3
   rx-chains: 0,1,2,3
  extra-info: pciinfo:0x0, cid:0, gain:5

/interface wireless info allowed-channels wlan3
  channels: 5500/20-Ceee/ac/DP(14dBm),5505/20-Ceee/ac/DP(14dBm),5510/20-Ceee/ac/DP(14dBm),5515/20-Ceee/ac/DP(14dBm),5520/20-Ceee/ac/DP(14dBm),5525/20-Ceee/ac/DP(14dBm),
            5530/20-Ceee/ac/DP(14dBm),5535/20-Ceee/ac/DP(14dBm),5540/20-Ceee/ac/DP(14dBm),5545/20-Ceee/ac/DP(14dBm),5550/20-Ceee/ac/DP(14dBm),5555/20-Ceee/ac/DP(14dBm),
            5560/20-Ceee/ac/DP(14dBm),5565/20-Ceee/ac/DP(14dBm),5570/20-Ceee/ac/DP(14dBm),5575/20-Ceee/ac/DP(14dBm),5580/20-Ceee/ac/DP(14dBm),5585/20-Ceee/ac/DP(14dBm),
            5590/20-Ceee/ac/DP(14dBm),5595/20-Ceee/ac/DP(14dBm),5600/20-Ceee/ac/DP(14dBm),5605/20-Ceee/ac/DP(14dBm),5610/20-Ceee/ac/DP(14dBm),5615/20-Ceee/ac/DP(14dBm),
            5620/20-Ceee/ac/DP(14dBm),5625/20-Ceee/ac/DP(14dBm),5630/20-Ceee/ac/DP(14dBm),5635/20-Ceee/ac/DP(14dBm),5640/20-Ceee/ac/DP(14dBm),5645/20-Ceee/ac/DP(14dBm),
            5650/20-Ceee/ac/DP(14dBm),5655/20-Ceee/ac/DP(14dBm),5660/20-Ceee/ac/DP(14dBm),5745/20-Ceee/ac(25dBm),5750/20-Ceee/ac(25dBm),5755/20-Ceee/ac(25dBm),5760/20-Ceee/ac(25dBm),
            5765/20-Ceee/ac(25dBm)

Posted: **Thu Mar 10, 2022 4:47 pm**

You are always limited to the channels allowed in your country. When you use an 80 MHz channel in Ceee layout the specified channel is the lowest of the 4 20 MHz channels joined together, so this apears to limit you channel choice (highest selectable channel) but this is not actually the case.
Also, in Audience I think there is a hardware limitation to use only the lower channels for the access point while the higher channels are reserved for the crosslink between the devices.

Posted: **Thu Mar 10, 2022 5:07 pm**

Thank you to prompt response.
But the point is that the CAPsMAN works badly with QCA9984 unless I made a mistake.

Posted: **Thu Mar 10, 2022 5:24 pm**

Also, in Audience I think there is a hardware limitation to use only the lower channels for the access point while the higher channels are reserved for the crosslink between the devices.

No, actually that's not the case, it's possible to configure any radio for any task ... it's only that MT marketing thought that 4x4 radio would be ideal for meshing. Probably there's a QuickSet setting that sets device accordingly.

The problem is that CAPsMAN doesn't offer full flexibility to configure radio. So if you really want to get maximum out of audience, configure it directly so you can optimize settings on each of radios. Try setting things manually (frequency, channel layout) so that you know what should be on air ...

One example:

Result#1 the channel: 5765/20-Ceee/ac+5570/80/DP and no connections

According to wikipedia list of WiFi channels, 5765 (channel 153) is not a good C frequency for 40/80MHz channels in Ceee layout .... 5745 would be fine as it's included in 20, 40 and 80 MHz channels equally (channels 149, 151 and 155). Channel 153 might be OK for 20/40 eC though.
At teh same time, 5570 doesn't seem to be good center frequency for 80MHz channel (it seems like it's fine for 160, but not for 80+80). 5530 would be fine (channel 108).
While MT doesn't seem to mind, some other devices may.

One more thing to keep in mind: the high channels (possible to use on 4x4 radio) are mostly DFS channels. Which means 1 (or 10) minute wait for AP to scan for possible radar signals. During that time, AP is not really up&running ... if using "normal" 20/40/80 channel, then AP won't even transmit SSID. I don't know how it behaves in 80+80 layout if the +80 fall into meteo-radar range which requires 10 minute scan ... does it start as 20/40/80 and only enables the +80 after scanning period is over or it doesn't start transmitting just like with "normal" channel layout?

Another thing: it would be nice if you posted actual configuration and running values ... e.g. thee don't correspond:

Test#2 the extension channel limited to XX

/caps-man configuration
add channel.extension-channel=XX country="united states capac" datapath.client-to-client-forwarding=yes datapath.local-forwarding=yes mode=ap name=\
test security=test ssid=test

Result#2 the channel: 5785/20-eC/ac and no connections

/interface wireless monitor wlan3
;;; managed by CAPsMAN
;;; channel: 5785/20-eC/ac(25dBm), SSID: Cheerful Wi-Fi, local forwarding
channel: 5785/20-eC/ac(25dBm)
noise-floor: -107dBm

Posted: **Thu Mar 10, 2022 5:59 pm**

MT does not use center frequencies for 40, or 80 MHz wide channels, it uses the 20MHz channels. So use 20 MHz center frequencies only.
100=5500, 104=5520, 108 =5540, 112=5560 ... So only the numbers out of the 20MHz column to be used with Mikrotik, even for 40 and 80 Mz wide channels where it corresponds to the C channel, use the numbers in the [brackets] to indicate the C channel. Use Ce,eC,Ceee,eCee,eecE or eeeC to align the rest of the wide channel.
.

Klembord-2.jpg

Posted: **Thu Mar 10, 2022 9:21 pm**

MT does not use center frequencies for 40, or 80 MHz wide channels, it uses the 20MHz channels.

That's correct. But other devices might use 40 or 80 MHz center frequencies at the same time. Hence if Mikrotik's center frequency and channel layout doesn't correspond to center frequency of wider channel, thete's high possibility for incompatibility.

What I'm trying to say: in order to have fully compatible 80MHz channel in lowest part of spectrum, only these combinations are valid: 5180-Ceee, 5200-eCee, 5220-eeCe and 5240-eeeC. It can't be say 5200-Ceee ... this makes valid 20MHz channel, but neither 40 nor 80 MHz.

Posted: **Fri Mar 11, 2022 3:58 am**

What I'm trying to say: in order to have fully compatible 80MHz channel in lowest part of spectrum, only these combinations are valid: 5180-Ceee, 5200-eCee, 5220-eeCe and 5240-eeeC. It can't be say 5200-Ceee ... this makes valid 20MHz channel, but neither 40 nor 80 MHz.

Yes, I have found this same thing. It only seems to happen with CAPsMAN where it selects this, when set for extension channel XXXX. If it isn't using CAPsMAN, it will always select one of 5180-Ceee, 5200-eCee, 5220-eeCe or 5240-eeeC (or some other equally valid selection). When it is using CAPsMAN, the XXXX setting occasionally selects things like 5200-Ceee and then nothing can connect, except a few random devices that happen to work (ex. Macbook Pro laptops). It has been a problem for us for a while and has caused us to enforce Ceee when using CAPsMAN instead of allowing it to remain on XXXX.

Posted: **Fri Mar 11, 2022 11:29 am**

I classified XXXX with "station" configs. It is free to accept anything. With XXXX on the AP side, one is NOT setting the freq to be used. We hope that RouterOS is smart enough, and also that it has a "smart auto", but there is clearly not such a thing. (Freq Usage and Snooper should be continous in the background). Now "auto" seems to be based on a single data acquisition and goes for some optimisation: lowest "freq usage" or lowest number of AP's (scan) or lowest number of devices (Snooper). All brands do prefer channel 3 and 8 on a busy 2.4GHz band with auto, ... not very smart.
[Draytek auto let you set the 1-6-11 or 1-5-9-13 preference. We could do the same with the channel list.] But I never use XX or XXXX for an AP, not even auto. And if CAPsMAN is not aligning the 40MHz and 80 MHz channels, or the user sets it unaligned, that is a problem then.

Posted: **Fri Mar 11, 2022 11:53 am**

Yeah, I think it is pretty dumb to sell routers that do not adhere to the 1-6-11 scheme by default on 2.4 GHz in auto mode.
That just causes a mess. I always install a 1-6-11 channel list (originally I named it like that, but that triggers a bug in export/import).
MikroTik should do that by default, and then advanced users can change it into 1-5-9-13 or other preferences. But those that do not know should not land on channel 3 or 8!

Posted: **Fri Mar 11, 2022 12:04 pm**

Yeah, I think it is pretty dumb to sell routers that do not adhere to the 1-6-11 scheme by default on 2.4 GHz in auto mode.

Want to mention that to TP-Link please ?
No F-cking way to change their channels on Deco line... this weekend remaining 2 Deco P7's go OUT here at home.

Posted: **Fri Mar 11, 2022 12:18 pm**

When scanning here, the vast majority of the 115 routers I see here is on 1, 6 or 11 (2412, 2437, 2462) with only very few, indeed mostly TP-Link, on other channels.
But I don't think anyone should hide behind such whataboutisms. Just fix your own stuff.

Posted: **Sat Mar 12, 2022 1:13 am**

But I never use XX or XXXX for an AP, not even auto. And if CAPsMAN is not aligning the 40MHz and 80 MHz channels, or the user sets it unaligned, that is a problem then.

MikroTik's default config for the 5GHz interface on most home devices is XXXX. Our default config for our home customer routers is based on this, and we kept this aspect from them. We haven't had a single problem. So I'm pretty sure the regular wireless is correctly aligning the 40 and 80MHz channels, otherwise we probably would have been getting complaints. It was only in our office, where we run CAPsMAN, that we found this misalignment of the 40 and 80MHz channels was happening sometimes.

Posted: **Sat Mar 12, 2022 1:46 am**

OK it is intended for AP as well. The wiki indeed says that it will make a proper choice: "Channel widths with XX and XXXX extensions automatically scan for a less crowded control channel frequency based on the number of concurrent devices running in every frequency and chooses the “C” - Control channel frequency automatically."
From this statement I cannot know what frequencies will be used for lets say 5540/XXXX. 'Chooses the "C",' means what ? Shifting the given frequency in the aligned 80MHz channel, or shifting the control channel position, or a combination? e.g.: The starting lower freq here could be 5500, 5520 or 5540 when shifting control channel position. (5540/eeCe, eCee, and Ceee, with eeeC being impossible. Only the first one is aligned as expected. Being "C" or "e" has some importance in 802.11ac)

Well maybe better do just test it ...
Following setting

Klembord-2.jpg

gives following status

Klembord-3.jpg

but I cannot force a different Control channel selection (would need some extra competing AP setup)

Interesting experiment ... 5180-5200-5220-5240/XXXX are all the same 80 MHz channel, by using resp. Ceee till eeeC, 5260/XXXX comes with 5260/eeCe, 5280/XXXX is not accepted unless e-and-C notation is used.

Posted: **Wed Mar 16, 2022 9:42 am**

New version v6.49.5 has been released:

viewtopic.php?t=184155

MikroTik

v6.49.4 [stable] is released!

v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!

Re: v6.49.4 [stable] is released!