In this article:
In Twingate, a Resource is attached to a single Remote Network but it is possible to declare identical Resources all assigned to different Remote Networks.
This is useful in environments where the same IP addresses of CIDR ranges are used across subnets and Remote Networks however it can sometimes create ambiguity in Resource resolution where Twingate cannot easily determine the proper network path to a given IP, hostname or FQDN.
If one of the following conditions is true in your environment:
- Identical Resources are mapped to different Remote Networks; at least one Group grants access to identical Resources
- Users belong to Groups which contain identical Resources.
Then Resource ambiguity might cause connectivity issues. In this case, please read follow the instructions from our Best Practices guide on overlapping IP addresses