Opened 8 years ago

Closed 8 years ago

#898 closed enhancement (no response)

Stop rejecting ALL tunnels

Reported by: DISABLED Owned by:
Priority: minor Milestone: 0.9.9
Component: router/general Version: 0.9.4
Keywords: Cc:
Parent Tickets: Sensitive: no


Don't reject client(me connecting to IRC2P or someone connecting to my HTTPd) tunnels due to heavy load..

if I have many partcipating, it is annoyance to notice all tunnels are rejected - and having to mess with settings or participating is annoying.

Can we have a way of balancing it out which is better.. or stop rejecting clients if we have a large amount of participating?

Not sure what the solution would be but the problem is there. How about reject all new participating while we wait for the pool to die down but NOT stop new clients?


Change History (4)

comment:1 Changed 8 years ago by Eche|on

Type: defectenhancement

In I2P we reject participating tunnel and drop them first if the load gets to high or bandwidth limits are hit. Client tunnel come next.
If the load is to high, we need to drop and reject tunnels to lower the load - with high load no tunnel will be built at all (other router do reject tunnels with to high latency). So no use to keep tunnels active built with high load.

comment:2 Changed 8 years ago by Eche|on

Forgot: - more information about all that rules. Not perfect and slighty changed the last 4 years. But still fine.

comment:3 Changed 8 years ago by zzz

Component: unspecifiedrouter/general

Please clarify your request, I'm a little confused. Let me clarify the terminology:

  • Participating tunnels (those created by others thru you) are accepted/rejected based on several factors. You can't accept everything or it will overwhelm your network and/or CPU capacity.
  • Tunnels you attempt to create, for your clients, are never "rejected" by you - only by others.
  • Incoming streaming connections, through inbound tunnels you created, to your eepsite, are rejected only if they exceed the quantities set in i2ptunnel (unlimited by default). This has nothing to do with tunnels or loads or bandwidth.

Please restate your request using the above terminology.

comment:4 Changed 8 years ago by zzz

Resolution: no response
Status: newclosed

No response, closing. Please reopen if you respond.

Note: See TracTickets for help on using tickets.