NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Guest network can't access internet when client isolation is enabled
Hi, I got an AX1800 wireless AP. I'm trying to set up a guest network and personal network. I configured each of them to have a separate SSID and separate VLAN. My problem is that when I "enable ...
We have made some improvements to address your issue mentioned here. Current ETA to release the firmware is in mid of March.
Kindly wait till that time and provide your feeback.
Thanks,
Raghu
Could you please send your network diagram with VLAN info and diagnostic logs? Please PM me.
Thanks,
Raghu
I was able to fix the problem.
It seems that you MUST have the DHCP client setting enabled in order for the "wireless client isolation" feature to work. Is this how it is intended or is this a bug?
I hope that it is a bug, becaues I don't want the AP management interface IP to be assigned by a DHCP server. The other weird thing is that when my computer was connected to the guest network, it was still properly being assigned a gateway, DNS, and IP address, even with the DHCP client disabled on the AP.
Thanks for any information you can provide.
AX1800 is some fancy marketing speed class definition - not a model. Are you talking of a WAX214 or a WAX610 or another WiFi 6 device with an access point feature ... and what firmware version are we facing here?
aefsdfsafwefaf wrote:It seems that you MUST have the DHCP client setting enabled in order for the "wireless client isolation" feature to work. Is this how it is intended or is this a bug? .. I hope that it is a bug, becaues I don't want the AP management interface IP to be assigned by a DHCP server.
This is at least very strange. It should not matter on how the device management interface is configured (IP, subnet mask, GW, DNS) for the wireless client isolation.
It's never a bad policy to have MAC IP pair reserved on the DHCP server, even if using static configs.
aefsdfsafwefaf wrote:The other weird thing is that when my computer was connected to the guest network, it was still properly being assigned a gateway, DNS, and IP address, even with the DHCP client disabled on the AP.
Assuming we talk of the WAX2xx/WAX6xx here: None of these devices does offer a DHCP service. The DHCP client is just to get the management interface config in place. Any DHCP service does come from the network, where what would be used as a guest network must be on a dedicated VLAN, with the appropriate router handling the routing, NAT, DHCP, ... There is no "magic" guest network thing, these are not consumer mesh type guest network devices.
Hi,
Sorry for the delay. The router is in fact the WAX610. It's running firmware version 9.2.07.
I agree that it is strange that the client interface was affecting the isolation feature on the guest network was werid, and that is why I was suggesting it is a bug.
I also understand that the DHCP server is provided by my firewall/gateway device. The reason I mentioned that my guest clients were still getting an IP address was because that presumably meant that some communication with the firewall/gateway was still taking place.
I also understand that there is no magic for the guest network. It is just and SSID with network client isolation enabled and put on the VLAN I configured for guests. With regards to this not being a consumer device—that is why I purchased it. However, I am wondering if it really is a business class device, because the solution I found (disabling the static clinet IP address for the AP configuration interface) was also described as a bug for a consumer level device. So I am suspect if the "business class" devices are just running consumer software under the hood.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
