The datasheet of your DoorBird says:MikroTik uses RJ45 mode B pinout for power distribution
Conclusion: you can't power this device with your Mikrotik cAP AX.PoE 802.3af Mode-A, 10/100 Base-T
The datasheet of your DoorBird says:MikroTik uses RJ45 mode B pinout for power distribution
Conclusion: you can't power this device with your Mikrotik cAP AX.PoE 802.3af Mode-A, 10/100 Base-T
/interface/wifi/export
Maybe post your device config and installed packages in a separate topic. This needs further inspection.Another 10 MB of RAM left within 1 day.
/system package update
set channel=testing
add action=accept chain=input comment="defconf: accept UDP traceroute" dst-port=33434-33534 protocol=udp
Embarrassing using testing release on your clients network devices...🙄embarrassing that client's network was broken due to rogue DHCP on their network
"Some" is a good indication for either a configuration issue (most probably) or hardware defects.Upgraded to 7.14.3 - still some of my cAP ax tend to crash with 5 GHz enabled. :-(
Have you reported that fact to support as well?... since when the RB5009 can no more recognize the stick, if I put any other device... it is the very same.
With a 1000Base-T port it won't be more than this.It should be 1GBps at least
I wanted to log stuff to a USB dongle
Yes, his point: if you don't need the LTE modem - then don't spend 2,5x price of a HAP ax3 for a Chateau LTE18 AX.Your right. I get confused on the Chateau, most are 16MB storage. And I kinda assumed @normis has some reason for his comments however
why this second router?Again, setup is ONT -> Rb50009 (bridge mode, handle PPPoE) -> second router in DHCP (avoid double NAT) -> clients/lan/rest of network
yeah, reading is one thing. Understanding is the part that will be tricky for you (with your attitude you show us).(not that I will spend much time reading)
And on that Microsoft DHCP server you do have configured static IP addresses for your iOS devices too?If using Microsoft DHCP server (obviously NOT on the same network!), I do not have any such issue with same devices
As someone who has noticed this behavior and already complained elsewhere: of course it is a bug IMHO. Mikrotik may see it differently.But, that is just a "winbox bug", that could be fixed with some additional code in winbox. After all, it knows which items you have changed.
I guess this has lots of metal construction where the plasterboard is attached to.The roof to the attic is plasterboard(don't know if this is the correct English term ) I think, so I'll. give it a try.
LOL? Seems not to be easy for MT. add drivers in a testing release: people moan. Exchange drivers in beta (!) release: people moan. Exchange drivers at all: people moan. 🤣A bit late in the beta cycle to be dropping in newer drivers.
Replace the 5.5dbi antenna with an e.g. 2.5dbi one to change characteristics of coverage. I did not know that I had to explain that.Now what legitimate use case would that be?
Sure they are published on testing channel. 🤔but MikroTik does not publicly release alpha versions
Within 2m connecting and 6m away not? that's odd indeedThe Android devices that can't connect 20 feet away do connect 6 feet away.
Remove word "EU" and it says what you actually mean: "regulations probably exist for a reason, but they are not for me"EU regulations probably exist for a reason, but they are not for me.
Can confirm this true on wifi-qcom-ac, country Austria as well (Chateau LTE12, cap ac)Addendum: I don't remember which countries this is true for, but in my testing hAP ax3 seemed to really love 5500/Ceee when frequency was unset.
Can this be real? Hap ax3 has 1GB of RAM.This is probably true-memory overflow, and subsequent reboot in order to clear it (at the moment, the rest of the memory is 30-35 MB)
see viewtopic.php?t=206196how about enabling us to boot the router as it used to be without a password
Still at 7.13.5. Space is plenty. If one with a 16mb arm devices likes to have the benefits of wifi-qcom-ac > 7.13.x is your friend.Personally, getting older routers to 7.12.1 might be a good call while we wait – since that already in the way before 7.13+.
*) health - added "cpu-temperature" for IPQ50xx devices;
And still my comment about upcoming beta7 custom ACME server got deleted as well?
Please keep this forum topic strictly related to this particular RouterOS release.
Friendly reminder ...
I do not understand. What else?It isn't
/system/routerboard/wps-button
It worked in 7.14?Bug in 7.14.1 on CRS328-24P-4S+: Blink button and blink cli command does not work
It seems like MikroTik is aiming to enter the brick industry. They have been increasingly producing more bricks lately.Yet another bricked hAP ac2 at the remote location while upgrading from 7.13.4.
free-hdd-space: 0
total-hdd-space: 15.2MiB
Yes, I switched to "testing" branch first time in years. 7.13 was already tough to swallow and then 7.14. Now I go YOLO as testing branch has the fixes first. LOLThere's a new stable in the beta channel.
16:32:04 script,error executing script from console failed, please check it manually
16:32:06 system,error,critical error while running customized default configuration script:
Does this fix the issue where the interface remained in "selecting channel" state after a radar event? e.g. viewtopic.php?p=1057657*) wifi - improve channel selection after radar detection events;
script,error executing script from console failed, please check it manually
*) console - added log for script execution failures;
Mikrotik, please elaborate on this. I can't find available-channels nor channel-priorities anywhere Thank you.*) wifi - rename "available-channels" parameter to "channel-priorities" and include desirability rating for each channel;
*) system - fixed "cpu-frequency" for CRS3xx ARM devices;
It exists: hap ax2
At the very least make one HaP AC2b, with more storage!
Thank you! 👍*) wifi - improve channel selection after radar detection events;
*) wifi - rename "available-channels" parameter to "channel-priorities" and include desirability rating for each channel;
Well, you've reverse engineered Winbox? coolThe winbox GUI presents you with a panel with all possible settings, reads the existing values in it and then you can change them and submit the whole thing. There is no way to submit individual fields.
People will still hit the upgrade button YOLOmove this version to v8
*) system - expose "lo" and "vrf" interfaces;
Different experience here with a U6+. The channel selection on "auto" is aweful. It even chose the same channel 1 of the only other 2ghz AP around. Pretty dumbI don't seem to worry about 5GHz channel selection and/or DFS. It just works out of the box.
Why don't you try it out?I assume that CAPsMAN controlled access points will stop working if CAPsMAN is not accessible?
Does this also mean a new Windows Winbox application?native Linux Winbox