WAX620 with firmware V10.6.1.1 I'm trying to set up a guest wifi using NAT configuration.
Connecting to the SSID with NAT enabled, strange network behaviour is observed.
Initial connection opening any web page or youtube app, whatever takes very long time 10 to 20 sec.
After the first connection, network flows smoothly but stuttering sometimes.
Measured throughput is as good as other bridged normal setting SSIDs.
There seems to be a mistake in firmware handling some kinds of packet like DNS or ACK? I'm not sure.
In addition, one possible misleading configuration is "DHCP Offer Broadcast to Unicast".
When this setting is "Enabled", devices that connect to the NAT SSID receive DNS nameserver configuration from the upper network. IPv6 nameserver in my case. That causes connected devices totally unusable.
So usually for a guest WiFi network, NAT and DHCP Offer disabled would be the possibly configuration. I believe.
This behavior is already acknowledged? Working to resolve in the future firmware?
Re: WAX620 NAT mode is terribly unstable and unusable
Reads like something is very wrong with the NAT config or the WAX6xx config in general.
Have defined an IP subnet not in use on any other local LAN or VLAN? Overlapping IP subnets probably?
An IPv6 DNS server must be able to resolve IPv6 and IPv4, including the fallback from IPv6 to IPv4. Check using https://ipv6-test.com/ for example FMI - from both a direct SSID as well as for the NATed SSID connection.
When using the NATed SSID, only IPv4 can be available, as the many-2-one NAT in place does support IPv4 only, using the WAX6xx LAN IP as the target for the NAT address.
The DHCP Offer Broadcast to Unicast is available to reduce the burden of massive broadcast traffic on the wireless. Unclear why and how this should make a difference in the way the DNS is used from the NATed SSID - essentially the same DNS config is in use either way.
As for IPv6. When NAT and DHCP both are enabled, connected client PC gets IPv6 nameserver address of
the upper network but doesn't get IPv6 address assigned to the PC. Ipv6 address advertisement seems not working to NAT network. I think that's why.
So far, for me, just NAT setting does not work well.
Would you mind to show how a common system on this NATed SSID does announce an IPv6 DNS address? Here what I get (while connected to a full dual-stack IPv6/IPv4 network, but only connecting to the NATed SSID) e.g. Windows shows, including which DNS server is accessed:
Re: WAX620 NAT mode is terribly unstable and unusable
Please keep us updated if a solution is found to this. We are having the same issue. 2 WAX620's. One on first floor, one on second floor. I have set up a guest wireless on a VLAN through a Sonicwall TZ370. It does work but seems to be dropping clients consistently. When I log in to Insight, the connection by SSID graph literally looks like a saw tooth with all SSIDs going from say.......5 clients connected to 0, then back to 5 again. We also have clients on the first floor randomly deciding to connect to the second floor WAP, which is odd.
I have tried all sorts of settings changes. Running firmware 10.6.1.1. Tried dropping power level to half on both WAPs, changing channels and bandwidth to create separation. Nothing seems to be helping.
Please keep us updated if a solution is found to this. We are having the same issue. 2 WAX620's. One on first floor, one on second floor. I have set up a guest wireless on a VLAN through a Sonicwall TZ370.
Obviously not the same.
@JakeJ does talk of the NATed SSID option, allowing to have a small isolated Guest IP subnet by each AP.
In your deployment, it appears you have an issue on one VLAN spanning all WAX6xx, with the L3 done on the Sonicwall. At the same time, there are no problems with the normal LAN or VLAN handling the non-guest network(S)?
