[Q&A] some confusing points about TUN mode in the new version ab2f0ec

[ghcred]

前置确认

• 我已查阅 常见问题，但仍未找到解决方案
• 我已使用关键字查询相关 Issues，但仍未找到解决方案

使用的分支

master

Commit ID

ab2f0ec

Shell 环境

zsh

问题描述

[Q&A] some confusing points about TUN mode in the new version ab2f0ec

I recently upgraded to ab2f0ec from a version from about one year ago. There are a couple of unexpected things. I want to ask:

1. Assumptions

From what I understand mihomo has two modes, system-proxy and TUN. And it is recommended to only enable one mode and disable the other.

I have TUN mode on and system-proxy mode off.

2. TUN mode consistency questions

Suppose system-proxy is off and TUN is on. If I restart clash by first running clashoff and then running clashon, TUN mode will be off.

A similar case occurs for TUN mode, after running clashsub update. TUN mode is on before running the command but off after running it.

In the last version I used, TUN mode behaves consistently (always on when set so). In the latest version (ab2f0ec), it is not. Is this intended or a bug?

In daily use, I have to turn off and on TUN mode manually in order to have "Internet access". When clashstatus returns three processes (like in step 3 in the above screenshot), it works. And when clashstatus returns only one process (like in step 7 in the above screenshot), it doesn't work. Why?

3. Repetitive start-of-interactive-shell notifications potentially related to TUN mode

The script checks if http_proxy is empty. If it is, clashon is called.

It seems this logic only accounts for clashproxy mode, where http_proxy is non-empty; in clashtun mode, http_proxy is still empty, in which case I get the 已开启代理环境 notifications in every interactive shell session.

Is this intended or a bug?

[nelvko]

First of all, enable Tun mode needs root permission.
If run install.sh by regular user, the clashon will start the proxy kernel by nohup, not as a systemd unit, and the process havn't root permission.
If you want to enable Tun, the clashtun on have to stop the old process and restart a new one by sudo, so clashoff also need run with sudo to stop root's process.
That’s why 'Suppose system-proxy is off and TUN is on. If I restart clash by first running clashoff and then running clashon, TUN mode will be off.'.Cause you are a regular user, if you run install by root user, that's not going to happen.

In the old version, regular user can't enable Tun, so i improve it and cause that things.

[nelvko]

About what you said 'And it is recommended to only enable one mode and disable the other', i think it doesn't matter.
Enable Tun: Traffic is forced to be routed to the proxy kernel, whether the system proxy is set or not, it is ineffective.

[ghcred]

Thanks so much for the reply! Now I understand.

(all information is from commit 90764c6c6820)

A follow-up questions is: is there a recommended way to install the project with systemd?

The default in some older version was systemd; in the current version it is nohup. There's a _detect_init function in the code. Please consider clarifying this in READEME. It'll be really helpful.

You said "if you run install by root user, that's not going to happen". So I think you mean installing with systemd will ensure consistent TUN mode. To do that:

I tried sudo bash install.sh (from commit 90764c6c6820). It failed.

I edited .env and changed ~/clashctl to root/clashctl (I'm not sure about what ~ does in different situations), and then sudo bash install.sh. I got this.

So I tried again with chmod +x /root/clashctl/scripts/cmd/clashctl.sh. Things got messy, I can't provide further detail. In the end it didn't work.

[nelvko]

Avoid using sudo for installations if you're a regular user, it has a little problem. I tried to fix it and finally shelved it.
Now its installation logic is as follows:

• regular user or container environment: run with nohup.
• root user: run with service manager, e.g. systemd.

[ghcred]

Avoid using sudo for installations if you're a regular user, it has a little problem. I tried to fix it and finally shelved it. Now its installation logic is as follows:

• regular user or container environment: run with nohup.
• root user: run with service manager, e.g. systemd.

If customization is not recommended/tested, I think it's better to add a note for that.

Please consider, in the README file:

1. adding "avoid using sudo for installations if you're a regular user"
2. removing "可通过 .env 文件或脚本参数自定义安装选项。", or adding further details about INIT_TYPE

Thanks for the instruction!