Skip to content

Commit

Permalink
doc: Fix dead links
Browse files Browse the repository at this point in the history
  • Loading branch information
rg0now committed Oct 24, 2024
1 parent f677a94 commit 9d1583d
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -401,7 +401,7 @@ a heartwarming welcome message.
```

1. We also need a STUN/TURN client to actually initiate a connection. STUNner comes with a handy
STUN/TURN client called [`turncat`](cmd/turncat/README.md) for this purpose. Once
STUN/TURN client called [`turncat`](docs/cmd/turncat.md) for this purpose. Once
[installed](cmd/turncat/README.md#installation), you can fire up `turncat` to listen on the
standard input and send everything it receives to STUNner. Type any input and press Enter, and
you should see a nice greeting from your cluster!
Expand Down
2 changes: 1 addition & 1 deletion docs/examples/simple-tunnel/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The tutorial assumes a fresh STUNner installation; see the [STUNner installation

### Setup

In this tutorial we perform a quick Kubernetes/STUNner benchmark: we fire up an iperf server inside the cluster and perform a speed test from the local console. We will use the [`turncat`](../../cmd/turncat) client utility to tunnel test traffic to the iperf server via STUNner acting as a STUN/TURN gateway.
In this tutorial we perform a quick Kubernetes/STUNner benchmark: we fire up an iperf server inside the cluster and perform a speed test from the local console. We will use the [`turncat`](../../cmd/turncat.md) client utility to tunnel test traffic to the iperf server via STUNner acting as a STUN/TURN gateway.

![STUNner benchmarks setup](../../img/stunner_benchmark.svg)

Expand Down

0 comments on commit 9d1583d

Please sign in to comment.