SAM 3.3 support?

[gdborton]

👋 I'm hacking on a torrent client that utilizes i2p. I'm trying to embed a binary and was originally looking at using i2pd as the client, but realized that it doesn't support datagram/raw subsessions.

My understanding is that this is a hard requirement for a torrent client to successfully utilize the DHT over i2p.

Is 3.3 support planned? (or has this support been landed since I looked last?)

It's not a blocker for me as I've switched over to emissary, but figured I'd check in anyway.

[orignal]

Please provide an example of app using SAM 3.3.
It's partially supported, just no app to test with.

[gdborton]

The app that I'm working on isn't open yet, but it's using 3.3 against emissary. I've hit some rough edges there as well so primarily built against i2p java to make sure I have the implementation right.

I'll throw up a sample when/if I get the sam bindings that I've been hacking on published.

In the meantime, I'm working on a bittorrent client which uses:

• streaming for sending chunks to/from peers
• datagram/raw sessions for DHT

My understanding is that we need a shared session for all three of these protocols to work over SAM w/ the same destination.

I'd originally tried i2cp, but switched to sam as I don't think I got the sliding window right for streaming.

[gdborton]

When writing my client, I created an integration test that:

• creates two destinations w/ a primary session each
• creates subsessions for stream/raw/datagram
• sends data between them on various ports

[orignal]

Can you please a provide python(or whatever langauge) script doing your test?

[gdborton]

I've pushed up the repo that contains the failing tests.

The suite is here:
https://github.com/gdborton/i2p-client/blob/b3def5fd706e1da79164dd0e5c24b6f90d039470/integration/sam.test.ts#L43

I believe the first issue is the i2pd still uses MASTER instead of PRIMARY for subsessions. Even hardcoding that though the integration test suite fails when run against i2pd.

Sending the SESSION CREATE command for the primary session here:
https://github.com/gdborton/i2p-client/blob/b3def5fd706e1da79164dd0e5c24b6f90d039470/sam.ts#L280

If you've got node installed, you can run the test suite with:

npm install;
npm test sam.test.ts

There's still a lot of clean up to be done, which I'll be working on tonight.

[orignal]

I believe the first issue is the i2pd still uses MASTER instead of PRIMARY for subsessions.

And i2pd will use MASTER when SAM 3.3. will be done, because how it was in the original specs.
If someone wanted to change change MASTER to PRIMARY without discussion, he would had to call it SAM 3.4 or whatever.

[gdborton]

Yeah that's fine, I'm not trying to rehash whatever decisions were made there.

I'm ok to use either so long as I can get it working w/ as many router implementations as possible.