Skip to content

apply tunnel parameters on reload - #2489

Merged
orignal merged 1 commit into
PurpleI2P:opensslfrom
pobregat0:tunnel-reload-params
Aug 17, 2026
Merged

apply tunnel parameters on reload#2489
orignal merged 1 commit into
PurpleI2P:opensslfrom
pobregat0:tunnel-reload-params

Conversation

@pobregat0

Copy link
Copy Markdown
Contributor

Tunnel parameters are taken when the destination is made, so a reload never
changed them: FindLocalDestination hands back the running destination and the
options read from the section were dropped on the floor.

Reconfigure is already there and used by I2CP, so the reload calls it. The pool
takes the new numbers as it is, without being torn down: it builds the tunnels
it lacks and lets the extra ones expire. A destination shared by several
tunnels is left alone, only the section that owns it can change it.

Checked on a live router: with inbound and outbound quantity raised from 3 to 8
a reload took the destination from 6 tunnels to 10 within 150 seconds and it
kept climbing, connections through the tunnel stayed alive, and a reload with
an unchanged config leaves everything as it was.

@orignal
orignal merged commit d9cd383 into PurpleI2P:openssl Aug 17, 2026
15 checks passed
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.

2 participants