Opicaak
What's the file limit on i2p's gitlab? I can't upload the pictures.
eyedeekay
Let me check, pretty sure you should have headroom though...
eyedeekay
Max attachment size is 10md
eyedeekay
*mb
eyedeekay
Lots of disk space
Opicaak
OK, had to do a little bit of compression. Those 3 pictures is all I managed to get from this person.
eche|off
interesting attack, looks liek syn/ack issues on TCP on my server
eche|off
trying to flood with false connects
Opicaak
Hello, zzz, do you have a private b32 for the stats page?
eche|off
thats the same as stats.i2p
eche|off
no other address does exist
Opicaak
I see, okay, thank you.
Opicaak
Has the network issue been identified yet?
eche|off
some attacks going on
Opicaak
I've noticed that it does work fine for a few minutes, then it finds a malicious node, the Routers and Floodfills skyrocket with other malicious nodes, and I can no longer access anything.
Opicaak
The success rate goes down to about 2% rapidly.
zzz
stats.i2p is down atm and may be up/down throughout the day
Opicaak
Thank you
dr|z3d
new reseeder has cert issues: Error reseeding (Unknown signer: root@bungee.systems for content type: reseed)
zzz
rename the cert file
dr|z3d
I renamed the cert file to root_at_bungee.systems.crt and, that was the error I got after.
dr|z3d
Host: lapras.bungee.systems
dr|z3d
Failure: Unknown signer: root@bungee.systems for content type: reseed
eyedeekay
seems to be working for me having changed the name to: root_at_bungee.systems.crt and placing it in ~/i2p/certificates/reseed/root_at_bungee.systems.crt
zzz
worked for me dr|z3d as I reported on my forum
dr|z3d
ok, maybe the certs get read in a startup and changing the name of a cert requires a restart?
zzz
welcome new reseed volunteer UDP, everybody say hi
UDP
Hey there
UDP
how's everyone
dr|z3d
as if by magic, UDP appears. sup UDP. just talking about your service earlier.
UDP
oh? were you? :p
dr|z3d
just cert filename issue. nothing exciting :)
UDP
oh gotcha, hope nothing was broken in the server info package I sent
dr|z3d
apparently it's all working fine.
zzz
ok so it was the rename issue dr|z3d ?
UDP
glad to hear I set it up ok :) been a tor relay operator for a few years now and it's been nice to learn something new for a change
dr|z3d
I'll know when I restart the router in question zzz. I think in my case it's a restart thing, given I'd already renamed by the time you suggested it.
zzz
just try the cli
dr|z3d
I'm guessing if a cert is read and it's the wrongly named, that association persists until restart. and I also tried the cli.
dr|z3d
(several times)
dr|z3d
that's where the last paste came from, the cli..
zzz
hmm
dr|z3d
just so we're clear, cert has been renamed to: root_at_bungee.systems.crt
dr|z3d
reseed in console with incorrect cert name, then cert renamed, then reseed attempts from console and cli.
dr|z3d
so, as I said, I suspect the original wrongly named cert has been associated and a restart will fix. if it's working for you, then no big deal.
zzz
there's obviously no "persistence" in the cli, new JVM each time
UDP
did a certain character in the filename cause the issue or was it something else?
dr|z3d
the su3_ prefix.
UDP
ah yeah, I added that to differentiate it while I was testing but forgot to remove it. sorry for the inconvenience.
UDP
will keep that in mind if there are any future certificate changes
dr|z3d
no worries, UDP
dr|z3d
might be something about the CLI tool that's misfiring, zzz.
dr|z3d
here's the full output for bungee.systems..
dr|z3d
Host: lapras.bungee.systems
dr|z3d
Failure: Unknown signer: root@bungee.systems for content type: reseed
dr|z3d
Version: 1675699266 (06-Feb-2023 16:01)
dr|z3d
Signer: root@bungee.systems
dr|z3d
SigType: RSA_SHA512_4096
dr|z3d
Content: RESEED
dr|z3d
FileType: ZIP