Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Open sidebar
dms3
go-dms3
Commits
12bdb94f
Commit
12bdb94f
authored
Jul 05, 2017
by
Łukasz Magiera
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
docs: correct p2p command usage
License: MIT Signed-off-by:
Łukasz Magiera
<
magik6k@gmail.com
>
parent
0660f1c4
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
docs/experimental-features.md
docs/experimental-features.md
+4
-4
No files found.
docs/experimental-features.md
View file @
12bdb94f
...
...
@@ -202,11 +202,11 @@ P2P command needs to be enabled in config
Basic usage:
-
Open a listener on one node (node A)
`p2p listener open p2p-test /ip4/127.0.0.1/tcp/10101`
-
Connect your app to the endpoint opened locally (tcp on localhost port 10101)
`
ipfs
p2p listener open p2p-test /ip4/127.0.0.1/tcp/10101`
-
Where
`/ip4/127.0.0.1/tcp/10101`
put address of application you want to pass p2p connections to
-
On the other node, connect to the listener on node A
`ipfs
i 1
p2p stream dial $NODE_A_PEERID p2p-test /ip4/127.0.0.1/tcp/10102`
-
No
w connect the application on node B to its tcp endpoint, and they should now be communicating
`ipfs p2p stream dial $NODE_A_PEERID p2p-test /ip4/127.0.0.1/tcp/10102`
-
No
de B is now listening for a connection on TCP at 127.0.0.1:10102, connect your application there to complete the connection
### Road to being a real feature
-
[ ] Needs more people to use and report on how well it works / fits use cases
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment