Appears to be fixed from here.
* Trying 127.0.0.1:4444...
* Connected to 127.0.0.1 (127.0.0.1) port 4444
> GET http://i2p-projekt.i2p/hosts.txt HTTP/1.1
> Host: i2p-projekt.i2p
> User-Agent:…
Did set some config options which were shown as solving the issue, and did resatart apache2.
Thanks for the update.
re: item 1, I will investigate.
re: item 2, yes. From the SAM spec:
Each registered I2P Destination is uniquely associated with a session ID (or nickname). Session…
On a hunch, I changed my SESSION ADD command to not include the FROM_PORT parameter and now it works! I had been putting in the port number of the socket where the sub-session stream was going…
The connect side was very simple:
HELLO VERSION MIN=3.3
SESSION CREATE STYLE=PRIMARY ID=P23 DESTINATION=TRANSIENT
SESSION ADD STYLE=STREAM ID=S23 FROM_PORT=nnnn
then on…
Thanks. Last questions, since you didn't say and didn't provide the connect-side logs:
In the STREAM CONNECT, did you specify a TO_PORT that matches the FROM_PORT of the accept side? If not,…
My software writes a log file that captures all requests and replies. I have included both versions.evidence-456.log
Please provide the exact sequence of SAM commands, including port numbers, for both the working case and the failed case.
Aha - I have a saved older copy of the spec that lacks that paragraph.
- Had discussion with OP on IRC re: how ports work
- Added reset of i2p socket if no subsession found, in rev above, to be 2.3.0-8
- Added subsection about how I2CP ports work to spec
- Confirmed…
Good news, I reproduced both your passing and failing test cases here with telnet, and verified things work with the correct ports specified. Yes, our I2CP port documentation is poor, and yes,…
Using the old code, I modified the CONNECT request to include TO_PORT with the same value and it fails differently in that no replay comes back for the CONNECT - it never connects?
S…
This has been reverted already in the course of some of the other reversions. Closing.