~dr|z3d
@RN
@RN_
@Stormycloud
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%ardu
%cumlord
%mareki2p
%snex
+FreefallHeavens
+HowardPlayzOfAdmin
+Onn4l7h
+Onn4|7h
+Xeha
+poriori
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
Arch
BubbRubb
C341
Danny
DeltaOreo
FreeB
Irc2PGuest18171
Irc2PGuest54725
Irc2PGuest57893
Liorar_
Meow
T3s|4__
acetone_
carried6590
halloy13412
maylay
moe_
not_bob_afk
pisslord
r00tobo[2]
shaye
shiver_
simprelay
solidx66
thetia
u5657
weko_
wew-
woodwose
zer0bitz_
uop23ip
tried to get to the release version by putting the release i2pupdate.zip into folder. it rejects it and i am still on dev .16 ;)
dr|z3d
I don't think that's an issue with +, uop23ip, could just be transient network issues.
dr|z3d
same with you, cumlord. probably matrix glitch.
dr|z3d
the low transit and low known peers sounds like local networking issues.
dr|z3d
what you might try is a reseed followed by a router restart, uop23ip.
cumlord
Maybe, I’ll try again at some point older snark standalones no problem
dr|z3d
running the latest standalone here, connecting to peers isn't an issue. an older client that only supports ElGamal will be a problem, since new snark now supports ECIES/MLKEM.
dr|z3d
that said, pretty sure it's been 4 for a while now, so 6,4 shouldn't present any issues. famous last words.
dr|z3d
cumlord: snark -> crypto is why you're not being able to talk to some clients. try setting encType=4 in the i2cp configs for snark and restarting.
dr|z3d
actually, that should be i2cp.leaseSetEncType=4