Skip to content

Commit 0c0bd4d

Browse files
committed
Fix checks
1 parent 5357190 commit 0c0bd4d

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

  • services/tailscale-subnet-router-node

services/tailscale-subnet-router-node/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
This Docker Compose configuration sets up a Tailscale Subnet Router Node, allowing devices in your Tailscale network to route their traffic securely through this node to a local subnet. By configuring a Tailscale Router Node, you can extend your local network of device to tailscale connected clients, such as your home or office.
44

55
## Tailscale Subnet Router Node
6+
67
Subnet routers let you extend your Tailscale network (known as a tailnet) to include devices that don't or can't run the Tailscale client. They act as gateways between your tailnet and physical subnets, enabling secure access to legacy devices, entire networks, or services without installing Tailscale everywhere. This capability maintains Tailscale's security model while providing flexibility for complex network environments.
78

89
## Configuration Overview
@@ -14,3 +15,4 @@ In this setup, the `tailscale` service runs a Tailscale container configures it
1415
- **TS_EXTRA_ARGS**: The `--advertise-routes` flag is used to designate this container as a Subnet Router Node within your Tailscale network.
1516
- **Sysctls**: The system controls `net.ipv4.ip_forward` and `net.ipv6.conf.all.forwarding` are enabled to allow IP forwarding, which is necessary for routing traffic through the Exit Node.
1617
- **Network Mode**: The `bridge` network mode is used to create a virtual network interface for the container, enabling it to handle traffic routing.
18+

0 commit comments

Comments
 (0)