I'm seeing a weird (and duplicatable) issue. Seeing the issue on multiple AP models and firmware versions, and on two different Central instances (US-2 and US-4)
Example:
We have tried this configuration with both AP-345 and AP-535
-
ENET0 - Trunk configured with VLANs 10,20,30.
-
ENET1 - Trunk configured with VLANs 40,50,60
wired-port-profile ENET1
no shutdown
switchport-mode trunk
allowed-vlan 40,50,60
native-vlan 999
access-rule-name ENET1
speed auto
duplex auto
poe
type employee
captive-portal disable
inactivity-timeout 1000
If I configure a WPA3-PSK SSID and set the VLAN as any of the above 6, it works perfectly fine. Client associates, gets IP, and is able to surf.
If I configure an Open Network with Cloud Guest, and set it to any VLAN on ENET0, client devices associate, gets IP, and is promptly redirected to the Cloud Guest portal. I am able to perform the click-thru, and client is able to surf.
If I configure an Open Network with Cloud Guest, and set it to to any VLAN on ENET1, client devices associate, get IP, and the redirect RARELY (1 out of 20 attempts) happens, and if it does the Cloud Guest page loads EXTREMELY SLUGGISHLY (we're talking 2-3 minutes to load). On the extremely RARE time that I am able to perform the click-through, the client is then able to surf normally at full speed.
Summary: When SSID w/ Cloud Guest is configured to use a VLAN on ENET1, it is essentially non-functional. If I change that SSID to use a VLAN on ENET0, it works perfectly.
I have tried this with both an AP-345 and AP-535. I have tried multiple versions of AP firmware (8.6.0.14, 8.6.0.15, 8.6.0.16, 8.9.0.2).
Has anyone seen this behavior before?
------------------------------
Robert Glover
------------------------------