Ill post it here and i hope all u mikrotik engineers will take a look at that comment. We need u to introduce codel algorithm, it is the best working feature this time we speak in routers.
Hi normis, from here - https://mikrotik.com/download
Now as i can see links were updated because it points correctly so yes, after my report now it;s fine.
P.S i’m not using any caching proxy etc
Hi,
I forgot to mention that I didn’t use protected-bootloader. But if I had used, the 300s reset would have erased mikoritk even with protected-bootloader?
thx
eifLZ9D8zSwW - Are you sure that you did not enable feature by accident? Or simply enabled it without knowing what it does? Wiki page will explain how it works. Your solution would work only if these 500 seconds are between min/max timeout values. Wiki page should explain how long you have to hold that button pressed if feature is enabled.
Again - we strongly recommend to NOT use this feature if you are not aware about how it works. If you will not know min/max settings, then you will not be able to recover device in any way.
I found a couple of strange entries in the routing table after the upgrade on my hAP ac. The upgrade path was the following: 6.40.5 > 6.41 > 6.41.1 > 6.41.2. Not sure when it happened exactly.
The new routes to 0.0.0.0/32 in the list which were not there before.
According to the RFC 3330 it is kind of special address, and I cannot understand if it was added on purpose or by mistake during the upgrade.
I’ve got trouble connecting older devices such as Android 4.0, iPhone 4 or Blackberry probably since Rel. 6.41 to access points using CAPsMAN. I downgraded to Rel. 6.35.4, which works well with these devices. Newer devices work (tested: iPhone 6, iPhone .
Currently installed on all devices: Rel. 6.41.2. The error I get is: “received deauth: class 3 frame received (7)”.
Does someone have a clue, what to do. Users are complaining heavily.
I have seen a wireless issue on two of the RB941-2nD I have. I don’t know if it is the same or not.
Initially it started with wireless devices intermittently dropping. Later on it progressed to more severe intermittent connectivity - about 50 percent of the time there will be no devices connected. Logs would show key exchange timeout and drop the wireless devices about every 30 minutes, then it changed to about every 2 minutes. It progressed further onto the wireless devices not being able to hold stable connection for more than 2-3 seconds, it would not matter if the frequency was set to auto or set frequency. Initially devices tried to connect frequently, then connection attempt became more rare, until almost no connection attempts would be made. Every time the router kicked out the device for unicast key exchange timeout. But it became even worse - the devices were not trying to connect because they could not see the SSID. Those two devices now (no longer at customer) do not advertise SSID no matter what, I can’t see it even with kismet. It seems like the radio RF portion just gradually and eventually died after the 6.41.1 upgrade. Multiple resets, and power off/power on did not make any difference.
Needless to say I had to replace these two. Initially they did not have the 6.41.1 firmware installed when they started being weird. When I got the issues, I installed the 6.41.1 firmware which made things worse and ultimately the WIFI portion just does not seem to work at all. The whole degradation from a fully stable working router to fully non-discoverable wifi (even on scans) started about a month after the 6.41.0 upgrade, and tool like 3-4 days with a 6.41.1 upgrade in the middle.
Regular AP bridge, no CAPsMAN, 2GHz-N-only band, 20Mhz channel, 802.11 protocol, WPS disabled, Hide SSID not set. Frequency - regulatory domain, Country - United States, Data rates - Default, Distance - indoors, Preamble - long/both
Hmm, tried setting the country to something else - Latvia - it would make the SSID temporarily discoverable (for about 5-10 seconds) and then it will die again. At the same time the status will claim it is running, at -112dBm noise floor and 2427/20/gn(20dBm) channel (sometimes 2422).
Nothing informative in the logs, even if wireless is on debug
Hi strods, i’m not using fastrack and tls rule was in top of all other forward chain rules.
Hm as i can see there is a fix for this feature in latest rc
What's new in 6.42rc24 (2018-Feb-08 09:42):
*) firewall - fixed "tls-host" firewall feature (introduced v6.41);
Is this related to my issue?
L.E: tested again and now it’s working.. odd.