-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tun Support #3576
Comments
dup |
This comment was marked as off-topic.
This comment was marked as off-topic.
Use transproxies. TUN is less performant than transparent proxies anyway, unless you need to also handle packets other than TCP and UDP. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
我觉得主要是 Windows 和 macOS 需要 Tun,Linux 上不如透明代理,话说 macOS 上有透明代理吗 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
这里似乎已经变成许愿井了 issue区不是干这个的。。。 |
Can we use this dependency? |
@omid-official I think GPL is not right to add to xray. There is some GPL code in xray, but it is historical, and the author themselves added it. (otherwise, I am sure adding some dependencies to xray for this feature is fine) |
This comment was marked as off-topic.
This comment was marked as off-topic.
I am a novice regarding licenses and do not know what terms and conditions each of them has, but as mmmray mentioned, the GPL license has stricter rules compared to the MPL license. |
Please stop that. We will not use it |
I think TUN is really good and practical( not only for Win or MacOS, for all platforms ), and at least for the following reason, it needs to be added: TUN can cover all network traffic, including traffic from non-browser software, apps, and various protocols. Additionally, you can block WebRTC STUN later to prevent the exposure of the real IP! |
Hello
Desktop clients needs Xray-core to support Tun
Do you have any plan to support it?
The text was updated successfully, but these errors were encountered: