Go-ipfs: Can I manually add address?

Created on 30 Mar 2017  路  2Comments  路  Source: ipfs/go-ipfs

Is it possible to add manually peers before starting ipfs daemon
And how I can get value from second machine to add it on first machine?

And for example I have run a daemon in local network on several devices, and then I give access to global network would files accessible to others people. If yes, how can I prevent it?

Most helpful comment

Is it possible to add manually peers before starting ipfs daemon

Use the Bootstrap list to add peers before starting in the configuration.

And how I can get value from second machine to add it on first machine?

Use ipfs id to find the second machine's peer addresses.

And for example I have run a daemon in local network on several devices, and then I give access to global
network would files accessible to others people. If yes, how can I prevent it?

Files are accessible to other people as soon as a node bootstraps to one of the default nodes or finds a node which is connected to the outside.

If yes, how can I prevent it?

Enable private networks. See https://github.com/ipfs/go-ipfs/issues/3397#issuecomment-284341649

All 2 comments

Is it possible to add manually peers before starting ipfs daemon

Use the Bootstrap list to add peers before starting in the configuration.

And how I can get value from second machine to add it on first machine?

Use ipfs id to find the second machine's peer addresses.

And for example I have run a daemon in local network on several devices, and then I give access to global
network would files accessible to others people. If yes, how can I prevent it?

Files are accessible to other people as soon as a node bootstraps to one of the default nodes or finds a node which is connected to the outside.

If yes, how can I prevent it?

Enable private networks. See https://github.com/ipfs/go-ipfs/issues/3397#issuecomment-284341649

@hsanjuan Thanks, it useful enough!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

emelleme picture emelleme  路  3Comments

0x6431346e picture 0x6431346e  路  3Comments

ArcticLampyrid picture ArcticLampyrid  路  3Comments

whyrusleeping picture whyrusleeping  路  4Comments

funkyfuture picture funkyfuture  路  3Comments