Release 2.8.0-0 broke SAM v3 application

[sovereign]

I have written an application that uses the libsam3 library (https://github.com/i2p/i2psam).
The application was working fine until the I2P v 2.8.0-0 release was installed. (It had been working fine since I deployed the app on release 2.3.0-0 and it worked fine up until 2.8.0-0)

To verify I removed the 2.8.0-0 and reinstalled v 2.7.0-0 and the application worked fine.

I'll try to narrow down why 2.8.0-0 broke the SAM v3 app and report back my findings.

Until then, if anyone has any ideas as to what might be the problem, please let me know.

[anikey]

What do you mean by "broke"? Does it give an error? Or does i2p router crash?

Also, you should check the Logs in your i2p web console.

[sovereign]

The router doesn't crash.
The app doesn't report an error, it just hangs.
I do see the connection establish successfully with the SAM bridge.

I'm testing now with a simple test app for SAM messaging with debug info to stdout.
In the test app I see:

Send: HELLO VERSION MIN=3.0 MAX=3.1

Reply: HELLO REPLY RESULT=OK VERSION=3.1

Reply: STREAM STATUS RESULT=OK

The issue appears when the test app writes the message out it hangs.

The app on the other side (hidden service socket) shows it receives a connection, but doesn't receive the message being sent.

The same code base works on a 2.7.0 router but not on a 2..8.0 router.

I'll keep investigating.

[anikey]

After some testing, I notice that communication between two SAM sessions on the same I2P router does not work.

I think you should notify the developers of I2P.

[sovereign]

I noticed the SAM communications did not work at all on a machine running a wireguard client VPN connection with release 2.8.0. The SAM communications worked fine on the same machine running a wireguard client VPN connection on release 2.7.0.

When I turned off the wireguard client VPN connection then restarted the I2P 2.8.0 router, the SAM communications completed successfully after a very long time 6-10 minutes (unacceptible).

I have started investigating and compiling documentation that I will maintain at: http://sovereign.i2p/sam-issue.html

I'll look to submit a bug report.

[anikey]

Tried it with two different routers? If it works that way, this is probably a known issue: http://zzz.i2p/topics/3669-cannot-reach ... e-on-2-8-0

[sovereign]

Yes I tried it with two different routers on two different machines. After the 2.8.0 update SAM stopped working for me. That's how I originally discovered the issue.

[zzz]

Yup, apologies for the "loopback" bug, we are planning a 2.8.1 release to fix it.

The workaround is in the zzz.i2p post linked above, and the information is also in your console news.

If it doesn't work when talking between two different machines, that's something different. But running i2p over wireguard is not recommended and probably won't work well.