Opened 6 years ago

Closed 5 years ago

#720 closed enhancement (fixed)

Implement per-destination priority

Reported by: zzz Owned by: zzz
Priority: minor Milestone: 0.9.4
Component: router/transport Version: 0.9.1
Keywords: Cc:
Parent Tickets:

Description

Once #719 is implemented, cross-connection priorities will work better. Then we can add a priority adjustment (say +/- 20) to the default outbound priority of 400, and poof, we can set HTTP Proxy to a higher priority than i2psnark, for example.

Requires changes to i2ptunnel UI, router/client, tunnel/OutboundReceiver and other tunnel OBGW code. Also requires changing the way priorities are mapped to stats in CoDelPriorityBlockingQueue?.

Subtickets

Change History (7)

comment:1 Changed 6 years ago by zzz

  • Milestone changed from 0.9.3 to 0.9.4
  • Type changed from defect to enhancement

comment:2 Changed 6 years ago by zzz

Implemented in 0.9.3-2, untested. No field in i2ptunnel GUI. Note that #719 is not implemented so this has limited effect.

Leaving open for testing.

comment:3 Changed 6 years ago by str4d

  • Keywords test added
  • Milestone 0.9.4 deleted

comment:8 Changed 5 years ago by str4d

  • Keywords testing-needed added; test removed

comment:9 Changed 5 years ago by str4d

  • Keywords testing-needed removed
  • Status changed from new to testing

comment:10 Changed 5 years ago by str4d

  • Milestone set to 0.9.4

comment:11 Changed 5 years ago by zzz

  • Resolution set to fixed
  • Status changed from testing to closed

We have default priorities set in i2ptunnel now. Don't know if it helps but doesn't seem to hurt.

Note: See TracTickets for help on using tickets.