netgear is strange, also this is a business model so it can be they made a variant just for the cover color....
I have just purchased 2 of the "B" models and both are white. Whatever the model variation is, its not in color. However, the standard 22.03 images install fine, so the hardware appears to be similar enough.
Oem has access to proprietary wireless drivers that can perform better.
I tested with standard OEM firmware in AP mode to AC clients before installing OpenWRT. No meaningful performance difference over OpenWRT. There is a thread about problems with AX clients, but I have not tested with AX.
Let's go back to the top of this topic ... that's why I said that I'm considering buying the WAX202
I can't claim a lot of usage yet, but the WAX202 at $30 appears to be a great deal. I'm swapping it in for (prior forum favorite) Archer C7s as "dumb" APs for N and AC clients (routing is on OpenWRT x86). Despite the apparent downgrade to 2x2 compared to the Archers, real world performance is better with the WAX202, even when using 3x3 clients (Intel Macbook). I'm getting 550-600+ when close to the base station. AIUI that's in the range of what's considered real-world best-case AC performance.
The AX limitations (no 160, etc.) may make this insufficient one I have more AX clients in a couple of years, but to get two APs upgraded at that price made it compelling.
I'll make another thread - none of that information was useful.
E.g. the some sections are struck-through and some sections say " This item needs careful vetting…" Another section appears to create tags; but doesn't show a corresponding network config for the respective VLAN.
I have no clue what that means. Then, I'm confused why multiple networks/VLANs say "br-lan". Lastly, there's no information regarding this script in the Wiki. I'll research more.
(Use case: one port connects to a VM Hypervisor on via tagging. One port will be e.g. untagged VLAN 1, another untagged VLAN 2 and the third port will tag both VLANs 1 and 2.)
That aspect is indeed a bit confusing (and imho 'wrong'), that's why my example (#4036) calls the bridge used for bridge-vlan-filtering "switch" instead. That example shows you also tagged and untagged VLANs on different ports (and in comparison to a very similar swconfig on the same device).
I'll report on the power savings soon (theoretically, it's >= 100% for me). I replaced a full-sized x86-64 and WD N750 as dumb AP/managed switch (but lost 1 port and may need to use it from time to time). The WAX202 now runs on solar/battery for indefinite power. The x86-64 ran ~45 W/hr. - so it would not be viable for solar and was on mains power.
0.6 A x 13.5 V = 8.1 W
Lights off: ~6.75 W
EDIT: I noticed I don't see channel 161 on 5.4 GHz WiFi. Odd, I see it.
Yes, I get that. laughs I haven't done wireless on WRT since the 54g days, because in general dedicated devices do it better (largely thanks to closed-source drivers).
I know Asus tried the grow-your-own-mesh thing with their proprietary firmware with mixed results, so I was more just casting a wide net to see if there was a reasonably straightforward software mesh capability available in OpenWRT these days.