After upgrade from 6.38.5 to 6.43.8 board 911G-5HPacD link 8 km the result is:

6.38.5
ping -3 ms
bandwidth test TCP: - 210 mbps

6.43.8
ping- 6 ms
bandwidth test TCP: - 145 mbps

I'm disappointed after upgrade. The only reason I made the change was that I saw in changelog: *) wireless - improved stability for 802.11ac;

OSPF randomly passes only part of the records to the routing table. It stops having fun.

We're seeing this too. We have one building-to-building link, using dynamic-mesh WDS. The two buildings, and the WDS link, are all on distinct subnets, with routing managed by OSPF.

When the routers were running 6.43.4, when the link would drop & reestablish, everything recovered fine.

Since upgrading to 6.43.8 last night, when the link drops & reestablishes, the near end adds the correct routes to its routing table, but it doesn't seem to pass those updates to its other neighbors. Disabling and enabling the OSPF network for the WDS link corrects the problem almost immediately.

These comments are interesting to us, since we encountered odd OSPF update problems after upgrading from 6.43.4 to 6.43.7. However, in our case, the network context is very complex, with two separately-managed networks peering via OSPF. We are actually deploying MikroTik routers to isolate the routing between these two networks. Since we only have control over one of the two networks, it is difficult for us to diagnose the problem when we are looking at OSPF issues on the boundary between the two networks.

My purpose in adding to these comments is to see if anyone else has encountered problems with OSPF route updates after upgrading to 6.43.7 or 6.43.8. The 6.43.7 release notes include:

*) ospf - improved stability while handling type-5 LSAs;

However, OSPF is not mentioned in the 6.43.8 release notes. One reason we upgraded to 6.43.7 was due to the above release note. I will try to provide more information, but our current situation is too complex to allow easy analysis. I’m intrigued with the simpler network setup describe by Hotz1, and may try to configure something similiar in a lab context to attempt to diagnose matters further.

After upgrading a couple of days ago to 6.43.8 stable in my RB952Ui-5ac2nD, i have experienced continuous reboots due to watchdog timer when i was casting from my laptop's chrome to google's chromecast (ver 2) using wifi 5G. I don't have the same issues while performing the same tasks in another 2.4G chromecast (ver 1). I will apply an ACL for chromecast (ver 2) in 5G and force thus only 2.4G wifi and see if it occurs again. I did't had such issues in the past while casting to any of them and for any type of supported casting (youtube, netflix, android apps, chromecast/opera content etc) in both 2.4G/5G.

After upgrade from 6.38.5 to 6.43.8 board 911G-5HPacD link 8 km the result is:

6.38.5
ping -3 ms
bandwidth test TCP: - 210 mbps

6.43.8
ping- 6 ms
bandwidth test TCP: - 145 mbps

I'm disappointed after upgrade. The only reason I made the change was that I saw in changelog: *) wireless - improved stability for 802.11ac;

In my PTP i don´t see changes, equal ping and equal bandwidth.
The only problem is the change of frecuency mode, i finnaly put all in debug and superchannel.
All of my antennas is dynadish 5 and NetMetal 5SHP with mAnt 30.

I think Country Debug it´s equal or better than old no_country_set.

Code: Select all

> interface wireless info country-info no_country_set 
  ranges: 2402-2472/b,g,gn20,gn40(30dBm)
          2417-2457/g-turbo(20dBm)
          5170-5250/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(17dBm)
          5250-5330/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(23dBm)/dfs,passive
          5735-5835/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(30dBm)
          5190-5230/a-turbo(17dBm)/dfs
          5230-5310/a-turbo(23dBm)/dfs,passive
          5740-5820/a-turbo(30dBm)/dfs
          5180-5260/a-turbo(17dBm)
          5260-5300/a-turbo(23dBm)/dfs,passive
          5745-5825/a-turbo(30dBm)
          902-927/b,g,g-turbo,gn20,gn40(30dBm)

Code: Select all

