You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When matching wildcard domain addresses, we were using the address matching function from ziti-sdk-c incorrectly. The matching function returns a score where -1 is a mismatch, 0 is an exact match, and larger integers are lesser matches, but the return value was being interpreted as boolean.
This caused matches on wildcard domains to incorrectly be counted as matching when compared against plain hostname addresses.
see https://openziti.discourse.group/t/interesting-issue-with-multiple-networks/956/7
User has a wildcard service and other services defined along with a port range defined on the wildcard service. The logs very clearly show:
stafford.esxi
is assigned IP 100.64.0.4matching domain[*.cla.local] found for tnas001.cla.local
tnas001.cla.local -> 100.64.0.22
The text was updated successfully, but these errors were encountered: