> From: > > Gianni Johansson <giannijohansson at mediaone.net> > > >2) Implement per host inbound connection limits. >I think what's happening now is that your node manages to contact a few other >nodes and accumulates a pool of cached connections to them which >is constantly recycled. That's why your node reliably connects to so few >other nodes, and why the nodes that it does connect to change seemingly at >random. Since there's a fixed connection limit (30 by default), once the OCM >connection cache fills up almost all inbound connections from >other nodes will be rejected. > >Placing a per host limit on inbound connections would decrease the severity >of this problem. > >I have been looking into this. It's kind of tricky because you don't want >to reject an incoming connection for a message chain >that your node originated, but you don't have the message chain ID until >after you have accepted the connection. Any ideas? >
Would limiting per node outbound connections not do the same thing? You could then have the node make an exception for replies to requests. Limiting on inbound connections could be set at a higher level to limit the damage done from bad nodes that are obviously trying to flood you. How about per node connection pools rather than one big one? If a node has too many pending transactions then it bumps its own old ones. Just ideas with little knowledge of if this could be easily done in code. Mike _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