> interface wireless info country-info debug          
  ranges: 902-927/b,g,g-turbo,gn20,gn40(5dBm)
          2302-2382/b,g,gn20,gn40(5dBm)
          2402-2482/b,g,gn20,gn40(5dBm)
          2474-2494/b,g,gn20,gn40(5dBm)
          2502-2742/b,g,gn20,gn40(5dBm)
          2292-2392/g-turbo(5dBm)
          2417-2457/g-turbo(5dBm)
          2492-2752/g-turbo(5dBm)
          5110-5710/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(5dBm)
          5735-5835/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(5dBm)
          5110-5690/a-turbo(5dBm)
          5130-5670/a-turbo(5dBm)

Debug has very low power limits - 5 dBm (like 3mW)

This power limits it´s if you put regulatory-domain, in normal cases if put debug you use superchannel. I check this in my antennas, put debug and superchannel and works same power than no_country_set. But if put debug and regulatory-domain drops the power to this 5dbm.

Sorry socada just quick question i'm willing to know.
How you puting debug for regulatory-domain and superchannel ?

Symbol: ` in WLAN SSID brake all wlan interfaces.
Or even not a symbol, but a virtual WLAN. When I create a virtual WLAN and reboot hap ac^2, I don't see all interfaces and export doesn't work in the console.

DimaFIX - Please send supout.rif file from your router to support@mikrotik.com. If I add such symbol to my wireless interfaces SSID, then it continue to work properly.

I don't think the problem is the ` symbol.
I upgraded over 40 devices of all makes and models without any problems.

But on a single hAP ac^2 after reboot the interface list was empty. The SSIDs were standard ASCII names, without any special character.
After many minutes of waiting, the interfaces appeared but the wlans were missing, and the whole board was very sluggish (no, there was no cpu load).
Reboots didn't help.

Also after each reboot a blue warning was shown about defconf not being able to find any wireless interfaces.

After downgrading back to 6.43.4, the warning is still there, reboot times are long, but all interfaces are working again.
I cannot troubleshoot this further since it's in production.

Upon further testing on this, the culprit is indeed the virtual wlan interfaces.

The issue seems to be present on older versions as well but not that severe.

With versions 6.42.10, 6.34.4, 6.34.7 that I tried doing a clean netinstall on all of them, after a reboot, the router would become reachable via IP after 20-30 seconds after actually booting. In the meantime accessing the router via MAC, the interface list is empty, all IP addresses show 'unknown' interface and no traffic passes through. After 20-30 seconds, all interfaces appear and the router start routing traffic.

Upgrading to 6.34.8, the issue is much more severe. It took over 25 minutes for the interfaces to finally appear. In the first 5 minutes the ethernet, pppoe, l2tp, eoip, bridge interfaces show up - but no traffic was routed. After 25-30 minutes the wlan interfaces appear as well, and only then traffic starts to flow through.

Disabling the virtual wlan interfaces, did not solve the issue. They had to completely get deleted. After that the router boots up in mere seconds and starts routing traffic immediately.

So, it appears there's an issue with virtual wlans on hAP ac^2 (or ARM - I don't have another ARM based device with wlans to confirm).

Just to clarify (if anyone else wants/can reproduce this), the config regarding the virtual wlan interfaces was, 1 virtual wlan interface per physical wlan (one for 2.4GHz and one for 5GHz) both added to a bridge.

I think Country Debug it´s equal or better than old no_country_set.

Code: Select all

> interface wireless info country-info no_country_set 
  ranges: 2402-2472/b,g,gn20,gn40(30dBm)
          2417-2457/g-turbo(20dBm)
          5170-5250/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(17dBm)
          5250-5330/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(23dBm)/dfs,passive
          5735-5835/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(30dBm)
          5190-5230/a-turbo(17dBm)/dfs
          5230-5310/a-turbo(23dBm)/dfs,passive
          5740-5820/a-turbo(30dBm)/dfs
          5180-5260/a-turbo(17dBm)
          5260-5300/a-turbo(23dBm)/dfs,passive
          5745-5825/a-turbo(30dBm)
          902-927/b,g,g-turbo,gn20,gn40(30dBm)

Code: Select all

