Zywall USG60W WLAN down after upgrade to 4.31(AAKZ.0) firmware

zykkeli

Hello,

We lost WLAN after upgrading from 4.25 (AAKZ.1) to 4.31(AAKZ.0). The WLAN led won't come green and in Monitor->Wireless->AP list the local-AP appeared to be offline, but an another AP (USG60W) had appeared to the list, waiting to be added to Mgnt list. The weird thing is that this AP seemed to have different MAC address than what our local-AP has. After we rebooted with the standby 4.25 firmware, the WLAN came up again and the extra AP disappeared from the list.

Zyxel_Cooldia

Hi @zykkeli,
It seems some settings caused USG60W local AP is unable to come on line.
Can you help me to post the result of CLI below for further checking.
(Please mask your IP information before your post)
Router> show interface wan1
Router> show interface wan2

zykkeli

Hello,

Thanks for your answer! I have posted results below. So we are currently running with 4.25 and only wan1 is connected. We are using custom MAC address and now I noticed that the other AP which appeared to AP list after installation of 4.31 seemed to have our default MAC address..I did not record it down at that point but I am quite sure it was the same. So custom MAC could be the reason for our problems?

Router> show interface wan1<br>active: yes<br>interface name: wan1<br>physical port: P1<br>description:<br>type: external<br>IP type: dhcp<br>IP address: XXX.XXX.XXX.61<br>netmask: 255.255.252.0<br>gateway: XXX.XXX.XXX.1<br>current MAC address: XX:XX:XX:XX:C1:22<br>use custom MAC address: yes<br>custom MAC address: XX:XX:XX:XX:C1:22<br>default MAC address: XX:XX:XX:XX:4A:FF<br>virtual MAC address: 00:00:00:00:00:00<br>metric: 0<br>unicast: off<br>igmp active: no<br>igmp direction: upstream<br>igmp version: IGMPv2<br>upstream: 1048576<br>downstream: 1048576<br>mtu: 1500<br>mss: 0<br>dhcp option 60:<br>tcp-ack traffic prioritize:<br>&nbsp;&nbsp;&nbsp; active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : yes<br>&nbsp;&nbsp;&nbsp; bandwidth&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 1048576<br>&nbsp;&nbsp;&nbsp; priority&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 1<br>&nbsp;&nbsp;&nbsp; maximize-bandwidth-usage&nbsp;&nbsp;&nbsp;&nbsp; : yes<br><br>&nbsp;&nbsp;&nbsp; <br>Router> show interface wan2<br>active: no<br>interface name: wan2<br>physical port: P2<br>description:<br>type: external<br>IP type: dhcp<br>IP address: 0.0.0.0<br>netmask: 0.0.0.0<br>gateway:<br>current MAC address: XX:XX:XX:XX:4B:00<br>use custom MAC address: no<br>custom MAC address: 00:00:00:00:00:00<br>default MAC address: XX:XX:XX:XX:4B:00<br>virtual MAC address: 00:00:00:00:00:00<br>metric: 0<br>unicast: off<br>igmp active: no<br>igmp direction: upstream<br>igmp version: IGMPv2<br>upstream: 1048576<br>downstream: 1048576<br>mtu: 1500<br>mss: 0<br>dhcp option 60:<br>tcp-ack traffic prioritize:<br>&nbsp;&nbsp;&nbsp; active&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : yes<br>&nbsp;&nbsp;&nbsp; bandwidth&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 1048576<br>&nbsp;&nbsp;&nbsp; priority&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 1<br>&nbsp;&nbsp;&nbsp; maximize-bandwidth-usage&nbsp;&nbsp;&nbsp;&nbsp; : yes<br>

Zyxel_Cooldia

Hi @zykkeli,
The custom MAC is the reason for this problem, it will be included at next formal firmware release.
Please change the custom MAC address to device default MAC address for workaround.

zykkeli

Hello @Zyxel_Cooldia ,

Thanks for information! We will keep running 4.25 until a new firmware will be released, cannot revert back to device default MAC :-)