According to the product page it's 80mhz (AX3600) but I'm not sure if that's correct.What is the maximum channel width for Chateau PRO at 5GHz? 4x4 160 MHz? 2x2 160 MHz, 4x4 80 MHz?
An interesting question. But the don't have block diagram too. I'd give about one week, in order for them to finish the page.Does this mean "hEX refresh" does not have IPsec acceleration, and the "twice the performance for the same price" claim is only for plain routing and not for IPsec?
The "hEX refresh" does not have IPsec test results, ...
It is 4x4 80 MHz"What is the maximum channel width for Chateau PRO at 5GHz? 4x4 160 MHz? 2x2 160 MHz, 4x4 80 MHz?"
I've wondered about that myself.I wonder why the Chateau PRO ax doesn't feature a 2.5G Port. The hap ax3 has one.
SOC Limits?
2x2 160 MHz is not supported, right?"What is the maximum channel width for Chateau PRO at 5GHz? 4x4 160 MHz? 2x2 160 MHz, 4x4 80 MHz?" - It is 4x4 80 MHz
Maybe you and most people in your environment? We are using IPsec. It may be a pain, but at least it is a standard.The "hEX refresh" does not have IPsec test results, ...
Not to downplay the importance of publishing IPsec results ... but lately they are becoming increasingly irrelevant. Most people are moving towards wireguard (and alikes), which AFAIK doesn't use IPsec HW offload.
don't have block diagram too
Block Diagram is available
THAT is their use case! Pop-and-Mom ISPs (commonly WISP) that provide internet to a building and wire up the whole thing using ethernet with PoE powering. There are several switch products for that use case as well.Stretching for a use case, I suppose you could use this to create semi-airgapped small LANs off a big PoE core switch, as in a hotel where you want a small number of wired ports at the work table, without letting each room's users see devices in other rooms.
It was added after the above remarks were made... but IPsec test results not yet, maybe they appear next week.Block Diagram is available:
You can use an always use PoE injector between ISP and ether1. i.e. if the gateway/ONT/etc is a basement/closet/outside/etc... but LAN ports needed elsewhere.Another strange PoE choice: the PoE-in port is off the switch, a sensible choice for a router-class device, but we then have to ask which ISP modems provide PoE input power?Block Diagram is available
Stretching for a use case,
Definitely not SoC limit. See https://wikidevi.wi-cat.ru/Qualcomm and 160 MHz bandwidth with 6E band should be supported too according Qualcomm. https://www.qualcomm.com/products/inter ... 0-platformI've wondered about that myself.I wonder why the Chateau PRO ax doesn't feature a 2.5G Port. The hap ax3 has one.
SOC Limits?
A real shame... I would have bought it right away.
I think the Qualcomm datasheet includes all chips that belong to that series.Definitely not SoC limit. See https://wikidevi.wi-cat.ru/Qualcomm and 160 MHz bandwidth with 6E band should be supported too according Qualcomm. https://www.qualcomm.com/products/inter ... 0-platform
I've wondered about that myself.
A real shame... I would have bought it right away.
As you can be seen on this new wAP ax chipsets require pretty large heatsink, not something one could easily do on something like wsAP...Please, pretty please :-)....
I really need some wsap hw UPDATE !!!
I would really appreciate some device hw update, ideally with the same form factor (wsap) but with AX wireless and (at least ) 1Gbps eth ports.
To bad wAP ax as a 2400 Mbit/s wifi device is also limited to 1Gbps ethernet, and IPQ5010 chip it is using acording to spec supports:I think the Qualcomm datasheet includes all chips that belong to that series.
Definitely not SoC limit. See https://wikidevi.wi-cat.ru/Qualcomm and 160 MHz bandwidth with 6E band should be supported too according Qualcomm. https://www.qualcomm.com/products/inter ... 0-platform
Your wikidevi link mentions that the QCN5054 (and IPQ8072A) only does 2.4 and 5GHz.
But then again it also mentions the IPQ8072A would support "4x GbE, 2x 10G (NBASE-T)"
Ethernet: Provides 2.5G SGMII and 1GE interfaces for wired connectivity options.
Wi-Fi 7 or 802.11be final ratification is not expected until the end of 2024, although many devices including latest iPhone 16 and Sony PlayStation 5 Pro released a couple of months ago are already supporting it as specs are not expected to change from preliminary...It is quite sad, that we are happy, that Mikrotik published AX device. Competition released many WIFI 7 devices - Ubiquity, TP-link, Zyxel.....
Maybe Mikrotik is only one, that is releasing AX device.
same thought, really. maybe .11be is not fully standardised yet, but radio hardware is available and clients are available -- seems odd that new MikroTik hero device for home router/AP user is only .11ax. who would buy it (other than dedicated MT user like us)?It is quite sad, that we are happy, that Mikrotik published AX device. Competition released many WIFI 7 devices - Ubiquity, TP-link, Zyxel.....
Maybe Mikrotik is only one, that is releasing AX device.
802.11be Standard is not finalized yet.It is quite sad, that we are happy, that Mikrotik published AX device. Competition released many WIFI 7 devices - Ubiquity, TP-link, Zyxel.....
Maybe Mikrotik is only one, that is releasing AX device.
Maybe a CCR2004-1G-2XS-PCIe in a case? (not sure if that board would work without being in a PCIe slot)Would be nice if Mikrotik develops something like RB5009 but with only 2 SFP+ ports, one for Internet and other for local net that could be attached to SFP+ switch
Boo !New hex sadly missing speaker
" old" Hex runs The Dude since a long time.Now that hEX Refresh has an ARM CPU, does that mean it can run Dude?
Oh yes, this was ages ago.Sorry guys, but 802.11be was standartized already - 26.9.2024. https://standards.ieee.org/ieee/802.11be/7516/
It is a preliminary version as can be seen from the title:Sorry guys, but 802.11be was standartized already - 26.9.2024. https://standards.ieee.org/ieee/802.11be/7516/
I agree that is the probably the most valid point - in case of 802.11ax it took roughly 1 - 1,5 years after final approval of ax standard when hAP ax^2 (as the first Mikrotik ax device) appeared. But it is necessary to take on mind the influence of Covid-19 in that time and early maturity of RouterOS 7. Basic implementation of Qualcomm "be" chipset should be much easier today.Oh yes, this was ages ago.Sorry guys, but 802.11be was standartized already - 26.9.2024. https://standards.ieee.org/ieee/802.11be/7516/
Yes, some vendors do develop and even start to market products before final standard gets adopted. They count on the possibility to make their products compliant to final standards by software upgrade (which mostly works out, but not every single time). And there are other vendors who wait for standards to be finalized and start to finalize their products only after that. I guess Mikrotik is one of vendors who do the later.
In addition, MT is a low-volume vendor (compared to some others) and I guess the priority with chipset vendors (Qualcomm, Mediatek, etc.) is a bit lower than with high-volume vendors. Which quite probably means MT gets chips at slightly higher price than the high-volume vendors. I guess this is another reason not to rush with new chipsets ... to wait for prices to drop a bit.
No, "approved draft" = final version. It is clearly stated that "be" and "bh" standards were approved on 26.9.2024. https://www.ieee802.org/11/It is a preliminary version as can be seen from the title:Sorry guys, but 802.11be was standartized already - 26.9.2024. https://standards.ieee.org/ieee/802.11be/7516/
IEEE 802.11be-2024
IEEE Approved Draft Standard for Information technology
Although no changes are expected in the final version...