> interface wireless info country-info debug          
  ranges: 902-927/b,g,g-turbo,gn20,gn40(5dBm)
          2302-2382/b,g,gn20,gn40(5dBm)
          2402-2482/b,g,gn20,gn40(5dBm)
          2474-2494/b,g,gn20,gn40(5dBm)
          2502-2742/b,g,gn20,gn40(5dBm)
          2292-2392/g-turbo(5dBm)
          2417-2457/g-turbo(5dBm)
          2492-2752/g-turbo(5dBm)
          5110-5710/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(5dBm)
          5735-5835/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(5dBm)
          5110-5690/a-turbo(5dBm)
          5130-5670/a-turbo(5dBm)

Debug has very low power limits - 5 dBm (like 3mW)

This power limits it´s if you put regulatory-domain, in normal cases if put debug you use superchannel. I check this in my antennas, put debug and superchannel and works same power than no_country_set. But if put debug and regulatory-domain drops the power to this 5dbm.

Sorry socada just quick question i'm willing to know.
How you puting debug for regulatory-domain and superchannel ?

No, I put debug for country and superchannel for frequency mode. In this answer I say that the power in the middle of () is only if you put regulatory-domain but if you put superchannel the power is the maximum.
Sorry if I don't understand your question my English not very good.

I think Country Debug it´s equal or better than old no_country_set.

Code: Select all

> interface wireless info country-info no_country_set 
  ranges: 2402-2472/b,g,gn20,gn40(30dBm)
          2417-2457/g-turbo(20dBm)
          5170-5250/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(17dBm)
          5250-5330/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(23dBm)/dfs,passive
          5735-5835/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(30dBm)
          5190-5230/a-turbo(17dBm)/dfs
          5230-5310/a-turbo(23dBm)/dfs,passive
          5740-5820/a-turbo(30dBm)/dfs
          5180-5260/a-turbo(17dBm)
          5260-5300/a-turbo(23dBm)/dfs,passive
          5745-5825/a-turbo(30dBm)
          902-927/b,g,g-turbo,gn20,gn40(30dBm)

Code: Select all

> interface wireless info country-info debug          
  ranges: 902-927/b,g,g-turbo,gn20,gn40(5dBm)
          2302-2382/b,g,gn20,gn40(5dBm)
          2402-2482/b,g,gn20,gn40(5dBm)
          2474-2494/b,g,gn20,gn40(5dBm)
          2502-2742/b,g,gn20,gn40(5dBm)
          2292-2392/g-turbo(5dBm)
          2417-2457/g-turbo(5dBm)
          2492-2752/g-turbo(5dBm)
          5110-5710/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(5dBm)
          5735-5835/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(5dBm)
          5110-5690/a-turbo(5dBm)
          5130-5670/a-turbo(5dBm)

Debug has very low power limits - 5 dBm (like 3mW)

This power limits it´s if you put regulatory-domain, in normal cases if put debug you use superchannel. I check this in my antennas, put debug and superchannel and works same power than no_country_set. But if put debug and regulatory-domain drops the power to this 5dbm.

Sorry socada just quick question i'm willing to know.
How you puting debug for regulatory-domain and superchannel ?

No, I put debug for country and superchannel for frequency mode. In this answer I say that the power in the middle of () is only if you put regulatory-domain but if you put superchannel the power is the maximum.
Sorry if I don't understand your question my English not very good.

You dont need excellent english, just simple like you said:

"This power limits it´s if you put regulatory-domain, in normal cases if put debug you use superchannel. I check this in my antennas, put debug and superchannel and works same power than no_country_set. But if put debug and regulatory-domain drops the power to this 5dbm"

My quastion was HOW??

How you puting debug for regulatory-domain and superchannel ?

My quastion was HOW??

Quote only what is needed. No need to quote a quoted a quoted post.....
To reply to a post above you, click Post Reply below the post, not the " above the post.

You dont need excellent english, just simple like you said:

"This power limits it´s if you put regulatory-domain, in normal cases if put debug you use superchannel. I check this in my antennas, put debug and superchannel and works same power than no_country_set. But if put debug and regulatory-domain drops the power to this 5dbm"

My quastion was HOW??

How you puting debug for regulatory-domain and superchannel ?

I´m not saying that I use both at same time (superchannel and regulatory domain) only one need to choose obviously.
I think we are not understanding but I repeat that I have done and it working, I said that I put country in debug and another user said that this country works at low power (5dbm).

> interface wireless info country-info debug
ranges: 902-927/b,g,g-turbo,gn20,gn40(5dBm)
2302-2382/b,g,gn20,gn40(5dBm)
2402-2482/b,g,gn20,gn40(5dBm)
2474-2494/b,g,gn20,gn40(5dBm)
2502-2742/b,g,gn20,gn40(5dBm)
2292-2392/g-turbo(5dBm)
2417-2457/g-turbo(5dBm)
2492-2752/g-turbo(5dBm)
5110-5710/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(5dBm)
5735-5835/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(5dBm)
5110-5690/a-turbo(5dBm)
5130-5670/a-turbo(5dBm)
Debug has very low power limits - 5 dBm (like 3mW)


But I try and saw that this power (5dbm) it´s only when put debug for country and regulatory-domain for frecuency mode.
In summary I have my devices in debug and superchannel and I can reach the full power of transmit of device and more variety of channels in default-scan-list that in no_country_set then if I want to follow regulation of my country or not it´s in my hand.

*) capsman - fixed "group-key-update" parameter not using correct units;

Can we get some details on this?
How was the parameter interpreted before this fix? Is the long-term release affected by the same bug? If yes: when can we expect a backport of this bugfix to long-term?

I've been debugging this and comparing the Group Key Handshake (GTK update) between 6.43.7 and 6.43.8 during the weekend, since I have a lot of clients with the famous group-key timeout issue.
I came to the following conclusion: if you set the group-key-update timer to 1:00:00 (1 Hour) on versions 6.43.7 and older the group-key is updated every 36 seconds instead of 3600 ( I believe the minimum interval should be 5 minutes (300 seconds)).
After you apply the 6.43.8 update the Group Key Handshake is performed every 3600 seconds just like configured. I did not test any value lower than 1 hour, so I don't know what it did when set to 30 minutes or 5 minutes.
The GTK is shared on establishing a new connection to a Wi-Fi ap during the WPA(2) 4 way handshake. After that it is updated every configured interval with an advised minimum of 300 seconds via a 2 way handshake. You can imagen what happens when a client misses this update and is unable to communicate (unicast/multicast) after it expired. I did not fully read the 802.11 spec. I believe an expired key can be used up to 60 seconds after it expired after that a client needs to re-establish its connection, probably by performing a full 4 way handshake effectively losing its Wi-Fi connection.
Long story short, the Group Key Update feature is working now like it should and did not work before as expected and was probably causing a lot of issues on busy networks or on devices in battery save mode since it had a a lot of opportunities for missing an update of the GTK..

Thank you for that info, it's rather interesting that wifi is still usable with 36 sec update interval.
I really hope that the fix gets backported to long-term soon.

!) telnet - do not allow to set "tracefile" parameter;

After some digging, it turns out this is actually to fix an exploit that enables privilege escalation to root or damage to system files. Why is this not labelled as a security fix?

https://cxsecurity.com/issue/WLB-2018120151

But on a single hAP ac^2 after reboot the interface list was empty.

Disable /tool graphing, and use 6.43.8.

Thanks! That resolved the issue!

!) telnet - do not allow to set "tracefile" parameter;

After some digging, it turns out this is actually to fix an exploit that enables privilege escalation to root or damage to system files. Why is this not labelled as a security fix?

https://cxsecurity.com/issue/WLB-2018120151

Nice find.

https://cxsecurity.com/issue/WLB-2018120151

Wow. Does every process in routeros run with unrestricted root privileges?

https://cxsecurity.com/issue/WLB-2018120151

Wow. Does every process in routeros run with unrestricted root privileges?

Many processes used to run with unrestricted root privileges in linux 15 years ago but not anymore. I guess many similar problems will be fixed in ROS7 ...

Strange. Isn't a torch via winbox and via webfig supposed to deliver the same results? Because I just noticed that it does not. Torch via webfig just shows two lines (see screenshot Torch2). Device is hEX S, ROS is 6.43.8, same interface, roughly the same time.

roughly the same time.

I guess this likely is the point. Torch is a "right now" tool, not a "historical data" tool.

after upgrade from v6.43.7 to v6.43.8 I am unable to have USB APPLE ethernet adapter, in /system/serources/usb
I see vendor Apple, Name : Apple USB Ethernet Adapter, even serial nuber is visible but interface "Ether2" is missing and all firewall rules for that interface are RED...

roughly the same time.

I guess this likely is the point. Torch is a "right now" tool, not a "historical data" tool.

I get that. But the webfig torch NEVER shows more than the two lines to be seen in the screenshot, no matter what traffic is to be seen via winbox.

I get that. But the webfig torch NEVER shows more than the two lines to be seen in the screenshot, no matter what traffic is to be seen via winbox.

Just tried it myself. Right after opening the Torch screen I can see the same two lines as shown on your screenshots, but after clicking on the "Start" button it works as expected. Weird behavior, indeed.

I get that. But the webfig torch NEVER shows more than the two lines to be seen in the screenshot, no matter what traffic is to be seen via winbox.

Just tried it myself. Right after opening the Torch screen I can see the same two lines as shown on your screenshots, but after clicking on the "Start" button it works as expected. Weird behavior, indeed.

Thanks for reviewing my observation. Also in my case pressing the "Start" button helps, but I suppose it's not the way it's meant to be.

I've update a couple (±30) of RB2011/RB3011's hAP AC^2's and wAP AC devices from 6.43.4 to 6.43.8 and until now I got 2 wAP AC devices in an undefined state right after/during the update (update via capsman), they would not boot anymore. Luckily I'm able to power cycle these devices via PoE switches. After the powercycle the devices start with normal behaviour and the routerboard firmware has been updated to 6.34.8 (Routerboard firmware is set to auto update). It seems that they are able to updaten but fail to fully boot after the update, after a forced reboot (via PoE power cycle) the devices become responsive again and work as expected. The log of both the router and the AP show no warnings during/after the update.

The following code fails all the time: The error message is produced by the last remove command.

This is basically the same, but usually works, if not repeated right away:
I guess there is no guarantee that 5 second delay is always enough.

(RB951G-2HnD, ros v6.43.8 )

There will always be delays before items appear in the table. Slower CPU greater delay.

There will always be delays before items appear in the table. Slower CPU greater delay.

There is no delay in appearance. The print command finds the entry named A, but the remove command fails regardless.

This works:
I do not have an explanation, though.

remove [find name="A"]

but I would suggest to use proper method and unset variables
:set A

If you have any further questions post in correct section, this is not v6.43.8 related.

After upgrade from 6.38.5 to 6.43.8 error: DHCP server offering lease without success. With version 6.38.5 working but allversion sfter 6.38.5 not working DHCP

Hello Friends...
I am using CCR1016-12G (tile) for my office network management. Yesterday i upgraded the OS version to 6.43.8 from v6.39. After upgrading, i make some queue is simple queue but it's not working. Upload & Download both are showing 0bps. Previously made queues are working finely. Last queue i added as below.

name="youtube-pranoy" target=10.3.10.180/32 parent=none packet-marks=BDCOM_Youtube priority=8/8 queue=default-small/default-small limit-at=2M/2M max-limit=2M/2M burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s bucket-size=0.1/0.1

Please suggest me what should i do now? All users are using unlimited bandwidth now, thats why, it's so much tough to me for managing the bandwidth.
Another thing is that, when i logged into the mikrotik via winbox, it's showing unsecured mode at the right corner.

Is perhaps fasttrack active (you'll see it in /ip firewall filter)? fasttrack-ing is not compatible with queues.

Is perhaps fasttrack active (you'll see it in /ip firewall filter)? fasttrack-ing is not compatible with queues.

I didn't find any fasttrack filter in firewall. This issue is happening with those queues which are created later. Previously made queues are ok.

pranoy1083, the problem is likely in the queues themselves and not specific to this particular version. Please start a new topic for this and/or (better yet) report it to support@.

Please suggest me what should i do now? All users are using unlimited bandwidth now, thats why, it's so much tough to me for managing the bandwidth.
Another thing is that, when i logged into the mikrotik via winbox, it's showing unsecured mode at the right corner.

Potentially the problem is with queue 216? The target there is 0.0.0.0/0 and might be preventing the traffic from going to later queues.

Not sure if mentioned in this thread / topic yet, but upgraded CHR with Dude running couple of days ago. Tonight I had to do some maintenance on network equipment and but could not disable notifications in the Dude.

Untick all in notifications, click apply, then OK. as soon as I bounced the first network device, I got hammered with Dude notifications, checked the Dude and notifications did not disable.

Dude is full of annoying bugs like this. Try changing notification settings from Winbox instead of Dude client.

Im using CRS112-8p-4S poe switch, with 6.43.8 version, and i have noticed the following bug.

Example, i have trunk(tagged) interface - ether 8, with some vlans (example. 200,300,400), and access ports(untagged) - ether1,ether2 is vlan200. Ether3, ether4 is vlan's 300, etc.

I have noticed, when I connect my Raspberry Pi 3 B+ to ether3, which goes thru vlan300, I can't access my DHCP server, which should give me some IP address, for example 10.10.30.x, instead, i get the 169.254.x.x/16 address. However, when I set Poe-out:OFF on ether3, my Raspberry gets through and gets the 10.10.30.x IP address.

P.S.
My Raspberry does not support PoE In.

Bug !
CRL downloading/updating is broken. I had to turn off the CRL check after upgrade.
Please check it.

Bug with TikApp recognition:
The TikApp is recognized as Winbox since the latest updates, therefore disabling the TikApp in the /user group menu won't block the app anymore.
If Winbox is enabled in the group permission, anyone with the TikApp can login.
Tested on an RB951 testrouter and Samsung Galaxy S6.

I've update a couple (±30) of RB2011/RB3011's hAP AC^2's and wAP AC devices from 6.43.4 to 6.43.8 and until now I got 2 wAP AC devices in an undefined state right after/during the update (update via capsman), they would not boot anymore. Luckily I'm able to power cycle these devices via PoE switches. After the powercycle the devices start with normal behaviour and the routerboard firmware has been updated to 6.34.8 (Routerboard firmware is set to auto update). It seems that they are able to updaten but fail to fully boot after the update, after a forced reboot (via PoE power cycle) the devices become responsive again and work as expected. The log of both the router and the AP show no warnings during/after the update.

I see similar behavior. When manually upgraded ros to this version, I suddenly realised that routerboot was also upgraded, even the (undocumented!) feature system/routerboard/settings/"auto-upgrade" is not set. At least all devices booted normally (and only once) after upgrade so far.

hello support!
Could you give us more information about this changelog entry?

*) wireless - improved stability for 802.11ac;

What have been changed? Any improvement in NV2?

Thanks!

Would like to know as well. My RB4011 keeps disabling 5ghz WiFi after a few days (see graph). Only a reboot can bring the WiFi up again. Wondering if this has been fixed

That is the exact same problem 4 me

Found possible bug:

When you add subnet into "available from" field for SSH service, under IP Services...SSH becomes inaccessible, even if PC is in that subnet. It seems only to affect SSH though, for limiting access to http, https it work just fine.

Подскажите пожалуйста, почему удален мой пост о проблеме MTU при создании влан на интерфейсе bonding ?
Проверял на ROS архитекуры x86, проблема актуальна.

____________________________________________________

Please tell me why my post about the MTU problem was deleted when creating a vlan on the bonding interface?
Checked x86 on ROS 6.43.8, the problem is urgent.

Mutator, in a previous post you wrote yourself that the problem is also reproducible on an earlier versions of RouterOS (6.42.x), so it is NOT a 6.43.8 specific regression. The release topics are meant for version-specific issues only.

Also you have already reported the problem in another thread, and there's absolutely no need to flood the forum with the same report in different places.

And also your previous post was in Russian only. This is an International forum, please respect others and post here in English only. Thanks in advance.

Mutator, in a previous post you wrote yourself that the problem is also reproducible on an earlier versions of RouterOS (6.42.x), so it is NOT a 6.43.8 specific regression. The release topics are meant for version-specific issues only.

In the currently supported stable and longterm versions, this problem exists, so it needs to be fixed.
Gentlemen from Mikrotik does not support outdated ROS branches? Stable 6.43.8. Right ?
Also in the neighboring branches, users point to a similar problem bonding, on ROS versions, of ROS that are no longer supported.
Experts mikrotik, ignored, all these posts, which indicate problems mtu and l2mtu, platform x86.
He pointed out that this problem also affects another branch.
So I now indicate in each branch that there is this problem?

_____________________________________________________________________________________________

В поддерживаемой актуальной stable и longterm версиях, эта проблема существует, поэтому ее необходимо исправить.
Господа из Микротик не поддерживает устаревшие ветки ROS ? Кроме стабильной 6.43.8. Верно ?
Так же в соседних ветках, пользователи указывают на аналогичную проблему с bonding, на ROS уже не поддерживаемых версиях ROS.
Специалисты mikrotik, проигнорировали, все эти посты, в которых указывают на проблемы mtu and l2mtu, платформы x86.
Указал, что эта проблема так же затрагивает и другую ветку.
Так что мне в каждой ветке теперь указать, что есть эта проблема ?

And also your previous post was in Russian only. This is an International forum, please respect others and post here in English only. Thanks in advance.

ok, fix it.

So I now indicate in each branch that there is this problem?

_____________________________________________________________________________________________

Так что мне в каждой ветке теперь указать, что есть эта проблема ?

Nope, problems must be reported to support@mikrotik.com. This is community forum, if problem cannot be solved by changing your config - we can only sympathize. Or recommend to write to support@

Nope, problems must be reported to support@mikrotik.com.

This is done, waiting for an answer.

Found possible bug:

When you add subnet into "available from" field for SSH service, under IP Services...SSH becomes inaccessible, even if PC is in that subnet.

Code: Select all

ssh_exchange_identification: Connection closed by remote host

It seems only to affect SSH though, for limiting access to http, https it work just fine.

Basically happens only: on Hap Ac2 at AP mode (full L2 bridge), still limiting SSH should work, IMHO...

bug.
I choose in settings "IP.IPsec.Peers " certificates for the server and remote server. But after some time, the certificates disappear and become "none". I use the method: rsa-signature-hybrid.
why does the certificate disappear? Sometimes it happens that the server and the remote server - certificates themselves become the same.

Bug 2
if you use https to connect (together with the certificate), sometimes there are delays of 3..5 seconds when opening various settings. all open quickly but then go to what that tab to view the settings and there is a delay for 3..5 seconds. nothing shows for 3..5 seconds. another problem with https is that it shows different settings compared to winbox.

this is possible due to access to jsproxy, it is not.

There's something really strange going on with DFS. I just got a new INTL RB4011 and set it to "united states" regulatory domain with "manual txpower" and 80Mhz channel. The AP is getting stuck in radar detection half of the time (even though I'm 100% sure there're no weather or military radars around, since I live practically in the forest). For example now (see screenshot) it was in "detecting radar" mode for 10 minutes.
It's simply not acceptable for me and AFAIK there's no way to disable DFS while still keeping the scanlist of the regulatory domain (or is it?).

Use manually non DSF channel (5200, 5220 or 5240). Problem solved.

@kiler129 I had this problem. After change change:
-Frequency Mode: superchannel
-Country: no_country_set
-Channel Width: 20/40/80MHz eeeC
my problem is solved. Lets try

You can't use anymore country settings and frequency mode different from regulatory domain.

hello support!
Could you give us more information about this changelog entry?

*) wireless - improved stability for 802.11ac;

What have been changed? Any improvement in NV2?

Thanks!

Would like to know as well. My RB4011 keeps disabling 5ghz WiFi after a few days (see graph). Only a reboot can bring the WiFi up again. Wondering if this has been fixed

I am having the same problem.

...
mikelaurense - Does interface actually gets disabled? Or it becomes inacessible? If it disabled, then someone has done that manually. Please provide supout.rif file tp support@mikrotik.com. Make sure that file is generated while interface is "disabled".
...

I'm facing the same issue as mikelaurense. When this happens for me, I can see that the wifi interface is shown as "S" instead of "RS". When going in the settings, I can see "Enabled" is still checked but the interface is not shown as "Running". The wifi network in itself becomes inaccessible, as in, it doesn't appear anymore when scanning from another device. There is nothing in the logs about the interface being disabled. Disabling and Enabling again the interface does not fix the problem. Rebooting does.

This happens every few days seemingly at random hours, always during the day when nobody is home (virtually no traffic on wifi) or at night one I sleep (virtually no traffic on wifi).

hello support!
Could you give us more information about this changelog entry?

*) wireless - improved stability for 802.11ac;

What have been changed? Any improvement in NV2?

Thanks!

Would like to know as well. My RB4011 keeps disabling 5ghz WiFi after a few days (see graph). Only a reboot can bring the WiFi up again. Wondering if this has been fixed

I am having the same problem.

Me too

I launch the terminal, I create the rule.
In the parameters an intentional error, the rule applies.
I look through the winbox, I see a new error parameter perouting.
This is normal ?

This is normal ?

It is. Absolutely. You have simply added a rule to a custom (user-defined) chain named 'perouting' that you can now jump to using 'action=jump' rules.

And, by the say, this is in no way version-specific, so in the future please refrain from posting such questions to version-specific threads.

...
mikelaurense - Does interface actually gets disabled? Or it becomes inacessible? If it disabled, then someone has done that manually. Please provide supout.rif file tp support@mikrotik.com. Make sure that file is generated while interface is "disabled".
...

I'm facing the same issue as mikelaurense. When this happens for me, I can see that the wifi interface is shown as "S" instead of "RS". When going in the settings, I can see "Enabled" is still checked but the interface is not shown as "Running". The wifi network in itself becomes inaccessible, as in, it doesn't appear anymore when scanning from another device. There is nothing in the logs about the interface being disabled. Disabling and Enabling again the interface does not fix the problem. Rebooting does.

This happens every few days seemingly at random hours, always during the day when nobody is home (virtually no traffic on wifi) or at night one I sleep (virtually no traffic on wifi).

After contact with Mikrotik support I changed channel width to ‘20/40/80 MHz XXXX’. This does seem to improve stability, although it did happen once or twice again since changing it

hello support!
Could you give us more information about this changelog entry?

*) wireless - improved stability for 802.11ac;

What have been changed? Any improvement in NV2?

Thanks!

Would like to know as well. My RB4011 keeps disabling 5ghz WiFi after a few days (see graph). Only a reboot can bring the WiFi up again. Wondering if this has been fixed

I am having the same problem.

LTE bell on any phone - kicks wifi on RB4011, any channel from 36-161!

Please see how shows "Bytes" in IP-mangle. There are non sense data.
Please fix it in next release.
This problem persists over many versions

Thank you

abrandecky please generate and send supout file to support.

Which one is next stable release? v6.44?

My 750Gr3s seem to show a memory leak in the proxy. With proxy disabled the memory usage is around 42mb. If you enable the proxy but don't send any traffic the memory consumption stays at 42mb. As soon as you open the web proxy interface in winbox the memory consumption jumps to 64mb (still no traffic via proxy). As soon as any traffic flows via the proxy the memory consumption jumps to 102mb. At the same time, if you go and look at the proxy it says Total RAM Used: 996KiB. So something somewhere is leaking close to 60mb. This did not happen before on 6.42.7 which is the version I upgraded from.
Does anyone know how to rectify?
I'm afraid of upgrading my 941 and 952 devices as they don't have the 60mb for the leak and most of them are remote (like 20 hour plane ride away)

I'm afraid of upgrading my 941 and 952 devices as they don't have the 60mb for the leak and most of them are remote (like 20 hour plane ride away)

"20 hour plane ride away", my god Please don't. Stay on bugfix or Long-term how it's called now.

New version 6.43.11 has been released in stable RouterOS channel:

viewtopic.php?f=21&t=144949