Horizon - Proxy - Blast secure gateway

You should not be Using matchclass (this keyword is deprecated/obsolete) instead use class match:

• • The matchclass command is not valid in this context, it was used before v10.
  • The correct command to use is class match, which is specifically designed for matching entries in data groups or shared objects.
  • 
    
     The correct command to use is class match, which is specifically designed for matching entries in data groups or shared objects.
  •  
  • when CLIENT_ACCEPTED {
      if { [class match [IP::remote_addr] equals international-sites_netgrp] } {
        pool infoblox-report
        # log local0
      }
    }
    
    
  • if { [class match [IP::remote_addr] equals international-sites_netgrp] }:
    • class match: This command checks if the client's IP address ([IP::remote_addr]) matches any entry in the specified data group or shared object.
    • [IP::remote_addr]: This command retrieves the IP address of the client.
    • equals international-sites_netgrp: This specifies the name of the shared object (address list) that contains the IP addresses or subnets to match against. In this case, international-sites_netgrp is a shared address list that includes other address lists or IP ranges.
  • 
    Incorrect Syntax:
    • Using incorrect syntax or commands that are not supported by iRules will result in errors and the iRule will not function as intended.
      
      For example, using class match [IP::remote_addr] without proper spacing or brackets will cause syntax errors.
      
      Not Using Shared Objects:
      • If you do not use shared objects or data groups, you would need to hard-code the IP addresses or subnets directly in the iRule, making it less flexible and harder to maintain. Shared objects allow you to manage and update the lists separately from the iRule, simplifying maintenance and updates.

class

matchclass