I create a private network. two bootstrap nodes S1, S2 have the public IP addresses, set RelayServer enabled two nodes A1, A2 in the local network behind NAT, set RelayClient enabled two nodes B1, B2 in another local network behind NAT, set RelayClient enabled All these nodes set up the same s…

yes, bootstrap nodes S1 and S2 using public facing IP address, and 4001 port allowed

In the following thread, while trying to help someone with a similar issue, I discovered that relay v2 does not support the use of swarm keys: [image] How to setup V1 Relay in the new config IPFS Hmmm, so the issue is that relay v2 doesn’t support the use of swarm keys. W…

Thank a lot for your reply @ylempereur :grin: This does look bad. I use ipfs/kubo as a library to develop based on ipfs applications, which makes the use of similar applications more restrictive. NAT configuration | IPFS Docs Fix common connection issues by managing your routers NAT …

The real solution is to use the main net instead of a private net (so, no swarm keys, and a lot more nodes available), and encrypt your data end-to-end, in effect creating a private network within the main net

Yes, I now plan to replace the private network with asymmetric encryption with “age” and then use a public node as a bootstrap node. I’ll test it later to see how it works

I removed the swarm.key file for all nodes and restart ipfs daemon With the ipfs id command, I can get the address of each node, including the relay address However, it is still not possible to get the files of other nodes through IPFS From the logs, it seems that the node does not actively go t…

when run ipfs swarm peers the node behind NAT circuit address showed, but can not cat file > ipfs swarm peers zeta@MacBook-Pro /ip4/1.14.102.…

Connecting using a relay v2 is a two step process. First, it connects through the relay itself and communicates using that connection for simple things (low bandwidth). Second, if it wants to use bitswap (to exchange blocks), it tries to connect directly using hole punching, and then uses that conne…

Thanks a lot ! @ylempereur :grin: As you said, the nodes behind NAT communicate very unstable, when I use ipfs mainnet, nodes behind different NATs can occasionally exchange data with each other, but it is very unstable and sometimes disconnects during communication. It would be exciting if this …

I sovled it , when I add 4 public ip bootstrap nodes ,it works!

Private network p2p-circuit swarm connect success, but ipfs cat not work!

Help

ylempereur December 9, 2022, 6:12pm 4

In the following thread, while trying to help someone with a similar issue, I discovered that relay v2 does not support the use of swarm keys:

Topic		Replies	Views
Need help! IPFS Swarm connect failure between two networks Help	24	3156	January 25, 2021
How to setup V1 Relay in the new config Help go-ipfs , bitswap	104	4688	April 5, 2024
IPFS Circuit relay connected to node under NAT but cant access files Help	0	57	June 14, 2024
How to connect a peer with an external IP address go-ipfs	59	900	July 9, 2024
Can i make a private ipfs network (of public/external ip's) ? This would require my own gateway as well? Help go-ipfs	16	7324	June 17, 2019

Private network p2p-circuit swarm connect success, but ipfs cat not work!

Related topics