Skip to main content
FortiKoala
Staff
Staff
Sep 28, 2018 6:58 AM UTC

Technical Tip: Need to use an IP Range as a criteria for a 2nd portal

  • Apr 16, 2026 1:22 PM UTC
  • 0 replies
  • 800 views
  • Translate All

Description

 
This article describes how and why it is necessary to use an IP Range as criteria for a 2nd portal.


Scope

 

FortiNAC 7.1.x.


Solution

 
Example: Upon setting up a second registration VLAN to send a different portal to clients who connect to that VLAN, using a host profile where the 'where' is a port group, and that default port VLAN is the new VLAN works as intended. But for a (hardwired) wireless client, putting the actual IP of the client (attached) works, but a range does not work (10.9.84.0/24). Since this will be the APs with many SSIDs/VLANs, a port group is not usable. As a result, it is desirable to send a client who ends up on that VLAN to the second portal.
 
Solution: The for fields only wildcard does not allow subnetting, so the solution for the above example is to use 10.9.84.*.
Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024