Ping in terminal CLI uses wrong id #114

New Issue

2026-10-27T09:33:56+01:00

adam commented

2026-10-27 09:33:56 +01:00

repeater v1.1.2-dev1
core v1.1.1
Path hash length: 2 byte

When trying to ping a local repeater that has 0x8e21 as id, it does not recognize it as being in the neighbor list.
Error: Node '0x8e21' not found in neighbors
Using the name of the repeater at least sends something (same with ping 0x8e):
Pinging UME-ACC-Backen-8E21 (0x8e) with 10s timeout...
it will fail to receive a reply, and this is what's in the log:
HTTPServer - INFO - Ping sent to 0x008e with tag 2339094271 (path_hash_mode=1)

Using the web-ui it works fine and gets a response:
HTTPServer - INFO - Ping sent to 0x8e21 with tag 1810524095 (path_hash_mode=1)

repeater v1.1.2-dev1 core v1.1.1 Path hash length: 2 byte When trying to ping a local repeater that has 0x8e21 as id, it does not recognize it as being in the neighbor list. ` Error: Node '0x8e21' not found in neighbors` Using the name of the repeater at least sends something (same with ping 0x8e): `Pinging UME-ACC-Backen-8E21 (0x8e) with 10s timeout...` it will fail to receive a reply, and this is what's in the log: `HTTPServer - INFO - Ping sent to 0x008e with tag 2339094271 (path_hash_mode=1)` Using the web-ui it works fine and gets a response: `HTTPServer - INFO - Ping sent to 0x8e21 with tag 1810524095 (path_hash_mode=1)`

adam closed this issue

2026-10-27 09:33:56 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#114