Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Patch v2ray-core to allow non-inbound configures. #1

Open
Yaspee opened this issue May 6, 2018 · 2 comments
Open

Patch v2ray-core to allow non-inbound configures. #1

Yaspee opened this issue May 6, 2018 · 2 comments

Comments

@Yaspee
Copy link

Yaspee commented May 6, 2018 •
edited
Loading

As the title is, v2ray-core must accept a legal inbound configure to start, but waVingOcean is already an "inbound".

And v2ray-core may not plan to have tun2ray as an inbound soon.

v2ray/Planning#1
@Yaspee Yaspee changed the title Patch v2ray-core to allow non-inbound configure. Patch v2ray-core to allow non-inbound configures. May 7, 2018
@TanNang
Copy link

TanNang commented Jul 24, 2018

@Yaspee

You can modify these lines:

https://github.com/v2ray/ext/blob/d65cd8c6a68851f6624f89edb77f6e77c6203590/tools/conf/v2ray.go#L468

@xiaokangwang
Copy link
Owner

xiaokangwang commented Jul 29, 2018 •
edited
Loading

I would like to recommend you to include an alternative inbound such as socks5 to workaround this issue.

Since V2Ray-core is changing so rapidly, I believe patching is not an ideal solution for long term.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xiaokangwang @Yaspee @TanNang