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.

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

Ability to define more than one L3 route in a network and have backup / fail-over #1015

Open
cameronbraid opened this issue Aug 21, 2019 · 1 comment
Labels
Networking & Routing Routing, networking to multiple systems, and multicast Status: Backlog Older issues that are awaiting resolution Type: Feature Request or Suggestion Enhancements, performance concerns, etc.

Comments

@cameronbraid
Copy link

cameronbraid commented Aug 21, 2019

I would like to have backup routes so that if one member is down I can still route via another member

For example say I have three members A, B and C
A zerotier IP is 10.123.1.1
B zerotier IP is 10.123.1.2
C zerotier IP is 10.123.1.3

A and B have access to the same private network subnet 10.118.56.0/26

Currently I can setup a route "10.118.56.0/26 via 10.123.1.1" and this allows C to access the private subnet

Though in the case where A is down I would like to be able to route via B

So ideally I can add a route "10.118.56.0/26 via 10.123.1.2"

But I have to manually manage these routes since A or B can come or go at any time.

Ideally I could configure both routes and have zerotier only create ONE route table entry on C, using A as perference and B if A is offline

@adamierymenko
Copy link
Contributor

We don't currently support anything like this... sorry. Adding as backlog feature.

@adamierymenko adamierymenko changed the title Backup Routes Ability to define more than one L3 route in a network and have backup / fail-over Aug 23, 2019
@adamierymenko adamierymenko added the Status: Backlog Older issues that are awaiting resolution label Aug 23, 2019
@unquietwiki unquietwiki added Networking & Routing Routing, networking to multiple systems, and multicast Type: Feature Request or Suggestion Enhancements, performance concerns, etc. labels Aug 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Networking & Routing Routing, networking to multiple systems, and multicast Status: Backlog Older issues that are awaiting resolution Type: Feature Request or Suggestion Enhancements, performance concerns, etc.
Projects
None yet
Development

No branches or pull requests

3 participants