There is no access from the lan to the tailscale network due to userspace mode being used however, the socks proxy could be enabled to gain access from the lan into the tailnet. Two env variables are required, $args and the $authkey.įor args I use -accept-dns=false -accept-routes=false -advertise-exit-node -advertise-routes=172.17.0.0/16 The file needs to be copied into the official container and pushed to a repo or exported as a tar file for used on Mikrotik FROM ghcr.io/tailscale/tailscale:unstable Tailscale -socket=/tmp/tailscaled.sock up $args -authkey=$authkey Tailscaled -tun=userspace-networking -socket=/tmp/tailscaled.sock &> /dev/null &

Figured I’d also share what I came up with: One of the long awaited benefits of RouterOS version 7 is a new routing protocol stack that enables new capabilities and fixes limitations in RouterOSv6 caused by the use of a very old Linux kernel. 3.7 and support for all current architectures. RouterOS v7 will be a continuation of RouterOS v6 with a bumped 3.xx Kernel, e.g. With that container, all you need is an entrypoint file. This is pure speculation based on what Mikrotik have done in the past, but my bet is on a split release. I had previously used tailscale on kubernetes (fantastic by the way) and therefore used the official container instead of building from source. RouterOS version 7.1beta6 has been released in public 'development' channel Whats new in 7. Please let me know of any suggestions or feedback. Didn’t have to build my own if I would have looked here first Too late. As noted this is a development project that is based on RouterOS 7, currently in beta.

Routeros 7 beta