Opened 4 years ago

Closed 3 years ago

#1513 closed task (fixed)

shutdown fetching of individual dat-files

Reported by: backup Owned by: meeh
Priority: minor Milestone: 0.9.20
Component: www/reseed Version: 0.9.18
Keywords: Cc:
Parent Tickets:

Description

shutdown fetching of individual dat-files in Reseeder.java

We have enough server providing su3-files and get an alternate way of reseeding on client side.

http://zzz.i2p/topics/1855-shutdown-dat-files-plain-http-reseeding

Subtickets

Change History (9)

comment:1 Changed 4 years ago by zzz

  • Status changed from new to infoneeded_new

I can do this, but we'll need to remove all hosts from the defaults that don't support su3. Please provide a list of hosts to remove.

comment:2 Changed 4 years ago by zzz

  • Status changed from infoneeded_new to new

This is also a good thing as it will speed up skipping over unresponsive reseed hosts, as we will only try them once, not twice.

comment:3 Changed 4 years ago by zzz

  • Status changed from new to infoneeded_new

comment:4 Changed 4 years ago by killyourtv

  • Status changed from infoneeded_new to new
Last edited 4 years ago by killyourtv (previous) (diff)

comment:5 Changed 4 years ago by zzz

0.9.19-6 has a change to make it super-easy to disable non-su3 reseed. just make the following additional change to disable it in Reseeder.java:

-    private static final boolean ENABLE_NON_SU3 = true;
+    private static final boolean ENABLE_NON_SU3 = false;

SU3 reseeding was implemented in 0.9.14 released 2014-07-26. Has enough time (and enough releases) gone by for us to disable it for 0.9.20? Are there any distros or other packagers bundling 0.9.13 or older? What are the odds of somebody booting up I2P for the first time in a year, and needs to reseed? Of course we'd have to go back and see what reseeds were the defaults back then. If none of them are still up, it doesn't matter.

Please discuss...

comment:6 Changed 4 years ago by zzz

  • Owner changed from zzz to backup
  • Status changed from new to assigned

Above change checked in as e2d3995cb73aac265c3872374a22ed1b2722809b, to be 0.9.19-6, since whatever we do in 0.9.20 can't affect older versions.

Reassigning to OP (backup) to decide on a timetable (see issues to consider in comment 5 above) and notify reseed hosters. Any reseed hosts that were not in the default list in 0.9.13 (released 2014-05-22) or older can disable non-su3 support immediately, as compatibility issues do not apply to them.

I also received approval from orignal today to disable non-su3 support, as far as i2pd is concerned.

comment:7 Changed 4 years ago by zzz

Note that the timetable for the reseed hosts should be independent of our 0.9.20 release plans, since we always try su3 first. A lot of our hosts are su3-only already. The only issue is whether to continue support for old routers for some period of time.

comment:8 Changed 3 years ago by backup

  • Owner changed from backup to meeh

server side:

All reseed server (except two from meeh) are fixed and provide only signed su3-files.

Thanks very much,
backup

comment:9 Changed 3 years ago by zzz

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

Closing as fixed in 0.9.20. If there's anything remaining to do on the reseed server side, please work with the operators directly. This means you Meeh :)

Note: See TracTickets for help on using tickets.