Hello @Hank21 ,
thanks for your reply
we have 5 ssids which send the clients to 4 vlans, (vlan ids simplified below)
management network of controller and accesspoints is on vlan 1
ssid1 WPA2-PSK/WPA3-SAE / AES - vlan 2 - all working perfect, client are sent to correct vlan and get ip via dhcp from firewall
ssid2 "guest network" with no security - vlan 3 - all working perfect, client are sent to correct vlan and get ip via dhcp from firewall
ssid3 "guest network" with hidden ssid with no security - vlan 4 - all working perfect, client are sent to correct vlan and get ip via dhcp from firewall
ssid4 hidden test network WPA2-PSK/WPA3-SAE / AES - vlan 2 - all working perfect, client are sent to correct vlan and get ip via dhcp from firewall
ssid5 WPA3-Enterprise / AES - vlan 5 - radius (windows nps) log shows same result as connecting to a eap660hd, eap225, but with eap670 and eap650outdoor - the client gets no ip from our windows dhcp server, the client connected to the "old" ap's work fine as always - after roaming from an old to a eap670 the clients remain the dhcp ip and work as well - so the associated vlan should be also correct
controller firmware is 5.9.31 (virtual on ubuntu - vmware)
ap firmwares
EAP660 HD(EU) v1.0 1.1.1
EAP610-Outdoor(EU) v1.0 1.1.3
EAP225-Outdoor(EU) v1.0 5.1.0
EAP650-Outdoor(EU) v1.0 1.0.2
EAP670(EU) v1.0 1.0.6