I don't know if it is a known issue, I only know that I do not experience it.
(and I have a similar config running under 7.12.1)
Yes, that is bad!Yes this device is restored using backup from another device. Is this something bad? And how to fix?
As I said, I did not know that AMPERE was a "CPU platform".First hit when searching for "Ampere CPU platform"
On the "managed" tab it works. I do not know about the "neighbors" tab, rarely use that.Never has here. Double click on that line and all it does is populate the top box.
Already works!Double click on an entry in Winbox to connect.
It is the fault of your board manufacturer or seller.something cosmetic on X86:
board-name: x86 To be filled by O.E.M. To be filled by O.E.M.
But you pay 3 times the money for a comparable product. Your decision.Dumbest I've heard. Can't even imagine Cisco or Juniper putting out a stable release that bricks the product.
I think not. I still see so many "introduced in 7.13x" bugfixes that I think there have been major changes and 7.12.x should be the longterm release.7.13.5 one more step against Long Term release :)
It is better not to do it. Just remain on v6.How can one run ROS 7 on a hAP lite? I've tried this several times and even just as a CPE (no firewall filter rules, a blank config in fact) it was barely unusable.
Do you observe actual decreased performance? Or are you just obsessed by what is shown in that dialog?Thanks for reply, Its always show 1200Mhz if i use os 7, never change also in Full user load, Only if i downgrade to OS v6 then CPU again show 2600Mhz, Any idea how to solve this issue?
That is not surprising because your question is completely unclear! You ask for a new device and think all existing devices that fit the bill are not right for you...May be you don't understand the direction. Applying for a router, not a wireless one!
Like CCR2004-16G-2S+? Maybe CCR2004-16G-2S+PC?Can we expect new "Ethernet routers" ?
Something with better CPU, RAM and so on ? Like 1GB memory ? x64 bit 4 cores or more ?
Of course not. It was not in the release notes, so why should it be there?We still don't have information about AS
and:Please, stop calling megabits as MB.
MB = megabytes
Mb = megabits
You can do that with two local EoIP interfaces.Bridge-To-Bridge joiner.
Via RADIUS or via access list. I also want to have that, I use it in the old wireless driver.do you mean via RADIUS?Please make dynamic vlan assignment possible for wifi-qcom-ac wireless driver
And even worse: 15.3MB FlashProblem are all ARM wireless devices with 16MB flash.
You can run SwOS on that. Anyway, I would never buy that kind of thing from MikroTik.Too bad the CRS326-24S+2Q+RM is delivered from factory with RouterOSv7 and 64MB of RAM.
True, you should not upgrade that kind of vintage device to RouterOS v7 unless you are prepared to live with performance issues.I do feel that 64MB of RAM is on the low side for ROS7.
/interface detect-internet set detect-interface-list=none
Yes, but a lot of buffering of the traffic is actually a bad idea. Especially when there are not multiple queues and DSCP based priority.More RAM helps at buffering the traffic, at my understanding.
They are no longer sold but they are still supported. Updates for RouterOS are released for this model.What they do have in common CCR1009 and EOL.
That is a different model! And different config as well.
No fasttrack!
Yes, that is great! I have been asking for that for many years...I would like to say THANK YOU VERY MUCH for this improvement in 7.14 beta8:Code: Select all*) traffic-flow - use 64bit counters for v9 and IPFIX flows
Did anyone already check by how much?What's new in 7.14beta8 (2024-Jan-22 21:07):
*) package - reduced "wireless" package size for ARM, ARM64, MIPSBE, MMIPS devices;
Of course until at some point the authentication or some other fundamental protocol detail is changed in some newer RouterOS version, as has happened before...Even if we make a winbox that is not the same as the good old Windows 95 inspired version, you can always just keep using the old one :)
Why?1) Check the bridge’s protocol-mode, with AX2/AX3 it MUST be default value (rtsp).