Add unsafe_route metric / hop count

[Mrc527]

Hello guys,

In my scenario, I've multiple nodes which could serve the same unsafe route.
Let's say, I want to access a TV on my local network and I've nebula nodes on my NAS and Router. Both on the same local network.

So, while being on the road, I could connect to the TV through the NAS or the Router. But since the NAS is more powerful, I get a better bandwidth if I go through it rather than the Router.

I would like to have an option in the unsafe_routes to specify a priority like:

unsafe_routes:
    - route: 192.168.1.0/24
      via: 192.168.99.1
      priority: 1
    - route: 192.168.1.0/24
      via: 192.168.99.2
      priority: 2

So, my nebula client should first try to reach 192.168.1.0 network through 192.168.99.1 and, if 192.168.99.1 is not reachable, start looking for 192.168.99.2.

How do you see it?

Ciao!
M

[hulucc]

Same requirement but I want to do unsafe_routes high availability.

[ton31337]

Related: #474

[wadey]

#474 was merged, so closing this issue.

[dhananjays]

Is this issue really addressed by #474 ?
It seems like that only supports the case where the two routes are via different interfaces (eg. one via openVpn while another via nebula)

When we are trying to define both routes via nebula (similar to the routes mentioned by OP #353 (comment)), we are seeing that whichever route is later in the config gets used (irrespective of value of metric). We are using v1.6.1

CC: @hulucc @Mrc527 Is your use-case working with 1.6.1?

[dhananjays]

@wadey I think this issue isn't addressed by #474. Can you please reopen this issue?

[undo-alex]

Is this issue really addressed by #474 ? It seems like that only supports the case where the two routes are via different interfaces (eg. one via openVpn while another via nebula)

When we are trying to define both routes via nebula (similar to the routes mentioned by OP #353 (comment)), we are seeing that whichever route is later in the config gets used (irrespective of value of metric). We are using v1.6.1

CC: @hulucc @Mrc527 Is your use-case working with 1.6.1?

Hi. We are trying to get use of metric feature in unsafe_routes and we see the same issue as dhananjays in version 1.6.1 and 1.7.0.

Any idea if this is going to be looked at? Thank you

[johnmaguire]

Hi @undo-alex and @dhananjays - the best way to let the team know this issue is a priority to you is to give the original issue a 👍 reaction. This way we can sort issues by votes. Thank you!