Equality logic in subnet conditions of klnagent connection profiles [KSC for Windows]

Advice and Solutions (Forum Knowledgebase) Disclaimer. Read before using materials.

Consider the following scenario:

You have a large local area network 10.36.0.0/16. There is a managed device with the following IP config: IPv4 address: 10.36.35.10 and Subnet Mask: 255.255.255.0. You create a new subnet condition for klnagent connection profile: 10.36.0.0/16.

Actual result:

The connection profile is not applied to the managed device.

The reason of this behavior is equality logic used by klnagent. It verifies if the condition matches by comparing the current value of the IP address and subnet mask of a managed device:

IP address 10.36.35.10 is within the 10.36.0.0/16 network.

However, subnet mask 255.255.255.0 is not equal to 255.255.0.0 specified in the condition.

Solution:

In order for the rule to work correctly, each 10.36.0.0/24 subnet (including 10.36.35.0/24) of the larger 10.36.0.0/16 network should be added as a condition: