@cryptotaxi247 / kubo / commits / 12bdb94f6

docs: correct p2p command usage

License: MIT Signed-off-by: Łukasz Magiera <magik6k@gmail.com>

Łukasz Magiera committed Jul 5, 2017 at 18:32 UTC 12bdb94f65d145e110b8c9d1e96e3a8d012661c0
1 file changed +4 -4
docs/experimental-features.md
+4 -4
@@ -202,11 +202,11 @@ P2P command needs to be enabled in config
202 Basic usage:
203
204 - Open a listener on one node (node A)
205 -`p2p listener open p2p-test /ip4/127.0.0.1/tcp/10101`
206 -- Connect your app to the endpoint opened locally (tcp on localhost port 10101)
205 +`ipfs p2p listener open p2p-test /ip4/127.0.0.1/tcp/10101`
206 +- Where `/ip4/127.0.0.1/tcp/10101` put address of application you want to pass p2p connections to
207 - On the other node, connect to the listener on node A
208 -`ipfsi 1 p2p stream dial $NODE_A_PEERID p2p-test /ip4/127.0.0.1/tcp/10102`
209 -- Now connect the application on node B to its tcp endpoint, and they should now be communicating
208 +`ipfs p2p stream dial $NODE_A_PEERID p2p-test /ip4/127.0.0.1/tcp/10102`
209 +- Node B is now listening for a connection on TCP at 127.0.0.1:10102, connect your application there to complete the connection
210
211 ### Road to being a real feature
212 - [ ] Needs more people to use and report on how well it works / fits use cases