Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Parents Reply Children
  • Coming back to this one: &  

    This seems to be an already under investigation issue with the wlnet (separate Zone) based traffic. 

    Bug ID: NC-94019

    Currently under investigation. 


  • One workaround in a broader Scale would be using Central Wireless + VLAN Tagging, if applicable. 

    Just wanted to share this workaround / alternative deployment method. (That is the reason, i did not pick up this issue, as i do not use any separate zone anymore and moved everything to VLAN). 

    Central Wireless is free to use.


  • We are also facing issue of with wireless separate guest  network . I have deleted  guest  zone and recreated it ,then added to acces point group again then only it works......

  • I can confirm LuCarToni's workaround. I had the same problem after upgrading from 18.5.2 to 19.0.1.
    I put the access points (without Central Wireless) into several VLANs and so far I have no more problems. It is of course a little effort to provide the active components (switches) with the VLANs, but are with us and our customers all managed switches Relaxed
    And I have also gained more flexibility, because I can now determine exactly in which directions the data traffic between the WLANs and the LANs should run.

    Best regards


  • This is pretty much what I did when I switched to Central Wireless. I substituted VLANs for the VXLANs that XG-based wireless used. I don't use the WiFi zone anymore, but instead it's three zones corresponding to three AP-based VLANs: LAN, Guest, and Work_IoT. (Actually, LAN is a bridge between an AP-based VLAN and a wired port for a server.)

    Works great.