Im using hAP ax3 at home with last rc version for testing and no issues even with these versions...
This ābeautifulā dashboard is already too complicated for the average joe.
Also back in like 2018-2020 their dashboard used to be actually good for wifi details. Now it's just useless and shows you watch porn too much
Please open a separate topic.
All my axs are working fine
I quick update for anyone that could be useful.
Yesterday I upgraded my Chateau PRO AX with wAP ax from 7.20.1 to 7.20.7 I'm using the new CAPsMAN, OSPF routing for internal networks, SSTP to my brotherās house - routing over it. ZeroTier and Back to Home VPN. So far, no issues noticed.
I've just upgrade 41 devices from 7.20.6 to 7.20.7 LT.
Still no errors and all is fully working (not like 7.21rc6).
RB5009, CRS310, CRS326, ac3, ax3, ax, RB4011 and hex
One thing I forgot to test and I just did while everyone in the house is asleep.
Support for capsman traffic processing for wifi-qcom drivers is still not supported in 7.20.7. I just tested it, when I turn it on in the configuration, Iāve got an error that the data channel is not supported.
Hopefully it would be available in later versions, one of the reasons I like it even if in my case the wAP ax is directly connected to the PoE port of the Chateau PRO is that with capsman traffic processing, I could view the WiFi traffic for both channels on the CAP directly on the CAPsMAN. Itās not a killer feature, but a nice to have in this case.
Of course not. It was added in 7.21beta2.
*) wifi - added CAPsMAN forwarding support (datapath.traffic-processing=on-capsman);
Unless you see this changelog item. IMHO it is a feature of 7.21 and won't come to 7.20 long-term.
Based on experience with legacy (wireless) CAPsMAN and initial experience if 7.21rc users enabling capsman forwarding will almost certainly notably reduce WiFi performance. So beware whenever you get to enable it.
Iām aware of that fact
Iām using the old CAPsMAN on version 6.49.18 on some now legacy devices, the controller is a RB3011 device - very capable, very powerful for the purpose thatās being used. So even with on-capsman traffic processing, the amount of traffic I could achieve on the WiFi exceeds the Internet capacity of the remote locations where the CAPs reside, the RB3011 is powerful enough and itās not overloaded. So in this particular scenario - itās just fine. In my current case I have a Chateau PRO AX which is totally overkill in terms of capacity. But I still havenāt tested it with 7.21RC because this is my home network and my wife works from home every day⦠so upgrade windows are just through the night and I will wait when this feature becomes more mature.
Another user posted some test results in another thread ... and depending on particular configuration, CAPsMAN forwarding could reduce WiFi throughputs even down to one 10th of "native throughput". And he was using decent devices both for CAP (IIRC he was using cAP ax) and for CAPsMAN (again IIRC RB5009) with CPU capacity to spare on both involved devices. It seems that at least for (large) portion of throughput drop the reason is added latency involved in frame processing.
From your comment I see that you have never ever seen Unifiā¦Why do you comment something you never seen???
Of couse you can adjust the home screen⦠this device cost 100ā¬.
It has advanced firewall with DPI inspection
Wireguard server and client - I use client only for two devices as conection to Proton VPN. to the server I have connected few Mikrotik wireguard clients.
It can block acces from any country by few clicks. It can bolock youtube to specific device by few clicks. You can see from which country is anyone trying to hack you..
Zero traffics is there because I did not connect any WiFI AP from UIā¦
You can filter which devices are downloading from youtube etc. but it is not ment to spy and if you need you can buy more expensive HW from UI and it can decode https traffic onlineā¦
You can give a name to HW and see the name in the GUIā¦you do not need to search which device has which mac adress.
I noticed you're not showing the OSPF or VRRP or etc configuration... Anyway, the long-term release thread is not the place for feature requests.
This release broke my CCR2004-16G-2S+PC internet connectivity. I had to downgrade to 7.20.6 (stable). Not impressed. This has been reported by someone on Reddit too: Reddit - The heart of the internet
Suspect it must be this change: bridge - fixed dynamic switch-cpu VLAN creation (introduced in v7.20);
When I managed to log into the device, I could see some additional dynamic bridge vlan entries reloating to the switch CPU.
I have a fairly standard routing setup.
Upvote +1
What about L2TP or PPTP. I know that PPTP is not secure but I want my advanced features. And dont make me start about OSPF, BGP, ISIS, EVPN, MLAG (I know it supports some of these featuers but there are problems with them and MK is working on these features) and the device that they call WAN SW
.
And their documentations cant be called documentation.
I would rather say that at Mikrotik you reach directly the things which are under the hood at Unifi
Can not run scrips via snmp in ros v7.20.7. Reports āNo Such Object available on this agent at this OIDā
yes @arm920t
you are right ![]()
MIKROTIK-MIB::mtxrScriptName\[1\] = LNMS_vlans
MIKROTIK-MIB::mtxrScriptName\[12\] = backup
MIKROTIK-MIB::mtxrScriptName\[13\] = update
MIKROTIK-MIB::mtxrScriptName\[14\] = backupp
MIKROTIK-MIB::mtxrScriptName\[15\] = global
Cache miss for snmpget MIKROTIK-MIB::mtxrScriptRunOutput.1, grabbing fresh data.
SNMP\['/usr/bin/snmpget' '-M' '/opt/librenms/mibs:/opt/librenms/mibs/mikrotik' '-m' 'SNMPv2-TC:SNMPv2-MIB:IF-MIB:IP-MIB:TCP-MIB:UDP-MIB:NET-SNMP-VACM-MIB' '-v2c' '-c' 'COMMUNITY' '-OQXUte' '-Pu' 'udp6:HOSTNAME:0:24:111::9\]:161' 'MIKROTIK-MIB::mtxrScriptRunOutput.1'\]
MIKROTIK-MIB::mtxrScriptRunOutput\[1\] = No Such Object available on this agent at this OID
god damn LTS
how naive i was to trust this update
well
looks like every version
LTS, RC, Beta have same SNMP problem
MIKROTIK-MIB::mtxrScriptRunOutput\[1\] = No Such Object available on this agent at this OID


