discuss I2P

ChangeLog wrote: ## [2.57.0] - 2025-06-02
### Added

• Local domain sockets for I2PControl
• "keys=shareddest" tunnel param to run on shared local destination
• HTTP and SOCKS proxy through BOB
• Localization to Hebrew and Hindi
• NTCP2 probing resistance
• Support SAM v1 datagram sessions without port
• OpenIndiana support

### Changed

• Don't request LeaseSet until I2CP destination is ready
• Keep receiving new data from I2PTunnel/SAM socket while previous is being sent to stream
• Insert phony record to inbound tunnel build message with real x25519 ephemeral key
• Set min peer test version to 0.9.62
• Increase I2NP message expiration timeout in SSU2
• Cleanup ECIESx25519 new session reply keys on Alice side
• Reduced router profile persist interval to 22 minutes
• SSU2 max padding size to 32 bytes
• Send SSU2 path challenge of 8 bytes. Add datetime and address blocks
• Don't delete trusted routers from netdb
• Disable loss-control in streaming
• Reseeds list

### Fixed

• Crash after SAM stream disconnect
• FORWARD session host handling in SAM
• x86 build for Haiku
• SSU2 session's remote endpoint after receiving path response

Ready-to-use downloads for various systems are available as usual at the following address: https://github.com/PurpleI2P/i2pd/releases/tag/2.57.0

Thanks for the info, lgillis.
I updated some of the I2Pd routers. I was confused when I received the "503 Service Unavailable" message for a while, but after a good hour of operation, it's working fine.
I can sleep easy.
Sincerely.

You're welcome, colleague.

The code 503 is an http server message, as I tried to explain in another post.^1 But I don't understand the connection between your update of I2Pd and this code. Can you explain this briefly?

^1: 503 Service Unavailable - what does this mean?

step to reproduce
test web service served by router I2Pd 2.56.0 before update -> OK
stop the router I2Pd 2.56.0 gracefully
update the I2Pd router to 2.57.0
start and wait for good integration (usually 15-30 minutes)
test web service served by router I2Pd 2.57.0 -> 503 Service unavailable
test the same web service at the same time with another I2Pd router in 2.56.0 -> OK
test the same web service at the same time with another I2P Java router in 2.8.2.0-1 -> OK

I assume that the 503 error comes from the router in 2.57.0, although the success rate of tunnel creation is 40%

And after a good hour of waiting, it finally works. Since it works, everything's fine, it's just that the start after the update is frankly longer than before and it can give the impression that it doesn't work at all. Hence the importance of being patient

COMiX wrote: ↑Fri Jun 06, 2025 9:30 am I assume that the 503 error comes from the router in 2.57.0, although the success rate of tunnel creation is 40%

Let me know if you find the corresponding place in the source code.

COMiX wrote: ↑Fri Jun 06, 2025 9:30 am Hence the importance of being patient

Good advice! I think, I'll read a bit of science-fiction now and end the day in peace.

Without even going to search in the code, the concern comes from Server Tunnels, which seems to have difficulty associating the identifier with the local service. It reminds me of a DNS looking to solve the name of the local machines by looking for them first outside the LAN, before searching locally

I'll see if it happens again after each restart, or if it was just because of the update.

Am I the only one getting errors running the tests after the compilation?

(The errors are fixed in a later git version, before or in version i2pd_2.57.0-10-g46154dab.)

i had some difficulty with restarts and socketfiles with i2pd before, if you're using those

I2Pd version 2.57 is not working properly with postman tracker in qbittorrent.
developers should take note.