~dr|z3d
@RN
@T3s|4
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%cumlord
+DirtyHarry
+FreefallHeavens
+Xeha
+ardu
+bak83_
+mareki2p
+onon_
+profetikla
+r00tobo
+uop23ip
AHOH
Arch2
Danny
DeltaOreo
FreeB
Irc2PGuest59581
Irc2PGuest70083
Irc2PGuest70134
Irc2PGuest96449
Irc2PGuest97049
Meow
Onn4l7h
Onn4|7h
acetone_
altonen
boonst
carried6590
duck
evasiveStillness
maylay
not_bob_afk
phobos_
pisslord
poriori_
qend-irc2p
radakayot_
shiver_1
simprelay
solidx66
thetia
u5657
weko_
zer0bitz
dr|z3d
where are you putting the router.config files, StormyCloud? And when?
dr|z3d
essentially, when you start the router for the first time, it will create a new router.config file in ~/.i2p/ and that's when you need to edit the router.config file or copy over your template file.
zzz
not sure if the 'deployment package' is for $I2P only or includes .i2p -- if you don't have a config dir yet, it will copy over anything from $I2P/router.config if present, which it usually is not
zzz
but if you have a ~.i2p/router.config already, it won't
zzz
or even just a ~/.i2p at all might be enough to prevent the first-install logic from happening
zzz
obviously the deployment package contained a .i2p dir with an identity, which really isn't safe to do it that way
dr|z3d
yeah, that's what I thought, and then I noticed we don't have a router.config file in i2p/
zzz
just have a $I2P dir with the default settings you want in a router.config file in there.
dr|z3d
so drop the router.config file in i2p/ and all's good, then, StormyCloud
zzz
correct, it isn't normally there, but if it is there we'll migrate it to the config dir, so you can do stuff like this safely
dr|z3d
ok, noted.
zzz
no drz. if you want a 'deployment package' thats the right way to do it, with a default router.config in there
dr|z3d
I say all's good, StormyCloud, but you'd drop the router.config file in i2p/ _before_ you run for the first time. :)
zzz
just don't include a .i2p dir at all in the package, let the first-install logic do its thing
dr|z3d
yup, yup, got it.
zzz
you don't need to remove $I2P/router.config, the only time we look at it is on first install
zzz
* first run
zzz
so you can put your port 7777 in there, for example
dr|z3d
if I had the energy, I'd probably code up a webui to create a custom deployment setup with default configs, tunnels etc. maybe someone else has the energy? :)
dr|z3d
or maybe an export settings from /configadvanced would be sufficient, where it adds the rebuildKeys config to the existing router.config, strips all the crud, and then presents a router.config file.
zzz
there's a hundred ways to do it, the flaw here was not checking that it worked
dr|z3d
true, true.
zzz
maybe, but I don't think there's any way to anticipate the requirements of a custom deployer and then write a packager
zzz
does he want an existing netdb to avoid reseeding? profiles? addressbook?
dr|z3d
I was thinking just the router.config file, not the full 9 yards.
zzz
yeah, but even then
StormyCloud
Tbf this is how my last deployment was done but I did not double check so that’s on me. I get home in 30mins so I can give the general workflow but something is missing the mark.
zzz
no need for a post-mortem StormyCloud. just do your thing
zzz
looks like he got about half of them rekeyed, half still to go, good job
StormyCloud
Yeah very annoyingly you have to remove them from the family before rekeying them. Adds extra steps
zzz
yeah that sounds right, do you have an error you hit if you don't? perhaps we can fix that
StormyCloud
No error the router ID just wont change no matter how many times you put the rebuild in the config file. Figured that out after trying it more times then I care to admit lol
dr|z3d
is that just for a single router?
zzz
hmm
StormyCloud
Tried with two different routers, same results.
StormyCloud
Ill have the other half finished today.
zzz
not sure why but will look into it. sorry for your troubles.
dr|z3d
so two different routers refuse to be rekeyed with the config, what about the others?
StormyCloud
No troubles, borked deployment is on me.
dr|z3d
just curious if most of the rekeys went fine, helps us narrow down the scope of the issue.
StormyCloud
After 2 failed I just went with plan b of leaving family, rekeying, rejoining family. I can try to push the change to the other 15 routers and see if fails on all of them.
dr|z3d
ok, so rekeying works, but only after you've left the family?
StormyCloud
correct
dr|z3d
so that's maybe where we could improve the rekeying routines.. zzz?
dr|z3d
I wonder if we can do a one-stop-shop on rekey.. leave family, rekey router, reimport family key.
zzz
the question is why does a family prevent a rekey
zzz
no clues after a quick skim of the startup code, so I'll put it on the list to look into it
zzz
your IPv6 seems a little janky, your routers can't decide if they have it or not, but perhaps that will settle out in time
zzz
tested rebuild, everything seems fine from here
zzz
set a family and restarted
zzz
then added router.rebuildKeys=true to advanced config and restarted again
zzz
got in wrapper log:
zzz
Removing old identity file: router.info
zzz
Removing old identity file: router.keys.dat
zzz
Removing old identity file: keyBackup/privateEncryption.key
zzz
Removing old identity file: keyBackup/publicEncryption.key
zzz
Removing old identity file: keyBackup/privateSigning.key
zzz
Removing old identity file: keyBackup/publicSigning.key
zzz
got in event log: New router identity xxxxx
dr|z3d
makes me think there could be a permissions issue on some of the files it wants to remove.
zzz
verified new identity on /netdb local router page
zzz
verified RI has family on local router page
zzz
we log that in wrapper log:
zzz
System.out.println("ERROR: Could not remove old identity file: " + _rebuildFiles[i]);
zzz
the only thing I see is we should be removing the ssu2tokens file on rebuild, but that wouldn't cause a rekey failure
zzz
only other theory is it's a plus bug, but I don't know why you'd be dinking around in that code
StormyCloud
I finished getting new ID for all 30 routers, Ill give them 24 hours to settle down and see what we end up with
StormyCloud
Ill work on troubleshooting what went wrong in the deployment process so this doesnt happen again
StormyCloud
someone wanted me to mention that wiki.i2p-projekt.i2p is down. I guess that is an echelon project.
dr|z3d
yeah, pretty sure I haven't been dinking around there.
orignal
<borat_> orignal, не знаю что за атака, но пацаны с музыкалки уже прознали шедевр InviZible PRO ? а я им ещё про фдроид рассказал , думаю теперь их андроиды тож будут в i2pd работать
orignal
zzz
orignal
that's the answer about "tm botnet" ))
orignal
<borat_> вот зырьте как i2pd работает
orignal
<borat_> cake.i2p/file/Dk5AAV6x4w_ZnCX3aAiX9qwCxkQawmjYSCtMZclke_cqIWAEJyXY/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%B2%202025-04-30%2022-34-36.png
orignal
<borat_> нет, i2pd прямым линком работает в туркменистане счас скину эксклюзив ,скрин как работает i2pd напрямую -главная страница роутера
dr|z3d
can you summarize for us, orignal?
dr|z3d
no worries, I see the conversation in -dev