#saltr (irc2p) | I2P+ 2.10.0-11+ >> i2pplus.github.io | skank.i2p | git.skank.i2p | purokishi.i2p | vituperative.github.io/i2pchat | notbob.i2p | ramble.i2p | drop.i2p | shinobi.i2p | wall.i2p | /msg an op for voice

cumlord snark rpc updater script that starts new torrents and stops any above share ratio git.simp.i2p/simp/SnarkUpdater/src/branch/main/snark_updater.py

cumlord it probably works

RN does the api use both of those pors? or are you using it for more than one snark?

RN *ports

cumlord for many snarks just to show it’s a list

RN gotcha.

orignal sorry

T3s|4 dr|z3d: just for kicks, I am trying an in-console update. Ater 80 minutes, I just passed the 50% completion mark

dr|z3d \o/ T3s|4

T3s|4 dr|z3d: update, 6

T3s|4 dr|z3d: update, *it never completed :D

T3s|4 fwiw: that was an attempt from 35b54ab1 (Build date: 2025-10-17 08:08:08 UTC)

T3s|4 trying to get the latest from 18 Oct

cumlord anything in the newest builds that would cause ratelimiting to be more aggressive?

cumlord it's possible my stuffs just getting attacked again but lot of weird timeout issues going on

cumlord yup opentracker keeps getting pinged to 429 and gets stuck like that once it gets near 20k peers

T3s|4 cumlord: I'm waiting for dr|z3d to re-appear. I have similar concerns re: timeout issues that were not present in earlier releases

cumlord seems more like bug than attack from what i can tell, some routers running multihome are on older release and not doing the same thing

cumlord yeah lot of weird things, with tunnel build failures maybe from timeout, sort of seemed like when that happened cpu usage would go high, loopback was giving me some problems where might've caused the server tunnel to fail, not really sure

T3s|4 cumlord: might prove useful / actionable evidence if you can capture the disparities :)

cumlord know he's been doing a lot of stuff though, the price of progress lol

T3s|4 yeah, ofc

cumlord ngl i went into panic mode because i thought certain routers were under attack

cumlord i'll look for logs later when i change my underwear

T3s|4 *** pukes at that site ***

T3s|4 *** pukes at that *sight :D ***

T3s|4 cumlord: dr|z3d is back; fire away!

cumlord lmao i didn't notice he was gone that whole time i thought you meant he was afk

cumlord anything in the newest builds that would cause ratelimiting to be more aggressive?it's possible my stuffs just getting attacked again but lot of weird timeout issues going onyup opentracker keeps getting pinged to 429 and gets stuck like that once it gets near 20k peers

cumlord seems more like bug than attack from what i can tell, some routers running multihome are on older release and not doing the same thing

cumlord *** goes to eat a taco ***

T3s|4 lols cumlord - enjoy your taco, especially if NOT from Taco Hell (tm). dr|z3d has vaporized (yet again) = perhaps ^related? :)

T3s|4 dr|z3d: did you see this?

dr|z3d ?

T3s|4 16:08:45 %cumlord | lmao i didn't notice he was gone that whole time i thought you meant he was afk │+Sh0ck

T3s|4 16:09:40 %cumlord | anything in the newest builds that would cause ratelimiting to be more aggressive?it's │+uop23ip

T3s|4 | possible my stuffs just getting attacked again but lot of weird timeout issues going │+waffles

T3s|4 | onyup opentracker keeps getting pinged to 429 and gets stuck like that once it gets near│+Xeha

T3s|4 | 20k peers │+xHarr

T3s|4 16:10:09 %cumlord | seems more like bug than attack from what i can tell, some routers running multihome are│ ac9f

T3s|4 | on older release and not doing the same thin%cumlord | anything in the newest builds that would cause ratelimiting to be more aggressive?it's │+Sh0ck

T3s|4 | possible my stuffs just getting attacked again but lot of weird timeout issues going │+uop23ip

T3s|4 | onyup opentracker keeps getting pinged to 429 and gets stuck like that once it gets near│+waffles

T3s|4 | 20k peers │+Xeha

T3s|4 | possible my stuffs just getting attacked again but lot of weird timeout issues goingg

dr|z3d didn't see it, thanks.

dr|z3d yeah, some possible weird stuff happening in the latest build, cumlord, working through the issues as we speak.

dr|z3d otoh, cumlord, you may just be hitting default stream limits for your zzzot tunnel if you haven't set those explicitly.

dr|z3d in your zzzot i2ptunnel.config, you want something like:

dr|z3d tunnel.0.option.i2p.streaming.maxConcurrentStreams=4096

dr|z3d tunnel.0.option.i2p.streaming.maxConnsPerHour=0

dr|z3d tunnel.0.option.i2p.streaming.maxConnsPerMinute=0

dr|z3d tunnel.0.option.i2p.streaming.maxTotalConnsPerHour=0

dr|z3d tunnel.0.option.i2p.streaming.maxTotalConnsPerMinute=0

dr|z3d adjust to taste.

T3s|4 dr|z3d: anything of late that could have adversely impacted IRC connection timeout values? Been seeing much longer (including up to 1-2 hours) post re-start for initial IRC connection, and far more frequent IRC disconnections and much longer 'automatic' re-connection times than previously on weechat. None of these issues are present while concurrently using weechat to connect to

T3s|4 libera.chat

cumlord lol thanks T3s|4

cumlord i've raised those a couple times, it wasn't just zzzot that it was just the first one that i noticed because peers suddenly were down to 3k and that's not right

T3s|4_ lols cumlord T3s|4 cannot hear you ATM, because he's been involuntarily disconnected (again) ;p

cumlord lmao this is what i get for switching clients

T3s|4_ OMG, T3s|4__ can hear you for the past 20 s (or so)

T3s|4 dr|z3d: hopefully, the first time you seen this:

T3s|4 dr|z3d: anything of late that could have adversely impacted IRC connection timeout values? Been seeing much longer (including up to 1-2 hours) post re-start for initial IRC connection, and far more frequent IRC disconnections and much longer 'automatic' re-connection times than previously on weechat. None of these issues are present while concurrently using weechat to connect to

T3s|4 libera.chat

cumlord jic: i've raised those a couple times, it wasn't just zzzot that it was just the first one that i noticed because peers suddenly were down to 3k and that's not right

T3s|4 there was at least a 20 second lag between seeing my last ^post here, and that same post showing up on another #salr rig. Is that related to a larger 'newish' build problem?

T3s|4 another * #saltr rig

cumlord the ones that were running newest build were getting it on a couple different server tunnels, though those ones have much lower limits than opentracker

T3s|4 Now there is a 1+ minute delay between posting here, and it showing up on my other. I checked and both rigs are connected to echelon's IRC server ATM

T3s|4 other *rig

T3s|4 yet another disconnect for T3s|4_ ;(

dr|z3d re peer count, will be lower than previously, should top out at around 4-5K with some uptime if floodfill, more robust ban handling implemented.

dr|z3d as for irc latency, will look into it. working through some issues here in my workspace.