I would be happier if I lost the bet because we would have wifi 7 devices...I completely forgot! The year 2024 is long over, and it looks like I’ve lost my bet. Congratulations, gigabyte091!The bet is on.
Who let the newbie here...Haha, I don't think I will be a real mikrotik guru in this lifetime.
Agreed.So why to not allow some winbox.cfg where all that bells and whistles could be set on/off?
Do you have multiple Mikrotik APs ? If you don't then there is no need for CAPsMAN.Also I got some problems configuring AX capsman, because capsman filtering was removed from ax, so I made it standalone.
Same here, after third attempt winbox was installed, W11Pro 23H2 build: 22631.4460Same problem here.
WIN 11 23H2 22631.4460
I corrected the mistake, it's hard to write on the phoneLooks good to me! ;-PP
First line is not correct![]()
7.17beta2Which version did you come from, just curious..Just tested with my RB5009 and upgrade to 7.17rc2 went without a problem. I did a config backup just in case.
Do you have a partner?Why size would influence the decision? Being bigger I mean. Trying to understand
system logging add topic=wireless action=memory
No, error message is displayed almost immediately so nothing is visible in bridge/vlans.After a station with non-default PSK (and hence custom VLAN ID) connects to AP, does wifi interface become member of that non-default VLAN?
Only supported on wifi-qcom interfaces, if wifi-qcom-ac AP has a client that uses a passphrase that has vlan-id associated with it, the client will not be able to join.