docs: clarify first byte key collision behavior in FAQ#1478
Conversation
Explain that ID collisions affect traceroute but not packet delivery. Advise users to check local neighborhood for prefixes. Refs meshcore-dev#1202
|
Sorry I missed this PR. Thanks for creating this PR. I would still use the reply I posted in #1202, especially the second paragraph.
In many large meshes, it is not possible to choose a unique 1st byte pubic key, therefore the next best option is to choose a unique 1st byte public key within a few miles or within 1 to 3 hops. Would be great if you could update that and I will review and add my approval, or I can make the change later. either way works. Thanks for your contribution! |
|
@LitBomb happy to help. This issue confused many users. I've added the second paragraph. |
Co-authored-by: Wessel <wessel@weebl.me>
|
|
||
| Having multiple repeaters with the same first byte ID does not negatively affect the mesh or its functionality. Flood and pathed packets will still reach their destinations. First byte ID collision makes traceroute and path analysis harder because these tools don't know exactly which of the two (or more) colliding repeaters is the one in the path. | ||
|
|
||
| It is best practice when setting up a new repeater to choose a public key that has a prefix that is not in use in local area. |
There was a problem hiding this comment.
Sorry I missed this PR. Thanks for creating this PR. I would still use the reply I posted in #1202, especially the second paragraph.
Best practice is when you set up a new repeater, choose a public key that is not in use. if it is not possible to find a unique first byte for your repeater's public key, choose one that is unique within about 10 miles/km to minimize collision with nearby repeaters.
In many large meshes, it is not possible to choose a unique 1st byte pubic key, therefore the next best option is to choose a unique 1st byte public key within a few miles or within 1 to 3 hops.
Would be great if you could update that and I will review and add my approval, or I can make the change later. either way works.
Thanks for your contribution!
- Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev/MeshCore#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev/MeshCore#1893
- Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
|
Since this hasn't been merged yet, I submitted PR #2172 which includes other updates and changes in this PR. After 2172 is merged, this can be closed. |
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
|
This now has been superseeded by the merged pull request #2172. @lpiob or @liamcottle, can you please close this here? Regards! |
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
Explain that ID collisions affect traceroute but not packet delivery. Advise users to check local neighborhood for prefixes.
Refs #1202