Sockets for communication between peers

[thelesbianguy]

Sockets for communication between peers

[Stebalien]

You mean between external applications (using IPFS)? We actually support this, checkout the ipfs p2p command.

[Stebalien]

Fair enough: https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#ipfs-p2p ("More documentation" is literally listed as a todo...).

As that documentation isn't very helpful:

On both nodes, you'll need to enable the feature (it's currently experimental):

> ipfs config --json Experimental.Libp2pStreamMounting true
> ... restart ipfs ...

On one of your IPFS nodes (NODEA)b, you'll need to register a listener. First, start your application and have it listen on YOUR_PORT. Then, run:

> ipfs p2p listener open /my/custom/protocol/name /ip4/127.0.0.1/tcp/YOUR_PORT

This will configure IPFS to listen for new streams speaking the protocol /my/custom/protocol/name and, for each new stream, proxy the stream to 127.0.0.1:YOUR_PORT.

Next, on the the other IPFS node, run

> ipfs p2p stream dial $NODEA_ID /my/custom/protocol/name /ip4/127.0.0.1/tcp/SOME_PORT

And connect your application to 127.0.0.1:SOME_PORT. The connection will be proxied through to the listener on the other node.

[Stebalien]

FYI, I've improved that documentation in: ipfs/kubo#4894

[thelesbianguy]

thanks a lot

…

On 29 March 2018 at 12:22, Steven Allen ***@***.***> wrote: FYI, I've improved that documentation in: ipfs/kubo#4894 <ipfs/kubo#4894> — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#290 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AkCuex891sTo6JmFS2CfgfvK1pD5kGkpks5tjIS1gaJpZM4S_wRP> .