WAX220 Guest Network - Unsecured

Do not buy this Access Point and expect a secure Guest Network. The original firmware had an option for L2 Isolation, but updating removes this option and reverting does not restore it. The Guest N...

Before You Buy

Firmware

Security

Troubleshooting

Retired_Member
Jun 09, 2023
schumaku wrote:
Retired_Member wrote:
Who knows what else is not working as intended...
Whatever impression you want to bring up with such shabby comments and poorly formulated subject lines. just poor sportsmanship or bad intentions?

Unexperienced users (some >99% of the readers in such a user community) tend to understand "WAX220 Guest Network - Unsecured" very different. Wouldn't "WAX220 Can't enable Client Isolation to Block LAN Subnet Access" describe the effective information much better? Just my 2 Cents.

Reminder: We talk about essential wireless AP products WAX214v2 (street price less than 88 USD ex VAT!) for a WiFi 6 AX1800 Dual-band PoE Wireless Access Point, and WAX220 (street price less than 129 USD ex VAT) for an AX4200 Dual Band AP with a 2.5 GbE network connection.

You really love those partial sentences, don't you? I didn't know this was a competition, Mr. Good-sport.
Unexperienced users absolutely need to be made aware of a product that has flaws. Quit defending a company you say you claim to not be affiliated with. You're playing a semantics game because you have a must-be-correct complex at this point.

You still haven't tested the WAX220 as thoroughly as I have, and you just glazed over some basic stuff, like an NPC help desk rep.

Here's a real reminder: I just picked up a different brand, and return all the Netgear products I bought. The competitor was even priced almost identically for each product (switch and access point), and they offer A LOT more control, along with functionality that isn't broken.

The solution? Buy something else, don't waste your cash till Netgear decides that firmware is important, again.

Done with this thread, the replies coming in are from sources out of their depth.

schumaku

Guru - Experienced User

May 23, 2023

Retired_Member wrote:

To clarify the Time Zone bug, it only happens if you check the Day Light Savings time box, and change the Time Zone from the DEFAULT one. Unchecking DST, then changing the Time Zone, then rechecking DST, will save it.

Thank you, nice find. Should be easy to fix for Netgear.

Retired_Member

May 24, 2023

schumaku wrote:
Retired_Member wrote:
To clarify the Time Zone bug, it only happens if you check the Day Light Savings time box, and change the Time Zone from the DEFAULT one. Unchecking DST, then changing the Time Zone, then rechecking DST, will save it.
Thank you, nice find. Should be easy to fix for Netgear.

After being logged out of the WAX220 for a little while, or possibly changing some settings on another page, the Time Zone will still unfortunately revert back to it's default setting. The bug grows.

schumaku
Guru - Experienced User
May 25, 2023
Retired_Member wrote:
After being logged out of the WAX220 for a little while, or possibly changing some settings on another page, the Time Zone will still unfortunately revert back to it's default setting. The bug grows.

Interesting. All related to the default time zone, and which one does apply to your installation?

Operating a bunch of WAX214, WAX218 as well as the newer WAX220 v1.0.3.0 and WAX214v2 v1.0.2.2 (two factory new units added these days to complement the Beta sample) on the UTC+01.00 time zone with the ubiquitous DST enabled. All trouble free since installing resp. updating a few days ago.
- Retired_Member
  May 31, 2023
  schumaku wrote:
  Retired_Member wrote:
  After being logged out of the WAX220 for a little while, or possibly changing some settings on another page, the Time Zone will still unfortunately revert back to it's default setting. The bug grows.
  Interesting. All related to the default time zone, and which one does apply to your installation?
  
  Operating a bunch of WAX214, WAX218 as well as the newer WAX220 v1.0.3.0 and WAX214v2 v1.0.2.2 (two factory new units added these days to complement the Beta sample) on the UTC+01.00 time zone with the ubiquitous DST enabled. All trouble free since installing resp. updating a few days ago.
  
  That's not correct.
  
  I just tested ANOTHER WAX220, more thoroughly, both with stock and then with current firmware.
  Firmware v1.0.1.2 (stock) = L2 Isolation option is PRESENT, but it does not actually work. I am still able to access my router's login page even when connecting to the guest network and enabling the isolation.
  Firmware v1.0.3.0 (current) = L2 Isolation option is MISSING. Clients on guest networks are still able to access the router's login page.
  The time zone will still default to PST after some random time and/or actions settings have been configured on the AP.
  
  Don't believe something simple like typing in 192.168.1.1 and watching your web browser ask you to for your login information? Then go for the overkill and Wireshark it like I did. I see why they removed the poor attempt at L2 Isolation. It's been broken from release. Who knows what else is not working as intended...
  - schumaku
    Guru - Experienced User
    Jun 01, 2023
    Retired_Member wrote:
    Don't believe something simple like typing in 192.168.1.1 and watching your web browser ask you to for your login information? Then go for the overkill and Wireshark it like I did. I see why they removed the poor attempt at L2 Isolation. It's been broken from release. Who knows what else is not working as intended...
    
    You talk to the wrong person on the wrong channel, please avoid insulting innocent community members please. To repeat .I'm just yet another Netgear customer who is happy to help. It's luckily not my job here figuring out what random time settings you played on to break the PST time. I'm located in Switzerland, all the local time zone GMT+0100 and DST works for me as expected.
    
    Putting the PST time zone and DST aside: If you can't see the Client Isolation controls (for whatever reason, I had the feeling these were hidden due some browser caching oddity here, too), it might be difficult to state, these don't work. I can't care less about the factor firmware which had to be released for production at a certain point for starting the serial production. Whatever broke back then. i have no access to the formal or internal released code. For me, at the end of the beta process, the control was visible and workable.
    
    Sorry for making you unhappy. I'm done on what I can do here. Talk to Netgear support with your findings please. For a reason Netgear does provide free support for the initial time after the initial installation.