@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16752
Irc2PGuest33667
Irc2PGuest51880
Irc2PGuest97218
Onn4l7h
Sisyphus
Sleepy_
Teeed
aargh2
ac9f_
b3t4f4c3__
b4dab00m
bak83_
duanin2
eyedeekay_
john231
leopold
makoto
nilbog-
not_bob_afk
poriori_
profetik1
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
tr
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
obscuratus
eyedeekay: Question about the blocklist configurable expire time... Is it the intended behavior to expire/skip the banning of specific router hashes from the blocklist.txt published in the news?
obscuratus
Whenever I enable a blocklist expire time, my router skips loading of the specifically banned routers in blocklist.txt
eyedeekay
No that's not the intended behavior, that sounds like a bug
eyedeekay
It is intended to expire those blocklist.txt bans though, is there any chance it's confused about the timing?
obscuratus
I'm still trying to sort through what's happening. Now that I know for sure that's not intended, I'll dig into why I'm seeing what I'm seeing.
dr|z3d
obscuratus: it's meant to expire bans, but not skip them entirely.
dr|z3d
I think the intended behavior is to expire bans and then reapply them if the router reappars on the radar, no, eyedeekay?
dr|z3d
if it's intended to expire bans entirely and release routers from the jail, that's probably not intended behavior. but what do I know?
obscuratus
dr|z3d: It's current behavior has some unexpected nuances. I'll keep you in the loop on what I sort out.
dr|z3d
thinking about it, and based on the commit notes, I think it's meant to expire bans for the sybil detection banlist that can extend over multiple router sessions. and thinking about it some more, I'm not entirely sure what we're trying to achieve here other than free up a nominal amount of memory used for storing the bans.
dr|z3d
ok, thanks, obscuratus
dr|z3d
for the most part, I'm happy banning routers in the throttlers if they're iffy.
dr|z3d
short term bans, not session-persistent, re-applied where apt.
obscuratus
I'm pretty sure this new feature is primarily intended for the places where we ban entire IP addresses.
dr|z3d
no doubt all will become clear in time :)
obscuratus
We currently don't have a mechanism for expiring them on the fly, but we usually lose them on restart.
dr|z3d
we have a mechanism for unbanning individual hashes.
dr|z3d
we also have a mechanism for setting the duration of sybil bans.
dr|z3d
but for feed ips, no, you're right, there's not much if any control.
dr|z3d
for manual control, the unban hash ui option could probably be extended to include ip addresses or ranges.
dr|z3d
(if that's desirable, which I'm not entirely sure it is)