Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

start tailscaled with error on version 1.66.4.1 and v1.66.4.0 #28

Open
dorom741 opened this issue Aug 10, 2024 · 1 comment
Open

start tailscaled with error on version 1.66.4.1 and v1.66.4.0 #28

dorom741 opened this issue Aug 10, 2024 · 1 comment

Comments

@dorom741
Copy link

dorom741 commented Aug 10, 2024

start tailscaled with error on version 1.66.4.1 and v1.66.4.0
this is the log:

2024/08/10 13:45:58 logtail started
2024/08/10 13:45:58 Program starting: v1.66.4-dev20240606-tcdb051cf1, Go 1.22.3: []string{"/data/adb/tailscale/bin/tailscaled", "-verbose=0", "-outbound-http-proxy-listen=localhost:1099", "-socks5-server=localhost:1099", "-tun=tailscale0", "-statedir=/data/adb/tailscale/tmp/", "-state=/data/adb/tailscale/tmp/tailscaled.state", "-socket=/data/adb/tailscale/tmp/tailscaled.sock", "-port=41641"}
2024/08/10 13:45:58 LogID: a9acfa7aff2a7387e3b89687417c67f8f31c4b827f2be7e2e534f3160d26ab1d
2024/08/10 13:45:58 logpolicy: using UserCacheDir, "/data/adb/tailscale/tmp/.cache/Tailscale"
2024/08/10 13:45:58 dns: [rc=unknown ret=direct]
2024/08/10 13:45:58 dns: using "direct" mode
2024/08/10 13:45:58 dns: using *dns.directManager
2024/08/10 13:45:58 linuxfw: clear iptables: multiple errors:
        deleting [-j ts-input] in filter/INPUT: running [/system/bin/iptables -t filter -D INPUT -j ts-input --wait]: exit status 2: iptables v1.6.1: Couldn't find target `ts-input'

Try `iptables -h' or 'iptables --help' for more information.

        deleting [-j ts-forward] in filter/FORWARD: running [/system/bin/iptables -t filter -D FORWARD -j ts-forward --wait]: exit status 2: iptables v1.6.1: Couldn't find target `ts-forward'

Try `iptables -h' or 'iptables --help' for more information.

        deleting [-j ts-postrouting] in nat/POSTROUTING: running [/system/bin/iptables -t nat -D POSTROUTING -j ts-postrouting --wait]: exit status 2: iptables v1.6.1: Couldn't find target `ts-postrouting'

Try `iptables -h' or 'iptables --help' for more information.
2024/08/10 13:45:59 linuxfw: clear ip6tables: multiple errors:
        deleting [-j ts-input] in filter/INPUT: running [/system/bin/ip6tables -t filter -D INPUT -j ts-input --wait]: exit status 2: ip6tables v1.6.1: Couldn't find target `ts-input'

Try `ip6tables -h' or 'ip6tables --help' for more information.

        deleting [-j ts-forward] in filter/FORWARD: running [/system/bin/ip6tables -t filter -D FORWARD -j ts-forward --wait]: exit status 2: ip6tables v1.6.1: Couldn't find target `ts-forward'

Try `ip6tables -h' or 'ip6tables --help' for more information.
2024/08/10 13:45:59 cleanup: list tables: netlink receive: invalid argument
2024/08/10 13:45:59 wgengine.NewUserspaceEngine(tun "tailscale0") ...
2024/08/10 13:45:59 Linux kernel version: 3.18.71-perf-g4a0ef96
2024/08/10 13:45:59 is CONFIG_TUN enabled in your kernel? `modprobe tun` failed with:
2024/08/10 13:45:59 wgengine.NewUserspaceEngine(tun "tailscale0") error: tstun.New("tailscale0"): CreateTUN("tailscale0") failed; /dev/net/tun does not exist
2024/08/10 13:45:59 flushing log.
2024/08/10 13:45:59 logger closing down
2024/08/10 13:45:59 getLocalBackend error: createEngine: tstun.New("tailscale0"): CreateTUN("tailscale0") failed; /dev/net/tun does not exist

May need to ignore errors during cleanup phase and automatically fall back to just using userspace-networking when tun is unavailable.
By the way,Some devices the tun file in /dev/tun instead of /dev/net/tun, which may need to be handled.

@NewbieLegit
Copy link

NewbieLegit commented Dec 30, 2024

As a temporary solution, it could be solved with making symlink in /dev/net/tun to /dev/tun,

mkdir /dev/net
ln -s /dev/tun /dev/net/tun

changes in /dev won't persist after reboot, so you will need to make boot script for this

However, adding the hotfix on module would be much better

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants