I have been using the above RB for a couple of weeks now and am generally and genuinely happy with its performance. It’s my main router and CAPsMAN for three other hAP ac. I am currently trying to set it up as a wireless AP with 160 MHz bandwidth, and that is where I struggle. Now, I have to admit that I do not technically need those 160 (or 80 + 80) MHz, but at least I wanted to see if it actually works.
That being said, I can’t seem to set it up with the targeted eight 20 MHz subchannels, regardless of whether I go through CAPsMAN or try directly on the wireless interface. I would like to use channel 50 which encompasses channels 36 through 64. I have tried to do this both manually
, but I always end up with a 80 MHz network - at least as per my wifi scanners both on my mobile and my laptop. Am I missing anything? Frequency spectrum is both legally allowed and usable. Any pointers are highly appreciated.
Cheers,
Smoerrebroed
PS: I am not sure if my client hardware actually supports 160 MHz, but I understand that I should at least be able to “see” the network in its entirety, correct?
5500 is out of the question, unfortunately, as there seems to be radar on the upper half of that range, so it won’t start up claiming that radar has been detected. For the country, I have tried both etsi as well as Germany (which is where I currently live), again both with indoor and any installation but to no avail. CAPsMAN (as well as the local interface config) will actually show, say 5180/20-Ceeeeeee/ac/DP(20dBm) but according to multiple wifi analyzers, there is no signal upwards of 5250 MHz.
I don’t intend to use XXXXXXXX, just wanted to clarify that even with everything set to auto, the router won’t go to 160 MHz combined channel width. This is on ROS 6.47.3, btw.
You probably don’t have a 160 Mhz client (Only Intel has one Wifi 11ax client card that can do that today
Result is you will not be able to see a 160Mhz channel in a spectrum analyser
best phones and clients today only have 80 Mhz (most even have only 40Mhz).
In addition initial boot with 160 Channel means +/- 10 minutes DFS scanning when booting your device , during this time no 5G Wifi
After a DFS detection, then again radio is off for scanning the same time.
(DFS depends on the country you are in, but ETSI/Europe is like this and many other countries as well)
Thanks for your input. I wasn’t asking about whether or not it makes sense to use 160 MHz channel width at the moment. (It probably doesn’t, and I am aware of that.) However, I assume that I would actually be able to “see” a 160 MHz channel in a real spectrum analyzer, but I do not have one. Instead, I use a wifi analyzer app which does show active networks. Even with my age-old mobile phone with only 1x1 MIMO, I can see those 80 MHz networks - I just can’t connect to them, so I’d think that it will be the same for 160 MHz networks, except I can’t get the RB4011’s network to show up as 160 MHz, and this is what I am asking about.
So, to repeat: Has anybody managed to produce a 160 MHz network using the RB4011?
the bandwidth you see in the net analyser tools (or similar SW) does not come from real RF scanning (like real spectrum analyzer),
but from decoding the beacon frame! So what you see is not necessarily what you have.
In the beacon frames your phone gets told that the AP can do 20/40/80 Mhz etc. which is then displayed in the app…
I have just 160Mhz set up to play around between RB4011 and Audience (both have QCA9984 4x4).
I saw 160Mhz channel usage in the connection info tab on both ends while my phones “net analyzer” still shows me 80Mhz only.
So device can do it and uses it…