Skip to content

fix: emit caplin bootnode override and enable local discovery#1452

Open
MysticRyuujin wants to merge 1 commit into
ethpandaops:mainfrom
MysticRyuujin:caplin-bootnode-fix
Open

fix: emit caplin bootnode override and enable local discovery#1452
MysticRyuujin wants to merge 1 commit into
ethpandaops:mainfrom
MysticRyuujin:caplin-bootnode-fix

Conversation

@MysticRyuujin

Copy link
Copy Markdown
Contributor

Summary

Two fixes to the Caplin launcher's peer discovery on private networks:

  • Emit bootnode_enr_override. The override (set when bootnodoor is the network bootnode) was assigned to bootnode_arg but only the bootnode_contexts path ever appended --sentinel.bootnodes, so a non-null override was silently dropped and Caplin nodes never learned the bootnode. Restructured to match the other CL launchers (assign bootnode_arg, emit once at the end).
  • Add --local-discovery. Caplin otherwise refuses to discover peers on private IPs. Added unconditionally in the base command, matching how the package sets the equivalent flags for Lighthouse/Grandine (--enable-private-discovery) and Teku (--p2p-discovery-site-local-addresses-enabled=true).

Testing

Verified live on docker: 2× geth/caplin + bootnodoor — with these fixes both Caplins receive --sentinel.bootnodes=<bootnodoor ENR> and connect to each other (previously 0 peers).

- a non-null bootnode_enr_override was silently dropped; emit it as --sentinel.bootnodes like other CL launchers
- add --local-discovery unconditionally, matching lighthouse/grandine/teku private-discovery flags
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant