~dr|z3d
@RN
@RN_
@Stormycloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%ardu
%cumlord
+HowardPlayzOfAdmin
+Onn4l7h
+Sh0ck
+Xeha
+hk
+moe
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+romer
+uop23ip
+waffles
+wew
Arch
BravoOreo
BubbRubb1
C341
Danny
Irc2PGuest10122
Irc2PGuest72586
Irc2PGuest74165
Irc2PGuest81794
Irc2PGuest83998
Irc2PGuest8714
Irc2PGuest92336
Liorar_
Meow
Over1
SigSegv
acetone_
aisle
anontor2
byakuren
halloy13412
makoto
maylay
nilbog
nnm--
pisslord
pory
r00tobo[2]
shiver_
simprelay
solidx66
thetia
u5657
zer0bitz__
uop23ip
has done reseed after 40min, dr|z3d netdb dat 600+, known 4k+
dr|z3d
ok, uop23ip, thanks. very strange, but I'll have to investigate more.
dr|z3d
600 sounds a little on the high side tbh, the i2p process definitely has write permissions on that folder?
dr|z3d
(you can check the timestamps for the dat files and ensure they're fairly recent, last 24 hours or so)
uop23ip
yeah modified last 10min.
dr|z3d
ok, thanks.
uop23ip
thanks and good luck hunting! router runs fine besides this "issue" btw, so np
dr|z3d
no worries, new build forthcoming shortly.
dr|z3d
Blinded message
dr|z3d
you may still see a reseed after 20m, uop23ip, still haven't identified why it's doing that, despite making code changes. hmm. it's not fatal, anyways. you can always specify i2p (http) tor as your socks proxy if you want to anonymize reseed requests while I get to the bottom of this.
dr|z3d
another update landing soon...
dr|z3d
Blinded message
dr|z3d
ok, uop23ip, from where I'
dr|z3d
*I'm sitting, looks like reseed is behaving now.
dr|z3d
(famous last words)
dr|z3d
zzz: zzzot warning, not sure it's noteworthy? > No listener found for protocol: 18 on port: 6969 from pool of 3 listeners
dr|z3d
18 is mux.
wew
dr|z3d i have 60 blocklist bans on f423a014 build
wew
with disabled blocklists
wew
oh lel
wew
since updating
wew
my router reseeded 6 times
wew
every 2 hours
T3s|4__
wew: I just pulled the latest from skank and restarted, which is: 8e338a4e (Build date: 2025-09-08 05:54:12 UTC)
wew
updating
wew
4 blocklist by ip entries after update
zzz
18 is raw which is wrong. might be tixati or somebody else testing/debugging
Sh0ck
Tixati :D
Sh0ck
Grew up with that
Sh0ck
Tehcnically limewire but when i switched to torrents that was my go to client
Sh0ck
Now its qbitorrent kek
zzz
you should try it, haven't seen it on a swarm yet
Sh0ck
Tixati?
zzz
yeah
Sh0ck
Automated my setup so qbittorrent plays really nice with it
Sh0ck
I barilly look at my torrent clients, i just tell it what i want and it gets it, only times i open my frontend is to add torrents i created or check on running transfers/seeds
Sh0ck
Or to add new magnets from i2p ;)
Sh0ck
Qbitorrent also plays nice with gluetun
Sh0ck
Makes it easy to update listener ports on the fly without restarting
Sh0ck
Whch is something you have to deal with when using VPN's that support portforwarding and P2P
zzz
the i2pforum crowd is giving qbittorrent good reviews
Sh0ck
Yeah its great
Sh0ck
Switched to it a few week back
Sh0ck
wondered why i never used it before
Sh0ck
Perhaps the stigma of qtorrent and derivatives
zzz
because it only recently started worked well with i2p?
Sh0ck
have not gotten into p2p on i2p prior to that
Sh0ck
So cannot tell, i only recently gotten serious about my contributions to the network and my setup regarding i2p
Sh0ck
Tier X all the way :)
dr|z3d
wew: what are the reasons for the bans?
dr|z3d
zzz: raw? we're not following standard protocol numbering??
dr|z3d
thanks
dr|z3d
I was going off this: en.wikipedia.org/wiki/List_of_IP_protocol_numbers
zzz
the constants are at the bottom of I2PSession.java
zzz
oh
zzz
I started with 6 and 17 to be cute
zzz
analogous to IANA
zzz
but then we just started incrementing
dr|z3d
"cute" LOL
zzz
they're just numbers. cute was probably a mistake if it led you to wikipedia
dr|z3d
saw 18 a few times, wondered wtf it meant, went looking, obviously to the wrong place, so I could put some basic string conversion in the logs.
dr|z3d
thanks for the clarification, I now have this:
dr|z3d
public String protocolNumberToString(int proto) {
dr|z3d
switch (proto) {
dr|z3d
case 0:
dr|z3d
return "ANY (0)";
dr|z3d
case 6:
dr|z3d
return "STREAMING (6)";
dr|z3d
case 17:
dr|z3d
return "DATAGRAM1 (17)";
dr|z3d
case 18:
dr|z3d
return "DATAGRAM_RAW (18)";
dr|z3d
case 19:
dr|z3d
return "DATAGRAM2 (19)";
dr|z3d
case 20:
dr|z3d
return "DATAGRAM3 (20)";
dr|z3d
default:
dr|z3d
return "Unknown (" + proto + ")";
dr|z3d
}
dr|z3d
}
Sh0ck
Are you posting this line my line?
zzz
looks right. the method can be static
wew
dr|z3d wdym
wew
i can screenshot you
wew
for you*
wew
11 blocklist bans right now
dr|z3d
public static final String protocolNumberToString(int proto) better?
dr|z3d
I mean on the banned routers page, you should have an indication of why the routers are banned. also, make sure you're on the latest update.
wew
see screenshot
wew
i'm on 8e338a4e build
dr|z3d
re static/final, reminds me of the question you asked a while back re var vs const. const in js is like final in java, can't be reassigned.
dr|z3d
ok, wew, further fixes will have to wait until after release, I'm not going to spend any more time until then chasing down the issue, disabling blocklists is super niche and unadvised. but thanks for bringing it to my attention. re reseeding, you can track that on /events, should be fixed now.
wew
thanks
dr|z3d
11 bans from a possible thousand or more ain't so bad, anyways. :)
wew
yep
dr|z3d
ok, answered my own question, `final` is redundant
Stormycloud
everytime I see drop.i2p it gets my engine going
dr|z3d
make sure said engine is well oiled, we don't want it failing :)
wew
=)
dr|z3d
wew: can you confirm you're no longer seeing spurious reseed events?
wew
0 yet
wew
well done
dr|z3d
how long's your router been up, roughly? multiple hours?
wew
4h
dr|z3d
ok, good.
wew
thank you
dr|z3d
no need to thank me, bugs need to die. thanks to you and others for bringing it to my attention.
wew
=)
dr|z3d
re Tixati, zzz, do we have an identifier yet so we can tag it in snark?
zzz
no, haven't seen in the wild, but the extension protocol for client name that we now support makes the hardcoded stuff redundant
dr|z3d
oh? didn't notice that.
zzz
if we can talk somebody into testing it then we can get on a swarm and see
dr|z3d
sounds like Sh0ck's our man :)
dr|z3d
*** tickles Sh0ck ***
dr|z3d
moe: please register your nick with nickserv for perma +V
zzz
from the libtorrent source, looks like the string is TIX, b64 would be VElY
dr|z3d
ok. but we don't need to explictly add that as a hard-coded value you're saying? or maybe tagging it as Tixati would be helpful?
dr|z3d
will add hard-coded value for now.
dr|z3d
else if ("VElY".equals(ch)) {client = "Tixati";}
zzz
it shouldn't be necessary, it would be a micro-optimization to avoid falling thru to the extension message
dr|z3d
yeah, but if the extension's returning "TIX", then Tixati is better, but maybe it returns "Tixati" .. I guess we'll find out when Sh0ck accepts the challenge.
zzz
no, extension returns a full name, not a code
dr|z3d
ok, thanks.
zzz
actually full name + version is what most do
dr|z3d
so the whole name and version extraction code can be tagged for removal?
dr|z3d
(we've got some hard-coded clients in there where we extract the version)\
zzz
it's a micro-optimization as I said, and also for those that don't do extensions (XD?)
dr|z3d
ok, got it.
zzz
seems like most clients do the belt+suspenders thing like we do, no particular need to rip it out
dr|z3d
roger that
uop23ip
reseed seems fixed. no reseed triggered. thanks, dr|z3d
dr|z3d
thanks for reporting back, uop23ip