tailscale: Tailscaled fails to start when IPv6 policy routing is unavailable
Hi,
Description
Since updating tailscale to version 1.2.1, it seems it does not create the socket in /var/run/tailscale/tailscaled.sock. The systemd service is indeed started but tailscale itself cannot connect or be brought up.
What happens
Tailscale service is running but /usr/bin/tailscale cannot connect
What should happen
Update should not break existing configuration
Steps to reproduce
Update tailscale through sudo apt update; sudo apt upgrade
Technical details
OS - Debian stable :
<font color="#E9AD0C">admin</font>@lovelace:<font color="#2AA1B3">[~]</font>: cat /etc/debian_version 10.6
Tailscale Version:
<font color="#E9AD0C">admin</font>@lovelace:<font color="#2AA1B3">[~]</font>: tailscale --version 1.2.1 tailscale commit: 9446e5c170fb251b83d3e1d14b319991c32f4135 other commit: 351e0990591be7c5f6631cca09c68ac264671404-dirty go version: go1.15-tsc333f7a
Kernel Version:
<font color="#E9AD0C">admin</font>@lovelace:<font color="#2AA1B3">[~]</font>: uname -a Linux lovelace 4.4.114-mainline-rev1 #1 SMP Thu Feb 1 16:16:01 UTC 2018 x86_64 GNU/Linux
Systemd service status:
<font color="#E9AD0C">admin</font>@lovelace:<font color="#2AA1B3">[~]</font>: sudo systemctl status tailscaled.service
<font color="#26A269">●</font> tailscaled.service - Tailscale node agent
Loaded: loaded (/lib/systemd/system/tailscaled.service; enabled; vendor preset: enabled)
Active: <font color="#26A269">active (running)</font> since Wed 2020-11-04 16:48:24 UTC; 933ms ago
Docs: https://tailscale.com/kb/
Main PID: 27057 (tailscaled)
Tasks: 9 (limit: 2389)
Memory: 9.6M
CGroup: /system.slice/tailscaled.service
└─27057 /usr/sbin/tailscaled --state=/var/lib/tailscale/tailscaled.state --socket=/run/tailscale/tailscaled.sock --port 41641
Nov 04 16:48:24 lovelace tailscaled[27057]: router: dns: using dns.resolvconfManager
Nov 04 16:48:24 lovelace tailscaled[27057]: Bringing wireguard device up...
Nov 04 16:48:24 lovelace tailscaled[27057]: Bringing router up...
Nov 04 16:48:24 lovelace tailscaled[27057]: Device closing
Nov 04 16:48:24 lovelace tailscaled[27057]: Routine: event worker - stopped
Nov 04 16:48:24 lovelace tailscaled[27057]: [RATE LIMITED] %s
Nov 04 16:48:24 lovelace tailscaled[27057]: wgengine.New: running "ip -6 rule add pref 5210 fwmark 0x80000 table main" failed: exit status 2
Nov 04 16:48:24 lovelace tailscaled[27057]: RTNETLINK answers: Address family not supported by protocol
Nov 04 16:48:24 lovelace tailscaled[27057]: flushing log.
Nov 04 16:48:24 lovelace tailscaled[27057]: logger closing down
tailscale error:
<font color="#E9AD0C">admin</font>@lovelace:<font color="#2AA1B3">[~]</font>: tailscale up Failed to connect to connect to tailscaled. (safesocket.Connect: dial unix /var/run/tailscale/tailscaled.sock: connect: no such file or directory)
Mitigations tried
I tried to reinstall, purge and reinstall to no avail.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 29 (11 by maintainers)
Commits related to this issue
- wgengine/router: disable IPv6 if v6 policy routing is unavailable. Fixes #895. Signed-off-by: David Anderson <danderson@tailscale.com> — committed to tailscale/tailscale by danderson 4 years ago
- wgengine/router: disable IPv6 if v6 policy routing is unavailable. Fixes #895. Signed-off-by: David Anderson <danderson@tailscale.com> — committed to tailscale/tailscale by danderson 4 years ago
- wgengine/router: disable IPv6 if v6 policy routing is unavailable. Fixes #895. Signed-off-by: David Anderson <danderson@tailscale.com> — committed to tailscale/tailscale by danderson 4 years ago
- wgengine/router: disable IPv6 if v6 policy routing is unavailable. Fixes #895. Signed-off-by: David Anderson <danderson@tailscale.com> (cherry picked from commit a664aac877c46f4f8778a19a0673725c525e... — committed to tailscale/tailscale by danderson 4 years ago
Hi, I have a slightly similar error upon launching Tailscale.
Following the steps above, I am running Tailscale (formerly on 1.2.2, then upgraded to 1.3.46 following this thread), on an Ubuntu 18.04 machine that has to deal with a HTTP proxy (it is configured, I am able to curl http and https). IPv6 is disabled.
error
nvidia-lmr@nvidia-lmr:~$ sudo tailscale up 2020/11/13 16:20:08 ReadMsg: read unix @->/run/tailscale/tailscaled.sock: use of closed network connectionStatus of the service :
`
And the journal state after
sudo tailscale up:The weird thing, is that I am able to curl https://login.tailscale.com/key from the cmd line.
Tailscale netcheck
I am investigating my proxy configuration, but as internet connection is working fine (curl, apt-get …) apart from Tailscale, I am not sure what I could try now.
Released 1.2.6 with this fix. You should be fine to switch back to the stable track now (once you’ve switched back to the stable repo URL,
apt-get install tailscale=1.2.6should switch you over, if I remember my incantations correctly)Yeah, you have a different problem, which is that the tuntap device driver isn’t loaded. Based on:
you may need to reboot, because there is a tuntap driver on disk, but for the wrong kernel version. Usually that means the kernel package got updated, but you haven’t rebooted yet so the modules don’t match.
I just pushed unstable packages to https://pkgs.tailscale.com/unstable. Can y’all give that a try and see if it fixes things?