@RN_
@orignal
@postman
%Liorar
+Onn4l7h
+Over
+marek22k
+nyaa2pguy
+poriori
+profetikla
+qend-irc2p
+r00tobo
Irc2PGuest30010
acetone_
f00b4r_
fattydove
makoto
nZDoYBkF
noidea
not_bob_afk2
o3d3_
r00tobo[2]
solidx66
RN_
dr|z3d, has the latest dev vers of + been well tested yet or is it bleeding fresh?
orignal
finnally made it working
dr|z3d
should be good, RN. who's asking?
dr|z3d
now you just need to mirror the main site, orignal
dr|z3d
and cgit :)
dr|z3d
new build arriving soon, RN...
dr|z3d
Blinded message
dr|z3d
new in the latest build: tunable period and concurrency for hostchecker, leaseset encryption types indicated in SusiDNS per host.
cumlord
Like that :)
dr|z3d
also, orignal, tell your haiku buddies to fix this, it's 2026 (almost) -> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
cumlord
would it make sense to use same set of tunnels for it? Feel like it takes way longer than it could bc of that
dr|z3d
up to 100 sites at a time, cumlord. each new host lookup is staggered to avoid hammering the floodfills (2-5s delay).
dr|z3d
re same tunnel, not really. you don't want your pings across sites to be correlated.
cumlord
ah so intentional then. My pinger tool probably is too aggressive then
dr|z3d
but.. now we perform a LS lookup first, so if we don't get a response, we skip the other stages.
dr|z3d
depending on what you want with your pinger, you might find you get all the data you need from .i2p/addressbook/hosts_check.txt
cumlord
in the traffic correlation sense or in the linked to the same b32 sense?
cumlord
nice, thats also what I started doing when I did the port scanner thing, saves some time
cumlord
I’ll check it later, mainly just care if it’s up and response time
dr|z3d
you don't want to perform all your pings from a single dest.
dr|z3d
it's a good workout for your router, also. watch the sidepanel, see how long it takes to build tunnels for a ping dest.. when your router's been up a while, builds should be more or less instant.
dr|z3d
the format of the hostchecker (if you want to use the data elsewhere) is documented in that file.
dr|z3d
a response time of -1 indicates no response received.
cumlord
I guess why is what I’m wondering. I’ve tried single or multiple round robin dests that changes after each ping, or new dest for each site which just took a lot longer. But I also was trying probably too many at a time.
cumlord
also tried splitting the load among multiple routers that way
cumlord
nice, straightforward enough
dr|z3d
you were running with i2ping?
dr|z3d
max 100, minimum period is 1hr per cycle.
dr|z3d
defaults to max 12 concurrent pings every 8 hours.
cumlord
yeah that sounds pretty inefficient. I think whatever I had going was fairly lean from python perspective anyway lol
cumlord
might be able to replace the one simp with it then, it does nothing special
dr|z3d
we also randomize the hosts each cycle, not least to avoid hammering individual hosts.
dr|z3d
any host in your susidns blacklist will be skipped.
dr|z3d
and we're not continuously pinging the host and averaging the pings, either. as soon as we get a response, that time is recorded.
dr|z3d
todo in susidns is (maybe) a response time indicator bar, and filters for categories.
orignal
yes, the main site
orignal
to download packages