Opened 7 years ago

Closed 7 years ago

#1281 closed enhancement (fixed)

i2psnark DHT: Implement flooding

Reported by: zzz Owned by: zzz
Priority: minor Milestone: 0.9.14
Component: apps/i2psnark Version: 0.9.12
Keywords: Cc:
Parent Tickets: Sensitive: no


http://zzz.i2p/topics/1613 comment 4:

One thing missing (AFAIK) from yours is that you don't do any forwarding of values stored to the 'K-1' other nodes closest to you (unless I missed this?) Doing this does increase the resilience of the DHT to node churn quite a lot, but introduces various issues around the originator of values.


Change History (3)

comment:1 Changed 7 years ago by zzz

See also comments 11 and 12 in link above.

Libtorrent also announces to the K-closest (see node.cpp announce_fun())

This would be combined with lengthening the announce interval and expiration time, to maintain or reduce the total announce/get_peers bandwidth.

comment:2 Changed 7 years ago by zzz

Status: newtesting

In e40cda3dd4d2c4b3354c53fc329789dbd0360853 i2p.i2p.zzz.test2 to be propped for 0.9.14:

  • Extend DHT tracker expire time from 45m to 3h
  • Extend DHT announce interval from 10m to 40m
  • Increase announces from 1 peer to 4

May increase the timeouts and announces again later after testing.

comment:3 Changed 7 years ago by zzz

Resolution: fixed
Status: testingclosed

propped in 0.9.13-2.

Note: See TracTickets for help on using tickets.