SSID not working if profile name is not the same

mMontana

Preamble: i found this behaviour on two different products.

First device is a NWA50AX PRO with V7.00(2) firmware and 14:XX:XX:XX:XX:XX mac address.
Second device is a NWA1100-NH with V2.12 firmware (still a wonderful AP… that have SNMP inside)

I'm assuming that I have the "Mobile" SSID (actual newtork name) with the "Release4" security profile (WPA2-AES PSK) with the current name of the SSID profile "Mobile".

I'm planning to change both security profile and the network name during a wireless configuration migration.
The new SSID will be named "Devices", will have the profile name "Mobile".
The current SSID "Mobile" is being renamed "Obsolete", while not changing any detail (SSID/network name, security configuration, security profile associated).

Trying the migration status "offsite", with a sample device (NWA50AX PRO, firmware indicated above.

A device which is using "Mobile" SSID stops working within minutes I rename the profile of the network (no security settings at all, no security profiles).
A device which try to connect to "Devices" will have access.

I rename the profile for SSID "Devices". After the rename, the device which is working on the network stops working.

If my explaination is not understandable, I hope that this will make sense to the audience.

Config 1
Profile 1 name: "Mobile"
actual SSID 1: "Mobile"
security: "Security profile 1" (WPA2PSK)

Device A (connects to "Mobile") works as intended

Config 2
Profile 1 name: "Obsolete"
actual SSID 1: "Mobile"
security: "Security profile 1" (WPA2PSK)

Profile 2 name: "Mobile"
actual SSID 2: "Devices"
security: "Security profile 2" (WPA2PSK)

Device A (connects to "Mobile") stops working
Device B (connects to "Devices") not working

Config 3

Profile 1 name: "Mobile"
actual SSID 1: "Mobile"
security: "Security profile 1" (WPA2PSK)

Profile 2 name: "New"
actual SSID 2: "Devices"
security: "Security profile 2" (WPA2PSK)

Device A (connects to "Mobile") works as intended
Device B (connects to "Devices") not working

Device A and B are note actual devices: I tried both with Windows 10 laptop, Android 12 mobile phone, Windows Mobile Intermec/Honeywell and Newland devices: the behavior was the same.

I think that this might be a small conceptual bug.
In my opinion is not useful have a "profile name" that can be edited if this break the SSID working condition.

I'd love to have the profile name, this will help explaining and migrate in such more easy way. Can tell to the admin what that wireless network does, without allowing rogue visitors to understand what the network could be or… which company is emitting that.

Anyway.

I'm not expecting updates for the whole shebang of the older zyxel devices, however… would be really nice that zyxel repair the broken feature since NWA-1100N

Zyxel_Melen

Hi @mMontana,

Could you share your migrate steps? I'm not sure this issue happened when you apply the sample device into this network. I want to clarify the issue happened on which step and narrow down it.