-
Notifications
You must be signed in to change notification settings - Fork 45
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
Multi-hop routes not working automatically ; erroneous auto-transport creation #1793
Comments
A test of manual route creation shows that, despite the existence of a route, when starting the proxy another, a transport and another direct route is created ; the proxy actually uses that one to connect instead of the existing route! perhaps I did not configure the route correctly @mrpalide ?
perhaps the issue is apparent here, some routes have the same route id! Here's the routing table:
Visor debug logging
|
Another attempt at a test of multihop routes using transport setup-node I created transports between (10) US visors providing proxy servers of version 1.3.21 currently
I ran the above command a few times so that enough transports would exist between those visors after setting min_hops in the visor's config to 3 i start a visor and made transports to all of the above visors
then i check for routes
the above was with 2 hops, however when I check for a route with 3 hops, none are returned
there should be sufficient transports in this instance to support a route with 3 hops, but none are returned. |
Regardless of the minimum hops set, the visor will attempt to make a direct transport to another public key.
A visor was started with minimum hops = 1
transports were created to several heavily transported visors (
skywire-cli rtree -s | head -n100
) .A proxy server with potential multihop routes was selected and connected to.
when the proxy server was started, a direct transport was established automatically to that visor which should not happen in this instance
When the transport was deleted, the connection was broken - despite the possibility of alternative routes and despite having more than 1 hop configured
The text was updated successfully, but these errors were encountered: