In this article:
    Applicable to:
    • Twingate Component: Client
    • Platform: macOS

    Overview

    If you're using Twingate on a macOS device and notice that certain IP resources aren't loading or functioning as expected, you may be dealing with a routing conflict due to overlapping subnets between your local network and the resources you're trying to access.

    What's Happening?

    When you add an IP resource to Twingate, your macOS device automatically routes traffic for that IP through Twingate's secure tunnel. However, if your local network uses the same subnet as an IP resource in another network, macOS might create conflicting routes. This can result in traffic being sent over your local network instead of through Twingate, leading to connectivity issues.

    This issue is specific to IP-only resources on macOS. While other operating systems handle route priorities effectively, macOS may incorrectly prioritize the local network, causing traffic to bypass Twingate.

    Resolution

    1. Use More Specific IP Resources
      To prevent this issue, consider defining more specific IP addresses as Twingate resources rather than entire subnets. This ensures that macOS correctly prioritizes the route through Twingate, directing traffic to the intended IP resource.

    2. Advanced Option: Remove Conflicting Routes
      For advanced users, another approach is to manually remove the conflicting local route using terminal commands. This solution should be used cautiously, as it may impact your ability to communicate with other devices on your local network.

    Conclusion

    If you’re experiencing issues accessing IP resources through Twingate on macOS, particularly with overlapping subnets, adjusting your IP resources or managing your routing table can resolve the problem. This will help ensure your traffic is correctly routed through Twingate, allowing you to access the necessary resources. This is a limitation within macOS and how they handle route priorities.