IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2025/06/20
@eyedeekay
&zzz
+R4SAS
+RN
+dr|z3d
+hagen
+hk
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
Arch
BubbRubb
Daddy
Daddy_1
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest41581
Irc2PGuest92548
Irc2PGuest95056
Irc2PGuest95323
Leopold
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SlippyJoe
StormyCloud_
T3s|4_
T3s|4__
Teeed
acetone_
ardu
b3t4f4c3___
bak83_
boonst
defaultnick
dr4wd3_
eyedeekay_bnc
guest7621
not_bob_afk
not_human
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
u5657
uop23ip
w8rabbit
x74a6
eyedeekay Forums back as of yesterday, will post a hypothetical schedule, next on my list is gitea/git lock issues and feedback on the remaining PR's then I can to go do go-i2p stuff in earnest for a little while I hope
zzz sounds good eyedeekay, just two PRs left, UDP announces and PQ Ratchet
eyedeekay Yup hopefully I should get to them in the next couple hours
eyedeekay At least 5-10 min from now lol
zzz did you and bigly fix his reseed yet?
eyedeekay No I haven't heard back on my email yet so I went digging in the reseed-tools code to try and find any differences in the way the IPv6 and IPv4 are handled. My going hypothesis is that the rate-limiter has some subtle IPv6 bug which is why I refactored the listeners and added all those unit tests last week
zzz ?? but the symptoms were it works on IPv6 but not on IPv4 ???
eyedeekay Other way around, isn't it? Works on IPv4 not on IPv6?
eyedeekay It's going to be the same system either way, that's the only place where any difference between IPv4 and IPv6 is handled
eyedeekay The actual listener is an "all available interfaces" listener on 0.0.0.0 and ::
zzz and since we essentially force IPv4 for reseeding since so many reseeds have broken IPv6 (maybe due to this problem, maybe not), it means his reseed is essentially down
zzz or at least it was last few times I tested, been a couple weeks
zzz email was May 28th
zzz but do your own testing, don't take my word for it
eyedeekay Yeah I replied and asked for feedback info because it's fairly mysterious to my why IPv6 would be different from IPv4 in this case. The only place I care about the diff is in the ratelimiter, so my immediate hypothesis is the reverse proxy or fail2ban, neither of which do I have a way to debug. I'll ping him again and ask for more feedback but I'm also going to make sure that I'm not doing something dumb
eyedeekay with the ratelimiter
eyedeekay *continue to make sure
zzz he's also one of two reseeds on a nonstandard port, if that makes a difference