You cant use 80+80 on cap ax, or any ax device at this point.Sorry. Mistyped. Updated. I was talking about 80+80 channel width.I don't even understand the question..
Test and see, but I suggest learning and doing full vlan setups.Good to know, will test with your example on my test setup, before i used capsman i had setup with trunk to the APs. No hybrid ports like i have now.
No, I still see all issues appear. I also see SA query time outs whit out FT enabled as ToTheFull mentioned.Out of curiosity, has 7.10rc1 fixed issues with AX devices?
What device is it?Still rebooting everyday and I have WPA3 disabled. Before the 7.9 upgrade everything worked great.
No response from Mikrotik support on my support ticket.
Would installing the 7.10 beta help?
I am planning to do tutorials, but not right now. For that I need time and be sure my knowledge is solid, so I'm not spreading false information.@maigonis
So we can expect some CAPsMAN tutorial from you ?
I do use capsman at home for 2 APs, its a learning opportunity.Certainly not.
Is it worth the trouble for just 2 AP ?
To hear better your phone behind walls.What is sensitivity good for???
No, I mean you buy 4 units.You mean it'll use 5GHz as a backhaul so only 2.4GHz will be available for client devices? How AX2 is different from AX3 here?
You can use ax2, but regular AP/router have only one radio, so 5ghz band can mesh, or be AP - not both at the same time.Can't wait for Audience unfortunately. Won't AX2 allow for 5 GHz meshing?
In that case wait for audience ax, or pair two hap ax3 units together if you want 5ghz meshing. It means one ax unit will mesh, other will be AP for stations.I want wi-fi 6 functionality.
For meshing audience was created.I want to connect one AP by wire and other two wirelessly so to create mesh network.
Messed whit mcs indexes?I am just some SOHO guy, but when I had customised rates enabled my WiFi performance was terrible. It would randomly drop speeds to 30Kbs on the 5Ghz channel.
Went back to default rates, and the problems are gone.
Something must be done in this case, stations will misbehave.What is "helping" here? The lingering packet is dropped after 20 sec. The connection is not dropped by the AP. It's up to the client to drop the connection if there is no activity.
AFAIK there will be no capsman forwarding.I really hope they'll add support for capsman forwarding in the next release, not the best solution to add vxlan/eoip everywhere and bridge cap interfaces locally
Tnx.Yes it is.
That usually is an existing firmware bug, do netinstall.Cant upgrade 2x LHG 5 AC from 6.49beta22 to 6.49 Stable, not enough space, i got nothing on internal storage...
Second this, open ports are a bad ides.1st: never ever open rdp to public.
Use a VPN or allow RDP port only for certain trusted static IPs or ddns
In GNS3 you can create all kind of setup and if you break something you can easely restore project.Why don't you practice CapsMAN on a physical device ?
Yep, its out. But still, I cant get storm control working.I just got the SwOS 2.13 on my device via auto-upgrade.
swos-css610.png
5GHz is a way to go nowdays, not because of MT WiFi quality. 2.4GHz have way too noise, interfierance and low troughtput.I have done channel analysis near the routers and I have to say: channels are pretty busy :D
I am considering 5 GHz more and more.
Flawless victory.Mikrotik fought the Logic and Mikrotik won.Yes, that would be logical.Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.
But I cant edit interfaces whit dynamic, that is the issue.I have dynamic, it's ok.