You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent changes on develop have altered the way that min_hops is interpreted with regards to routing. Now, a value of 0 will basically block routes from being created by the visor. We need to change the default min_hops to 1 so that routing will work with the default config which is generated - before v1.3.29 is released.
The text was updated successfully, but these errors were encountered:
It should be noted in the documentation that setting min_hops as 2 does not prevent a single hop route from being used, it merely prevents auto-transport creation. This seems incorrect, but it should be noted in documentation if nothing else
Recent changes on develop have altered the way that
min_hops
is interpreted with regards to routing. Now, a value of0
will basically block routes from being created by the visor. We need to change the defaultmin_hops
to1
so that routing will work with the default config which is generated - before v1.3.29 is released.The text was updated successfully, but these errors were encountered: