-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encrypted lease set reliably crashes i2pd (server) instance #2124
Comments
i2cp.dontPublishLeaseSet = true Also try to remove i2p.streaming.maxOutboundSpeed and i2p.streaming.maxInboundSpeed . |
Good question. The docs do not explain the context very much for this option, so I did not know it was not meant to be used for servers: https://i2pd.readthedocs.io/en/latest/user-guide/tunnels/#signature-types I have only a very beginner's knowledge of lease sets. I was trying to follow #2104 and it looks like I mixed up client vs server for this option. I will try making those changes and see if it does not crash. |
Does it crash on high load or always? |
Thank you for your comments. I removed The crash happened always. |
See PurpleI2P/i2pd_docs_en#101 for context. I wanted to set up an encrypted lease set, but when making the connection from client to server it ended up crashing i2pd with:
Floating point exception (core dumped)
I compiled with compiler hardening enabled.
Here is what my tunnels.conf looked like:
server:
client (machine 2):
This will always crash the server i2pd. Version 3c608ec
Also, the client gets a lot of "incoming tags". Sometimes it was small (like 26). Sometimes large (3000 or more). Is this expected? The "Tags sessions" was small, like 1.
Whether you have encrypted leases or not it still crashes. With its regular b32 address after removing the encrypted lease settings I was able to send some packets and get a response before it crashed.
The crash still happens with hardening off when compiling.
The crash still happens on release 2.54.0.
OS: Ubuntu 22.04.5 LTS
The text was updated successfully, but these errors were encountered: