~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens
+Irc2PGuest92669
+Xeha
+cumlord
+j6
+onon
+profetikla
+r00tobo
+snex
+uop23ip
An0nm0n
Arch
Danny
DeltaOreo
DiCEy1904
Irc2PGuest45008
Irc2PGuest68141
Irc2PGuest71319
Irc2PGuest91332
Irc2PGuest92810
Onn4l7h
acetone_
anon2
anontor
anu
bak83_
boonst
goose
itsjustme
mareki2pb
no
poriori_
qend-irc2p
shiver_
u5657
unwr
snex
(i2p+) i continue to have low peer counts for some reason... i tried banOldRouters=false, updating to various dev builds. sometimes i start off healthy but it always seems to degrade over time. i really dont understand this.. it seemed to only start happening a couple weeks ago when my external IP changed, but that could just be a red herring. i am using hostname-based resolving on my external IP so peers should...
snex
Blinded message
snex
is there some way to tell if peers are banning me and if so why?
snex
it could just be generic "network under attack" as i see tor doing similar stuff too but answers like this are never satisfactory.. WHAT is the nature of the attack? WHY cant we stop it?
dr|z3d
I think there might be an issue with snex's ddns hostname specified on /confignet, zzz. any ideas?
dr|z3d
Maybe there's a period where the hostname is pointing at a stale ip address, and that tanks his router connections.
dr|z3d
rebroadcast for snex (this is where you take over the conversation):
dr|z3d
> I think there might be an issue with snex's ddns hostname specified on /confignet, zzz. any ideas?
dr|z3d
> Maybe there's a period where the hostname is pointing at a stale ip address, and that tanks his router connections.
snex
the IP change happened like 2 weeks ago so i would hope any of that should be flushed out by now. im using traditional hosting where if i get an IP change i have to go manually update it but im able to do that within an hour of it happening
dr|z3d
I'd just use autodetect on /confignet and see if that resolves your issue.
dr|z3d
if you don't have UPnP enabled on the host, then opt for "Use SSU IP address detection only".
snex
the reason i switched off of that was because it catastrophically failed the prior time my IP changed. though that was quite a while back and iirc was i2p rather than i2p+. can try and see if it helps
dr|z3d
SSU detection relies on peers confirming that whatever ip your router things it has is valid.
dr|z3d
*thinks
snex
what about for the TCP config?
dr|z3d
if you're never firewalled, use auto-detect (not firewalled), otherwise just autodetect.
snex
ok
dr|z3d
might be safer to use the latter.