Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Diagram map:

## L1 context and L3 components

This diagram shows culvert as one box and what it talks to.
Clients tunnel into culvert, which routes their traffic to the site networks.

```mermaid
flowchart LR
Expand Down Expand Up @@ -53,7 +53,7 @@ flowchart LR

*Figure 1. L1 Context -- Culvert. Dashed boxes are external, and dotted arrows are opt-in.* Up: top of culvert. Down: [L3 Components -- Culvert](#l1-context-and-l3-components).

This diagram shows the processes inside the container.
stunnel fronts OpenVPN and wstunnel fronts WireGuard.

```mermaid
flowchart LR
Expand Down Expand Up @@ -137,7 +137,7 @@ drops a compiler toolchain from the image at no cost to the capability.
in a focused module under `scripts/lib/`, and the entrypoint's job is the
order.

This diagram shows the startup steps as three stages.
Network and firewall come up before either VPN.

```mermaid
flowchart TB
Expand Down
2 changes: 1 addition & 1 deletion docs/use-case-edge-fleet.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ It is gated: the CIDRs in `CULVERT_DOWNSTREAM_ADMIN_CIDRS` are the sources
allowed to initiate inbound. Everything else unsolicited into the tunnels is
dropped.

This diagram shows the two flows through culvert in an edge fleet.
In an edge fleet, data flows up from the appliances to the receiver, and admin traffic flows down from the admin networks to the appliances.

```mermaid
flowchart TB
Expand Down
Loading