mirror of
https://github.com/netbirdio/docs.git
synced 2026-04-20 01:16:36 +00:00
Fix about NetBird images
This commit is contained in:
@@ -24,7 +24,7 @@ It can be a Linux server running in the cloud or on-premises, a personal laptop,
|
|||||||
With NetBird clients installed and authorized on the Management service, machines form a mesh network connecting to each other directly via an encrypted point-to-point Wireguard tunnel.
|
With NetBird clients installed and authorized on the Management service, machines form a mesh network connecting to each other directly via an encrypted point-to-point Wireguard tunnel.
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<img src="/docs-static/img/architecture/mesh.png" alt="high-level-dia" style={{boxShadow: '0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19)'}}/>
|
<img src="/docs-static/img/architecture/mesh.png" alt="high-level-dia" className="imagewrapper"/>
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
While it is possible to create a full mesh network, it might be not a desirable outcome. In this case, [ACLs](/how-to/manage-network-access) can be utilized to limit the access to certain machines.
|
While it is possible to create a full mesh network, it might be not a desirable outcome. In this case, [ACLs](/how-to/manage-network-access) can be utilized to limit the access to certain machines.
|
||||||
@@ -54,7 +54,7 @@ After that, they are able to establish a connection to the new peer.
|
|||||||
The Management service runs in the cloud NetBird-managed. It can also be self-hosted.
|
The Management service runs in the cloud NetBird-managed. It can also be self-hosted.
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<img src="/docs-static/img/architecture/management.png" alt="management-dia" style={{boxShadow: '0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19)'}}/>
|
<img src="/docs-static/img/architecture/management.png" alt="management-dia" className="imagewrapper"/>
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
### Client Application
|
### Client Application
|
||||||
@@ -88,7 +88,7 @@ The only Signal's responsibility is:
|
|||||||
This is done through Signal. After a connection has been established, Signal steps out.
|
This is done through Signal. After a connection has been established, Signal steps out.
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<img src="/docs-static/img/architecture/signal.png" alt="signal-dia" style={{boxShadow: '0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19)'}}/>
|
<img src="/docs-static/img/architecture/signal.png" alt="signal-dia" className="imagewrapper"/>
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<Note>
|
<Note>
|
||||||
@@ -105,7 +105,7 @@ In fact, we use an open-source implementation called [Coturn](https://github.com
|
|||||||
The purpose of this service is to be a "plan B" and relay traffic between peers in case a peer-to-peer connection isn't possible.
|
The purpose of this service is to be a "plan B" and relay traffic between peers in case a peer-to-peer connection isn't possible.
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<img src="/docs-static/img/architecture/relay.png" alt="relay-dia" style={{boxShadow: '0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19)'}}/>
|
<img src="/docs-static/img/architecture/relay.png" alt="relay-dia" className="imagewrapper"/>
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<Note>
|
<Note>
|
||||||
|
|||||||
Reference in New Issue
Block a user