Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix: Derive the exclude_rt from the preferred route #649

Merged
merged 1 commit into from
May 24, 2023
Merged

Fix: Derive the exclude_rt from the preferred route #649

merged 1 commit into from
May 24, 2023

Commits on May 6, 2023

  1. Associate the exclude_rt with the correct interface. 

    Every exclude_rt was derived from the system's default route (which is
retrieved using ip route show default). This causes the
communication to use the default gateway even if the system had a more
preferred route for the destination. In the worst case, the destination
is unreachable from the default route, causing loss of communications.

This fix addresses this behavior by looking up the system's preferred
route for the destination and then deriving the exclude_rt from that
route.

A secondary benefit of this approach is that the ziti-edge-tunnel can use
indirect underlays such as Speedify or Tailscale to communicate with the
controllers and edge routers. One of the benefits of indirect underlays
is increasing the likelihood communications pass firewalls and hard
NATs.

Signed-off-by: Tom Carroll <[email protected]>
    @tomc797
    tomc797 committed May 6, 2023
    Configuration menu
    Copy the full SHA
    ad1128a View commit details
    Browse the repository at this point in the history