[Release Note] Nebula Access Point Series - Phase 2 firmware has been released!

Nebula Moderator

Zyxel Nebula Access Point Series

Release Note

July, 2017

---

Firmware Version on all models
Zyxel NAP102 - V1.02(ABDF.3)
Zyxel NAP203 - V1.02(ABFA.3)
Zyxel NAP303 - V1.02(ABEX.3)
Zyxel NAP353 - V1.02(ABEY.3)

* V1.02 patch 3 firmware was released on July 23.

New Feature and Enhancements

1. Add DCS Scheduling feature.
   
2. Add SSID Scheduling feature.
   
3. Add LAN Port Provisioning feature.
   • For NAP203/303
4. Add display of port status on NCC
   • For NAP203/303
5. Add locator LED feature.
   • For NAP102/203/303
6. Add additional LED pattern when wireless module failure.
   
7. Added option to allow/block HTTPS traffic for captive portal.
   
8. Captive portal now supports Social login with Facebook.
   
9. Captive portal will now display NCAS notifications.
   
10. NCC now will show current transmit power of NAP.
    

Bug Fix of Major Release

1. Fixed error of NAP sending 00:00:00 faulty MAC address.
   
2. Fixed unsynchronized configuration when device reset upon receiving configuration from NCC.
   

Patch 3 fixes

• Resolve the issue of configuration returning to default after upgrading on NAP203/303/353.
  
• Resolve the issue of Captive portal being not able to lease authorization to new client entries when total site clients accumulated to 64 clients before any entry is released by re-authentication timer.
  
• Fixed the issue when click agree button of click-to-continue portal will cause high CPU on NAP.
  
• Fixed the issue when roaming between 2.4G and 5G band needs to re-auth with captive portal.
  
• Fixed the issue when stations associate with NAP under configuration change will cause authentication to fail afterwards.
  

Notes

1. To all users when upgrading Nebula devices, please make sure your device is connected to the control center and internet.
   
2. During the upgrade process (notice the LED will flash in red rapidly), make sure the power is not inturruped or disabled, in the unlikely event of this happening, you may have to perform the upgrade again.