Since the upgrade to V1.17.1 (I suspect #3106), if I try to log into a repeater direct that is 1 or more hops away (and that repeater doesn't have a stored return path), I never receive a reply. (This was received as expected in 1.16)
The only way I can now log in to a repeater is to first login "Flood" so that the repeater records a return path, then a reply is received and subsequent logins can be sent as direct. Often this flood path picks weak repeaters over several hops, when one strong hop is much preferred.
Repeater owners almost always know the best route to their repeater and can thus supply a working path.
Does the login request supply (or is it capable of supplying) this path?
I note a value in the code of REPLY_ROUTE_DIRECT_SUPPLIED, which seems to suggest that packets can carry a return path.
Is it simply a matter of the app, when logging in with the "Log In - x hops" option, supplies the app-stored path with the login request, which can then be acknowledged directly back on that path? This would make repeater administration so much easier, and more reliable!
Thanks,
Since the upgrade to V1.17.1 (I suspect #3106), if I try to log into a repeater direct that is 1 or more hops away (and that repeater doesn't have a stored return path), I never receive a reply. (This was received as expected in 1.16)
The only way I can now log in to a repeater is to first login "Flood" so that the repeater records a return path, then a reply is received and subsequent logins can be sent as direct. Often this flood path picks weak repeaters over several hops, when one strong hop is much preferred.
Repeater owners almost always know the best route to their repeater and can thus supply a working path.
Does the login request supply (or is it capable of supplying) this path?
I note a value in the code of REPLY_ROUTE_DIRECT_SUPPLIED, which seems to suggest that packets can carry a return path.
Is it simply a matter of the app, when logging in with the "Log In - x hops" option, supplies the app-stored path with the login request, which can then be acknowledged directly back on that path? This would make repeater administration so much easier, and more reliable!
Thanks,