Compare commits
2 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| 57df037137 | |||
|
315fd630e3
|
+1
-2
@@ -166,8 +166,7 @@ RUN mkdir -p /out/usrlocalbin && \
|
||||
# overlayfs single-copy property). `exec` keeps tailscaled as PID 1.
|
||||
RUN printf '%s\n' \
|
||||
'#!/bin/sh' \
|
||||
'# Enable IPv4/IPv6 forwarding (best-effort; sysctls are writable inside' \
|
||||
'# a RouterOS container netns). Required for advertised subnet routes and' \
|
||||
'# Enable IPv4/IPv6 forwarding. Required for advertised subnet routes and' \
|
||||
'# exit-node functionality.' \
|
||||
'for f in /proc/sys/net/ipv4/ip_forward /proc/sys/net/ipv6/conf/all/forwarding; do' \
|
||||
' if [ -w "$f" ]; then echo 1 > "$f" 2>/dev/null || echo "warn: could not write $f"; fi' \
|
||||
|
||||
@@ -120,12 +120,6 @@ The node now appears in your Tailscale admin console. Approve the advertised
|
||||
routes / exit node there. Because the auth state is written to the persisted
|
||||
`tailscaled.state`, you only do this once — it survives reboots and updates.
|
||||
|
||||
> **IP forwarding** (IPv4 and IPv6) is enabled automatically by the container's
|
||||
> entrypoint, so advertised subnet routes and exit-node traffic work without any
|
||||
> extra `sysctl`/`/container` configuration. (IPv6 forwarding in particular is
|
||||
> not reliably enabled by `tailscaled` itself inside a container network
|
||||
> namespace, so the entrypoint sets it explicitly.)
|
||||
|
||||
### 6. Enable automatic updates
|
||||
|
||||
First, edit the `CONFIG` block at the top of `routeros/update-tailscale.rsc` if
|
||||
|
||||
Reference in New Issue
Block a user