You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New users to IPFS typically expect to be able to add some data to IPFS on their local machine and then fetch it through the IPFS Gateway, or from a Pinning Service.
If the user's local machine is behind a NAT, another machine can't fetch the data.
Dialback Protocol
One solution is for the publicly available node to request a "dialback" from the NATed node. Once the NATed node connects directly to the public node, the public node can fetch the data from the NATed node through this connection.
During a DHT query, each node reports its nearest neighbours - the NATed node should be connected to its nearest neighbours in the DHT. In order to request a dialback, the public node can find a neighbour to the NATed node and ask the neighbour to pass the dialback request to the NATed node. Participating nodes' peer records should indicate that they support the dialback protocol.
The text was updated successfully, but these errors were encountered:
Background
New users to IPFS typically expect to be able to add some data to IPFS on their local machine and then fetch it through the IPFS Gateway, or from a Pinning Service.
If the user's local machine is behind a NAT, another machine can't fetch the data.
Dialback Protocol
One solution is for the publicly available node to request a "dialback" from the NATed node. Once the NATed node connects directly to the public node, the public node can fetch the data from the NATed node through this connection.
During a DHT query, each node reports its nearest neighbours - the NATed node should be connected to its nearest neighbours in the DHT. In order to request a dialback, the public node can find a neighbour to the NATed node and ask the neighbour to pass the dialback request to the NATed node. Participating nodes' peer records should indicate that they support the dialback protocol.
The text was updated successfully, but these errors were encountered: