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
Testing with the 9 visor public keys which have updated to v1.3.21 and which provide proxy servers in the US (according to SD which is known to use an outdated ip geo-location database)
Transports were established from my local visor to each key in the list
$ skywire cli proxy list -v v1.3.21 -c US | while read _pk ; do echo $_pk ; skywire cli tp add -t dmsg $_pk ; done
022e504c96fae546deae42f1109a9effed6ba5e427f01ec864f1fedcab6723b25a
[2024-04-18T09:58:14.487142465-05:00] INFO [skywire-cli]: Established dmsg transport to 022e504c96fae546deae42f1109a9effed6ba5e427f01ec864f1fedcab6723b25a
type id remote_pk mode label
dmsg f8a80bcf-35f1-0d67-bd43-37d39e1771e2 022e504c96fae546deae42f1109a9effed6ba5e427f01ec864f1fedcab6723b25a regular user
025b8f1a36bbdc1678811c26035ce1b84e92a3bf75ab439790c82143e81a07b419
[2024-04-18T09:58:14.644125734-05:00] INFO [skywire-cli]: Established dmsg transport to 025b8f1a36bbdc1678811c26035ce1b84e92a3bf75ab439790c82143e81a07b419
type id remote_pk mode label
dmsg bf97fc52-a273-0016-b063-d7a7518fbf13 025b8f1a36bbdc1678811c26035ce1b84e92a3bf75ab439790c82143e81a07b419 regular user
02781a0ac87d137d612bdefc5d68f420125887771e2d5cf6bc710c83ffc3b9d696
[2024-04-18T09:58:14.798216988-05:00] INFO [skywire-cli]: Established dmsg transport to 02781a0ac87d137d612bdefc5d68f420125887771e2d5cf6bc710c83ffc3b9d696
type id remote_pk mode label
dmsg eb54647a-67ab-097b-83ff-b93072e542a2 02781a0ac87d137d612bdefc5d68f420125887771e2d5cf6bc710c83ffc3b9d696 regular user
029eb3bd20846d6488132310236e2eab7d3b5dd92fb06050c765ce8f0b916eb8ec
[2024-04-18T09:58:14.953384269-05:00] INFO [skywire-cli]: Established dmsg transport to 029eb3bd20846d6488132310236e2eab7d3b5dd92fb06050c765ce8f0b916eb8ec
type id remote_pk mode label
dmsg e3127e3f-b939-06e2-82cb-e0a091986a82 029eb3bd20846d6488132310236e2eab7d3b5dd92fb06050c765ce8f0b916eb8ec regular user
03075370d8cc7f2b66d19795ca47f8bfe26ee5cd755029c59616c900319c2f4b63
[2024-04-18T09:58:15.11548611-05:00] INFO [skywire-cli]: Established dmsg transport to 03075370d8cc7f2b66d19795ca47f8bfe26ee5cd755029c59616c900319c2f4b63
type id remote_pk mode label
dmsg af3b7106-6b30-02fd-824d-bf3248ca83ff 03075370d8cc7f2b66d19795ca47f8bfe26ee5cd755029c59616c900319c2f4b63 regular user
0318536c5b6ab85edbd61666c0a675033528bc3b474ea8669bd8b2caef08248f3b
[2024-04-18T09:58:15.272589471-05:00] INFO [skywire-cli]: Established dmsg transport to 0318536c5b6ab85edbd61666c0a675033528bc3b474ea8669bd8b2caef08248f3b
type id remote_pk mode label
dmsg 368ad924-778c-08da-98ae-62b11f4d7416 0318536c5b6ab85edbd61666c0a675033528bc3b474ea8669bd8b2caef08248f3b regular user
03419b3c3f9db0404b44afc532a91eb2c108499f7575d0e7937dd8d076d385b607
[2024-04-18T09:58:15.4320917-05:00] INFO [skywire-cli]: Established dmsg transport to 03419b3c3f9db0404b44afc532a91eb2c108499f7575d0e7937dd8d076d385b607
type id remote_pk mode label
dmsg 3a306a5d-7000-00ea-ab83-d45b5a5151e3 03419b3c3f9db0404b44afc532a91eb2c108499f7575d0e7937dd8d076d385b607 regular user
03a3dfc9819cd6cddd97e3b2af553151f2c02263e7da0a5d55857d56a5efc59367
[2024-04-18T09:58:15.587856724-05:00] INFO [skywire-cli]: Established dmsg transport to 03a3dfc9819cd6cddd97e3b2af553151f2c02263e7da0a5d55857d56a5efc59367
type id remote_pk mode label
dmsg 5b6598fd-4e13-0a72-8745-f1d587427178 03a3dfc9819cd6cddd97e3b2af553151f2c02263e7da0a5d55857d56a5efc59367 regular user
03b7f091b03bf62a69c664bee8c1cbf59469874801334adaabba9e880bec899215
[2024-04-18T09:58:15.741053902-05:00] INFO [skywire-cli]: Established dmsg transport to 03b7f091b03bf62a69c664bee8c1cbf59469874801334adaabba9e880bec899215
type id remote_pk mode label
dmsg e7e04369-1875-08e4-8485-5db987279cab 03b7f091b03bf62a69c664bee8c1cbf59469874801334adaabba9e880bec899215 regular user
Confirmation of the transports which exist via transport discovery
$ skywire cli tp disc -p $(skywire cli visor pk)
id type edge1 edge2
bf97fc52-a273-0016-b063-d7a7518fbf13 dmsg 025b8f1a36bbdc1678811c26035ce1b84e92a3bf75ab439790c82143e81a07b419 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c
af3b7106-6b30-02fd-824d-bf3248ca83ff dmsg 03075370d8cc7f2b66d19795ca47f8bfe26ee5cd755029c59616c900319c2f4b63 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c
368ad924-778c-08da-98ae-62b11f4d7416 dmsg 0318536c5b6ab85edbd61666c0a675033528bc3b474ea8669bd8b2caef08248f3b 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c
3a306a5d-7000-00ea-ab83-d45b5a5151e3 dmsg 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c 03419b3c3f9db0404b44afc532a91eb2c108499f7575d0e7937dd8d076d385b607
e7e04369-1875-08e4-8485-5db987279cab dmsg 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c 03b7f091b03bf62a69c664bee8c1cbf59469874801334adaabba9e880bec899215
f8a80bcf-35f1-0d67-bd43-37d39e1771e2 dmsg 022e504c96fae546deae42f1109a9effed6ba5e427f01ec864f1fedcab6723b25a 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c
eb54647a-67ab-097b-83ff-b93072e542a2 dmsg 02781a0ac87d137d612bdefc5d68f420125887771e2d5cf6bc710c83ffc3b9d696 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c
e3127e3f-b939-06e2-82cb-e0a091986a82 dmsg 029eb3bd20846d6488132310236e2eab7d3b5dd92fb06050c765ce8f0b916eb8ec 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c
5b6598fd-4e13-0a72-8745-f1d587427178 dmsg 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c 03a3dfc9819cd6cddd97e3b2af553151f2c02263e7da0a5d55857d56a5efc59367
$ skywire cli tp
type id remote_pk mode label
dmsg 368ad924-778c-08da-98ae-62b11f4d7416 0318536c5b6ab85edbd61666c0a675033528bc3b474ea8669bd8b2caef08248f3b regular user
dmsg 3a306a5d-7000-00ea-ab83-d45b5a5151e3 03419b3c3f9db0404b44afc532a91eb2c108499f7575d0e7937dd8d076d385b607 regular user
dmsg 5b6598fd-4e13-0a72-8745-f1d587427178 03a3dfc9819cd6cddd97e3b2af553151f2c02263e7da0a5d55857d56a5efc59367 regular user
dmsg af3b7106-6b30-02fd-824d-bf3248ca83ff 03075370d8cc7f2b66d19795ca47f8bfe26ee5cd755029c59616c900319c2f4b63 regular user
dmsg bf97fc52-a273-0016-b063-d7a7518fbf13 025b8f1a36bbdc1678811c26035ce1b84e92a3bf75ab439790c82143e81a07b419 regular user
dmsg e3127e3f-b939-06e2-82cb-e0a091986a82 029eb3bd20846d6488132310236e2eab7d3b5dd92fb06050c765ce8f0b916eb8ec regular user
dmsg e7e04369-1875-08e4-8485-5db987279cab 03b7f091b03bf62a69c664bee8c1cbf59469874801334adaabba9e880bec899215 regular user
dmsg eb54647a-67ab-097b-83ff-b93072e542a2 02781a0ac87d137d612bdefc5d68f420125887771e2d5cf6bc710c83ffc3b9d696 regular user
dmsg f8a80bcf-35f1-0d67-bd43-37d39e1771e2 022e504c96fae546deae42f1109a9effed6ba5e427f01ec864f1fedcab6723b25a regular user
There are 9 keys here, not including my own, for a total of 10 keys.
A route cannot go through the same visor twice
Hence, the maximum number of hops should be half the number of keys.
10 / 2 = 5
A route with up to 5 hops should be possible.
If the first key and the last key of the route remain the same, it should be possible to have 2 * 2 * 2 * 2 * 2 = 32 routes from my key to any other key in that list.
It should further be possible to have 16 possible 4-hop routes, 8 possible 3-hop routes, and 4 possible 2-hop routes.
tests of skywire cli route find - first with the default 1 hop
$ skywire cli proxy list -v v1.3.21 -c US | while read _pk ; do echo $_pk ; skywire cli route find -n3 -x3 $_pk ; echo ; echo ; done ; echo
022e504c96fae546deae42f1109a9effed6ba5e427f01ec864f1fedcab6723b25a
[2024-04-18T10:32:23.534345707-05:00] FATAL [skywire-cli]: transport not found
025b8f1a36bbdc1678811c26035ce1b84e92a3bf75ab439790c82143e81a07b419
[2024-04-18T10:32:24.223133083-05:00] FATAL [skywire-cli]: transport not found
02781a0ac87d137d612bdefc5d68f420125887771e2d5cf6bc710c83ffc3b9d696
[2024-04-18T10:32:24.862692817-05:00] FATAL [skywire-cli]: transport not found
029eb3bd20846d6488132310236e2eab7d3b5dd92fb06050c765ce8f0b916eb8ec
[2024-04-18T10:32:25.516558448-05:00] FATAL [skywire-cli]: transport not found
03075370d8cc7f2b66d19795ca47f8bfe26ee5cd755029c59616c900319c2f4b63
[2024-04-18T10:32:26.161052215-05:00] FATAL [skywire-cli]: transport not found
0318536c5b6ab85edbd61666c0a675033528bc3b474ea8669bd8b2caef08248f3b
[2024-04-18T10:32:26.818670857-05:00] FATAL [skywire-cli]: transport not found
03419b3c3f9db0404b44afc532a91eb2c108499f7575d0e7937dd8d076d385b607
[2024-04-18T10:32:27.521366805-05:00] FATAL [skywire-cli]: transport not found
03a3dfc9819cd6cddd97e3b2af553151f2c02263e7da0a5d55857d56a5efc59367
[2024-04-18T10:32:28.177572504-05:00] FATAL [skywire-cli]: transport not found
03b7f091b03bf62a69c664bee8c1cbf59469874801334adaabba9e880bec899215
[2024-04-18T10:32:28.890815998-05:00] FATAL [skywire-cli]: transport not found
min, max hops = 4
$ skywire cli proxy list -v v1.3.21 -c US | while read _pk ; do echo $_pk ; skywire cli route find -n4 -x4 $_pk ; echo ; echo ; done ; echo
022e504c96fae546deae42f1109a9effed6ba5e427f01ec864f1fedcab6723b25a
[2024-04-18T10:33:36.896984312-05:00] FATAL [skywire-cli]: transport not found
025b8f1a36bbdc1678811c26035ce1b84e92a3bf75ab439790c82143e81a07b419
[2024-04-18T10:33:37.573298574-05:00] FATAL [skywire-cli]: transport not found
02781a0ac87d137d612bdefc5d68f420125887771e2d5cf6bc710c83ffc3b9d696
[2024-04-18T10:33:38.244392288-05:00] FATAL [skywire-cli]: transport not found
029eb3bd20846d6488132310236e2eab7d3b5dd92fb06050c765ce8f0b916eb8ec
[2024-04-18T10:33:38.876893555-05:00] FATAL [skywire-cli]: transport not found
03075370d8cc7f2b66d19795ca47f8bfe26ee5cd755029c59616c900319c2f4b63
[2024-04-18T10:33:39.520027991-05:00] FATAL [skywire-cli]: transport not found
0318536c5b6ab85edbd61666c0a675033528bc3b474ea8669bd8b2caef08248f3b
[2024-04-18T10:33:40.154807991-05:00] FATAL [skywire-cli]: transport not found
03419b3c3f9db0404b44afc532a91eb2c108499f7575d0e7937dd8d076d385b607
[2024-04-18T10:33:40.825226237-05:00] FATAL [skywire-cli]: transport not found
03a3dfc9819cd6cddd97e3b2af553151f2c02263e7da0a5d55857d56a5efc59367
[2024-04-18T10:33:41.47681786-05:00] FATAL [skywire-cli]: transport not found
03b7f091b03bf62a69c664bee8c1cbf59469874801334adaabba9e880bec899215
[2024-04-18T10:33:42.140122224-05:00] FATAL [skywire-cli]: transport not found
min, max hops = 5
$ skywire cli proxy list -v v1.3.21 -c US | while read _pk ; do echo $_pk ; skywire cli route find -n5 -x5 $_pk ; echo ; echo ; done ; echo
022e504c96fae546deae42f1109a9effed6ba5e427f01ec864f1fedcab6723b25a
[2024-04-18T10:34:25.983848668-05:00] FATAL [skywire-cli]: transport not found
025b8f1a36bbdc1678811c26035ce1b84e92a3bf75ab439790c82143e81a07b419
[2024-04-18T10:34:26.673128462-05:00] FATAL [skywire-cli]: transport not found
02781a0ac87d137d612bdefc5d68f420125887771e2d5cf6bc710c83ffc3b9d696
[2024-04-18T10:34:27.338371729-05:00] FATAL [skywire-cli]: transport not found
029eb3bd20846d6488132310236e2eab7d3b5dd92fb06050c765ce8f0b916eb8ec
[2024-04-18T10:34:28.002208239-05:00] FATAL [skywire-cli]: transport not found
03075370d8cc7f2b66d19795ca47f8bfe26ee5cd755029c59616c900319c2f4b63
[2024-04-18T10:34:28.6778144-05:00] FATAL [skywire-cli]: transport not found
0318536c5b6ab85edbd61666c0a675033528bc3b474ea8669bd8b2caef08248f3b
[2024-04-18T10:34:29.351720407-05:00] FATAL [skywire-cli]: transport not found
03419b3c3f9db0404b44afc532a91eb2c108499f7575d0e7937dd8d076d385b607
[2024-04-18T10:34:30.021480568-05:00] FATAL [skywire-cli]: transport not found
03a3dfc9819cd6cddd97e3b2af553151f2c02263e7da0a5d55857d56a5efc59367
[2024-04-18T10:34:30.664901804-05:00] FATAL [skywire-cli]: transport not found
03b7f091b03bf62a69c664bee8c1cbf59469874801334adaabba9e880bec899215
[2024-04-18T10:34:31.314702793-05:00] FATAL [skywire-cli]: transport not found
This is very likely to be an issue with the route finder itself.
The text was updated successfully, but these errors were encountered:
0pcom
changed the title
skywire cli route find not returning routes with more than 2 hops when 5 hops are possibleskywire cli route find route finder not returning routes with more than 2 hops when 5 hops are possible
Apr 20, 2024
I attempted to test a local instance of the route-finder with a visor running locally - however, it did not return any routes at all.
Apparently the route-finder does not look at the transport discovery? it's also apparent that any visors that one desires to establish a route to needs to use the same route finder as the local visor. This makes testing quite difficult.
Erson pointed out that the route finder is supposed to use the same database as transport-discovery. So that explains why it wasn't working on it's own.
It's also wrongly documented that it uses it's own database in the deployment documentation
Testing with the 9 visor public keys which have updated to v1.3.21 and which provide proxy servers in the US (according to SD which is known to use an outdated ip geo-location database)
Transports were established using the transport setup-node between adjacent keys in the above list
Transports were established using the transport setup-node between even-even and odd-odd keys by their array index
Result:
Transports were established from my local visor to each key in the list
Confirmation of the transports which exist via transport discovery
The local visor's transports
There are 9 keys here, not including my own, for a total of 10 keys.
A route cannot go through the same visor twice
Hence, the maximum number of hops should be half the number of keys.
10 / 2 = 5
A route with up to 5 hops should be possible.
If the first key and the last key of the route remain the same, it should be possible to have 2 * 2 * 2 * 2 * 2 = 32 routes from my key to any other key in that list.
It should further be possible to have 16 possible 4-hop routes, 8 possible 3-hop routes, and 4 possible 2-hop routes.
tests of
skywire cli route find
- first with the default 1 hopmin, max hops = 2
min, max hops = 3
min, max hops = 4
min, max hops = 5
This is very likely to be an issue with the route finder itself.
The text was updated successfully, but these errors were encountered: