adam/ipfs-blog
1
0
Fork 0
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-08-11 03:12:47 +02:00
Code Issues Packages Projects Releases Wiki Activity

src/_blog: Link to ipfs glossary

Browse Source
This commit is contained in:
Max Inden
2022-01-27 14:58:54 +01:00
parent 9d92fc39c3
commit a78d5ddeb5
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/_blog/libp2p-hole-punching.md
+1 -1
View File
@@ -23,7 +23,7 @@ Computers in today's Internet can be divided into two groups, public and non-pub
Let's look at an example. Two computers, *A* and *B*, each in their own network, connected to the internet via a separate home router each, with those home routers acting as firewalls.
Note that we are focusing on overcoming firewalls today and ignore NATs for now. The process described below (hole punching in libp2p) enables overcoming both. For the sake of simplicity we will concentrate on firewalls in this blog post.
Note that we are focusing on overcoming firewalls today and ignore [NATs](https://docs.ipfs.io/concepts/glossary#nat) for now. The process described below (hole punching in libp2p) enables overcoming both. For the sake of simplicity we will concentrate on firewalls in this blog post.
![img](../assets/libp2p-hole-punching-network.svg)