Of course I did - and the matter of fact - I ALWAYS use local forwarding enabled, cause capsman forwarding gives me like 10% of wireless perfomance.Have you tried local forwarding vs capsman forwarding to see if there's a difference?
But you shouldn't you expect > 500Mbps with three chains on 5GHz ac? I consider 100Mbps with that hardware pretty slow, that speed is already achievable with 2.4GHz dual chain n.Personally, I get > 100Mbps using wAP AC + RB3011 running CAPsMAN, local forwarding.
I live in suburban area, big house, closest neighbout is literally ~100m away. Not corwded at all - area is "crowded" by only me, myself and I.Personally, I get > 100Mbps using wAP AC + RB3011 running CAPsMAN, local forwarding.
How crowded is the wireless around your place?
Are APs locked to CAPsMAN and using encryption?
Could you post a screenshot of winbox CAPSMAN-Channels?
That's what I'm talking about - and I've metnioned it already (no?) - that using dual-chain 2.4Ghz band with 802.11n protocol, I can't even beat through Internet channel! 100mbps are being choked by poor wireless perfomance. I mean, I'm experiencing overall wifi perfomance drop, not only PC and 5Ghz 802.11ac connection.But you shouldn't you expect > 500Mbps with three chains on 5GHz ac? I consider 100Mbps with that hardware pretty slow, that speed is already achievable with 2.4GHz dual chain n.
MAIN2.pngCould you post a screenshot of winbox CAPSMAN-Channels?
When I lived in the city, I've used to have 1Gbps internet channel. Though, it was roughly 1 Gbps - more like 900 mbps at night (best), and down to 600-700 mbps daily. And asus RT-AC66U as a router - no complicated wifi stuff, just a a swetpot with 3 antennas.Looking at your first screen shot in your first post, I'd say that's a decent connection.
You're connected at VHT MCS 7 with two spatial streams and short guard interval resulting in 650MBps connection rate at 80MHz.
Keeping in mind that actual real-life throughput is roughly 50...65% of the w/l connected rate, you're in a pretty good shape.
Increasing throughput further from here from here would ideally be a different wireless client supporting three spatial streams which would give you 975MBps @ VHT MCS 7, resulting in roughly 500...650 MBps real-life throughput.
-Chris
What, do you mean frequency? No way, it gonna throw overlapping ones in.MAIN2.pngCould you post a screenshot of winbox CAPSMAN-Channels?
CAPsMAN-Channel. Control Channel under CAPsMAN is what I need to see it should be in auto mode.
Yeah, seems like it. Furthermore, as I mentioned before (here or in support ticket?), MIMO seems to be broken broad - "at all" - if I can say so - because I really can't imagine how it can be broken.So MIMO is broken in some way that prevent any speed gain from additional chains? Interesting observation, let's hope that this is reproducible and fixable by mikrotik.
yeah, np mate, any idea is good!Hi RobCo,
I really feel your pain, I do.
Although I'm not convinced my post will help you, it may spark some insight in you.
1st thing - are you sure your clients are actually WIRED with 2 separate antennae?
2nd thing - for MIMO to work well one needs a good spatial separation for all spatial streams, i.e. there should be no correlation between the 2 spatial streams. This is hard to achieve with ordinary antennae and LoS between AP and client.
You could also try iw phy from most Linux boxes to check if your client WiFi cards support MIMO.On Windows you can try netsh wlan show wirelesscapabilities from admin CMD.
Yup, that's what I'm talking about.Yes, you're totally running @ 1 spatial stream, i.e. 1 chain.
Also, you're not wanting too much of your HW, you're just wanting what you paid for, which according to MT's own page is 1300 (or 900Mbps if you consider the real life). What you get is a far cry from the advertised speeds...
Check this out - https://www.cisco.com/c/dam/en/us/produ ... c383047840
According to the link from this renowned manufacturer of networking equipment above, you're not even getting 256QAM! 256QAM should yield ~433MMbps.
Honestly, I don't know what else to suggest for troubleshooting. Had we some fancy test equipment things would have been easy. Maybe if you can temporary get another wAP for testing, you could try setting up a WiFi network between those 2, and see how they play it out?
Wish things just always would work as advertised. FTFYWish things just always would work as intended (wanted)
The wAP AC CPU is likely maxing out at that bandwidth.
Hey guys, sorry for the delay.Getting ~500Mbps with multi-stream iperf3 means all WiFi technologies are kicking in, i.e. they are working.
What R1CH says may be the truth, sadly... Can you start profiling on the wAP AC and see how much the CPU gets loaded during iperf?
If local forwarding, wAP's CPU only needs to copy packets from wireless interface (which alone is a CPU-intensive operation on RBs) to ethernet interface. Gateway (for simplicity's sake let's say it's CAPsMAN device) takes those packets off ethernet and routes them to WAN.... it local forwarding mode enabled. With CAPsMAN forwarding, with totally the same load applied, wAPs go insane 80-90% load, wireless speed drop a little too. I can't really understand it, since, shouldn't it be other way round?
To have MIMO (multiple spatial streams) working, those streams have to be well separated (radio-wise) from each other. A great separation technique is use of two orthogonal polarizations (if usual stick-shaped antennae are used it means having them oriented at angle of 90° between them ... but that only works for a pair of antennae). A good technique is to have antennae separated spatially ... by at least a few wavelengths. Wavelength at 2.4GHz is around 12.5 cm, so those antennae should be at least 30 cm (a foot) apart (this is a bare minimum, more than half a metre would be better). It is easier to get enough spatial separation at higher frequencies, hence higher number of spatial streams on 5.xGHz band (wavelength of less than 6 cm, hence same 30 cm separation is pretty good).Still get 0 improvement with 3 spatial streams, 3 chains working between wAP AC client and Asus AC68 unit.
Well.... you know, this stuff relates to my problem as bad as it can be at allTo have MIMO (multiple spatial streams) working, those streams have to be well separated (radio-wise) from each other. A great separation technique is use of two orthogonal polarizations (if usual stick-shaped antennae are used it means having them oriented at angle of 90° between them ... but that only works for a pair of antennae). A good technique is to have antennae separated spatially ... by at least a few wavelengths. Wavelength at 2.4GHz is around 12.5 cm, so those antennae should be at least 30 cm (a foot) apart (this is a bare minimum, more than half a metre would be better). It is easier to get enough spatial separation at higher frequencies, hence higher number of spatial streams on 5.xGHz band (wavelength of less than 6 cm, hence same 30 cm separation is pretty good).Still get 0 improvement with 3 spatial streams, 3 chains working between wAP AC client and Asus AC68 unit.
And that must be done on both ends of a radio link ... or else things don't work as (naively) expected.
RB4011 have it's own set of quirks and issues, 5GHz WIFI is very much broken as you can see here: RB4011: wlan1 disabling itselfYou'd be in much better position with an (overkill) RB4011 WiFi and RouterOS 6.45, which enables all four chains correctly.
UPD: Ok, seems like it, I've managed to get 530 Mbps upload from PC to NAS using WLAN. Still, download is much worse.Due to latency at various internal points (wireless microprocessor, kernel scheduler, hardware interrupts), the wAP ac processor is a limiting factor here. As the MIPSBE SoC is older and cost-optimised, some of the internal datapaths may be a bit limited too.
You'd be in much better position with an (overkill) RB4011 WiFi and RouterOS 6.45, which enables all four chains correctly. I really wish Mikrotik had a dual-core >1GHz processor ARM AP with spatially-diverse 3-chain 5GHz and 2-chain 2.4GHz radios.
Finally, I suggest measuring WiFi throughput with iperf UDP, so you can decouple TCP congestion control.
@RobCo can you share your config file please? I'm only just beginning to experiment with CAPsMAN - running on MT HAP AC with hardwired AP's. I've enabled CAPS on the HAP as well so clients can connect to it's wireless or one of the remote AP's.Ok, so I was wrong and it was unfair to say "MIMO doesn't work", etc, etc...
MIMO works! I've made couple of IRL tests (not iperf) - so far, even 3x3:3 makes sense. And note that AC68 is not in the best position - bandwith rate is around 877-1300mbps, jumping around due to close distance - adapter is too powerfull to work in 1,5m from wAP, so I think if I get better position for it, I could hit stable 700-800 mbps over WiFi.
And that's said, while having 700mbps in ultra-brilliant condition, it means I can have 500mbps easily achieveble by any client in any circumstances (well, my circumstances, at least, won't state that about some really crowdy office or stadium).
Anyway, download speed still an issue, like 2x times. Smth like this:
@Bivvy: when datapath is configured to use capsman's bridge, this usually becomes a srrious bottleneck. If you don't have a good reason not to, set datapath to local-firwarding=yes ... and the rest of appropriate settings.
Thanks @mkx@Bivvy: when datapath is configured to use capsman's bridge, this usually becomes a srrious bottleneck. If you don't have a good reason not to, set datapath to local-firwarding=yes ... and the rest of appropriate settings.
I never tested the difference myself ... but from other people's observations it hits cAPs as well. Beefy capsman HW makes things a tad easier, at least in DL direction.does this count if we have a heavy duty ros hardware?
I hardly choose 40Mhz for my cAP because it will get channel not support(?) in CAPsMAN setup.
/caps-man channel
add band=2ghz-g/n control-channel-width=20mhz extension-channel=XX <and the rest of settings like frequency list etc.>
thanks for this tip, save me big time.This puzzles me as it's different if configured through capsMan than if it's configured directly on device. But it works for me if I set up like this:
This way devices see a 40MHz channel.Code: Select all/caps-man channel add band=2ghz-g/n control-channel-width=20mhz extension-channel=XX <and the rest of settings like frequency list etc.>
You can set any valid control/extension channel pattern (Ce, eC, XX) feasible for 40MHz channel.