From 93ee6013a3ddebb86e53bbc8f3b2f5b4de76bcc2 Mon Sep 17 00:00:00 2001 From: Lukasz Biegaj Date: Sun, 25 Jan 2026 14:22:46 +0100 Subject: [PATCH] docs: clarify first byte key collision behavior in FAQ Explain that ID collisions affect traceroute but not packet delivery. Advise users to check local neighborhood for prefixes. Refs meshcore-dev/MeshCore#1202 --- docs/faq.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/faq.md b/docs/faq.md index 66a942a4a..46ed6910e 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -279,8 +279,11 @@ Reboot the repeater after `set prv.key ` command for the new private key to ### 3.6. Q: The first byte of my repeater's public key collides with an exisitng repeater on the mesh. How do I get a new private key with a matching public key that has its first byte of my choosing? -**A:** You can generate a new private key and specific the first byte of its public key here: https://gessaman.com/mc-keygen/ +**A:** You can generate a new private key and specify the first byte of its public key here: . +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. ### 3.7. Q: My repeater maybe suffering from deafness due to high power interference near my mesh's frequency, it is not hearing other in-range MeshCore radios. what can I do?