WIP: Tunnels: Per-participating-tunnel bandwidth limiters #521

Draft
zzz wants to merge 2 commits from zzz/i2p.i2p:tunnel-limiter into master
Owner

Using requested bandwidth parameters (prop. 168) when available

Prevents a single tunnel or over-aggressive streaming endpoints from
taking all bandwidth, ensuring more consistent part. tunnel counts,
acceptance rates, and available capacity.

Using requested bandwidth parameters (prop. 168) when available Prevents a single tunnel or over-aggressive streaming endpoints from taking all bandwidth, ensuring more consistent part. tunnel counts, acceptance rates, and available capacity.
zzz added this to the 2.11.0 milestone 2025-07-30 14:24:13 -04:00
zzz added the router label 2025-07-30 14:24:13 -04:00
zzz self-assigned this 2025-07-30 14:24:13 -04:00
zzz added 1 commit 2025-07-30 14:24:29 -04:00
Using requested bandwidth parameters (prop. 168) when available

Prevents a single tunnel or over-aggressive streaming endpoints from
taking all bandwidth, ensuring more consistent part. tunnel counts,
acceptance rates, and available capacity.
zzz added 1 commit 2025-08-09 10:17:33 -04:00
- Handle IBGW max BW param (prop. 168)
- Set allocated BW in config for all tunnels for display
- Display allocated BW on /tunnels

more fixes to follow
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u tunnel-limiter:zzz-tunnel-limiter
git checkout zzz-tunnel-limiter
Sign in to join this conversation.
No Reviewers
No Label router
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: I2P_Developers/i2p.i2p#521
No description provided.