IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2024/05/19
~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+Afkaid
+FreefallHeavens
+Unbur
+Xeha
+cumlord
+goose2_
+j6
+poriori
+profetikla
+r00tobo
+snex
+uop23ip
+weko
An0nm0n
Arch
Danny
DeltaOreo
DiCEy1904
Irc2PGuest11229
Irc2PGuest21326
Irc2PGuest48909
Irc2PGuest54864
Irc2PGuest71250
Nausicaa
Onn4l7h
acetone_
anon2
anontor
anu3
bak83
boonst
enoxa
fujifilm
goose2
itsjustme
mareki2pb
onon_1
qend-irc2p
shiver_
tr
u5657
user
veiledwizard
xen_NULL
T3s|4 o/ dr|z3d - minor nit, but afaict there were 4 iterations of 2.5.2-1+. The first had a build string of af906f2f, but the last 3 had a static string of b22cec82, despite the dates and build time changing. Ofc, now running -2+
dr|z3d hi T3s|4
dr|z3d yeah, not every build gets a version bump, standard. otherwise we'd be off the charts in very short time :)
dr|z3d also, if you're looking at /info for the revision, that only reflects the router.jar revision.
dr|z3d so it won't necessarily change with every update.
dr|z3d you'd need to look on /jars to see revisions for all jars and wars to identify what's changed (if not router.jar)
dr|z3d and occasionally with dev builds, the code may not have been committed, so the revision will stay the same even though there are updates.
dr|z3d (in this instance I was doing some work on the http server blocklist stuff before committing it)
T3s|4 gotcha dr|z3d, and thanks for the helpful explanation :D
dr|z3d anytime :)
dr|z3d and right on cue, another update just landed.
T3s|4_ dr|z3d: I noticed today you bumped skank, download to 2.5.2+ Installer* and Update. I was actually planning to remind you that 2.5.0 had been hanging about for a bit, but per normal, got crunched for time :D
StormyCloud Some changes made to stormycloud outproxy. Please let me know if you notice any issues.
Irc2PGuest7233 StormyCloud: what are the changes? are you logging everything for the fbi?
StormyCloud *pikachu face* how did you discover our secret so quick. Cant talk much about the changes, they are in response to the recent attacks on the I2P network so wanting to keep public information limited. Nothing has changed in terms of logging or what we monitor/restrict (which is nothing).
snex what if we just ask the attackers nicely to stop
snex i have high build success (92%) but it can take like an hour to get an eepsite :(
snex my snark cant hit postman tracker at all
snex people cant download the canary in the cage podcast!
snex do i just need to restart my i2p every day or something?
dr|z3d you haven't configured 0 hops and multiple tunnels for snark have you?
dr|z3d just stop and start the torrent in question, should resolve.
dr|z3d also try the latest + dev build re browsing.
snex its all of them
dr|z3d stop all, start all.
snex and the error is "no response from tracker2.postman.i2p"
dr|z3d and check /logs in console, see if there's anything there.
snex nothing in logs
dr|z3d yeah, usually a transient error, normally it'll fix itself, sometimes it needs a nudge.
snex well the other day i restarted i2p and that seemed to work. but now back in the same situation
snex this never happened before
dr|z3d might be postman testing new infrastructure, might have nothing to do with your router.
dr|z3d if you request a stale leaseset on a multihomed site, you can see that error.
dr|z3d so, stop all, start all.
dr|z3d people should still be able to download your torrent anyways, via DHT or opentrackers.
snex well they all have 0 peers
dr|z3d shouldn't need to restart router, just restart of torrents normally fixes. transient issue, anyways, so I wouldn't worry about it. will likely fix itself.
dr|z3d if you're using haproxy for web browsing, check that haproxy backend tunnels are functional.
dr|z3d forgot to ask the obvious question, snex. what version are you running?
snex 2.5.2+ on the i2p. snark standalone 2.5.0
snex 2.5.0+
dr|z3d issues with browsing is why 2.5.2 was pushed out. ok, 2.5.2+, good.
dr|z3d you may still wish to grab the latest update from skank, either dev or release path. some minor fixes there.
dr|z3d (assuming you grabbed the update from torrent)
snex the 2.5.2+ came from skank
snex release path
dr|z3d ok, well 2.5.2+ dev build is rock solid, also has the new http server blocklist feature you might want to test. up to you.
snex eta on it being officially released?
dr|z3d you mean the next official release?
snex whatever these changes are that might fix the issue, when will they be in a release build?
dr|z3d not entirely convinced there are fixes relating to your issue per se, but the next "official" release is mid-July afaik.
snex is there some amount of torrents that might be causing it? like would postman tracker be rate limiting?
dr|z3d in any event, you should have _at least_ the skank release update path active in +. you can configure it to notify only. anything that addresses a possible bug will get an out-of-band release.
snex other sites seem to work
dr|z3d yeah, postman will likely be rate-limiting.
dr|z3d for likely read definitely.
dr|z3d I've never experienced more than transient errors with postman's tracker, but I'm not hosting 1000s of torrents.
snex i only have 23
dr|z3d you shouldn't be rate limited then.
snex well even if i was, the website would still work because thats 2 different tunnels right? and also other sites seem to take many many tries to load if they load at all
snex if im having problems with all eepsites then the problem would have to be in my router, not snark or tracker2
dr|z3d sure, likely. try an update via the update mechanism, either release or dev. I recommend dev, but up to you.
snex i should already be on the latest release one
dr|z3d did you download via the in-console update mechanism?
snex no, i did eepget skank.i2p/i2pupdate.zip from cli
dr|z3d Blinded message
dr|z3d >>> in any event, you should have _at least_ the skank release update path active in +. you can configure it to notify only. anything that addresses a possible bug will get an out-of-band release.
snex the in-console has literally never worked
dr|z3d you have to enable development updates otherwise it will continue to literally not work :)
snex it never worked no matter what i enabled
snex we went over this last time. thats when you showed me how to do it via cli
dr|z3d yeah, but that's not a tenable long term solution. you want the console to notify you when an update is available.
dr|z3d try again, it will work sooner or later. enable development updates, save, set policy to notify only, save. then hit check for updates, using either dev or release path.
snex "Unable to connect to news server dn3tva...b32.i2p"
snex whats weird is that when i finally DO get something to work, it stays working for a while
dr|z3d ignore that, that's a separate non+ issue.
snex like irc here...
snex its like im being flooded with fake tunnels or something
dr|z3d have you got sybil defenses enabled?
dr|z3d you want automatic blocking for floodfills at least.
snex i have automatic blocking, every 60m
dr|z3d that's currently blocking a bunch of those 2.5.1 routers that are floating around.
dr|z3d ok, that's fine then.
dr|z3d floodfill enabled?
snex i doubt it.., this is a single board ARM
snex i definitely did not try to force floodfill on
uop23ip Hi orignal , i am trying to build a static i2pd on arm64 and got an error at the last end.
uop23ip [100%] Linking CXX executable i2pd
uop23ip collect2: error: ld returned 1 exit status
uop23ip make[2]: *** [CMakeFiles/i2pd.dir/build.make:203: i2pd] Error 1
uop23ip make[1]: *** [CMakeFiles/Makefile2:169: CMakeFiles/i2pd.dir/all] Error 2
uop23ip make: *** [Makefile:136: all] Error 2