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.

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

Sing-box TUN choosing wrong adapter to connect #2107

Open
4 of 5 tasks
somebodywashere opened this issue Sep 13, 2024 · 1 comment
Open
4 of 5 tasks

Sing-box TUN choosing wrong adapter to connect #2107

somebodywashere opened this issue Sep 13, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@somebodywashere
Copy link

somebodywashere commented Sep 13, 2024

Operating system

Windows

System version

10

Installation type

Third-party graphical clients that advertise themselves as using sing-box (Windows)

If you are using a graphical client, please provide the version of the client.

NekoRay fork v4.1.4 by Mahdi-zarei, this issue was always persisted even in older "original" versions

Version

No response

Description

Sing-box TUN decision on what adapter to chose to connect is based ONLY on interface metric rather than checking metric and if adapter has Connected state.

Screenshot3995

Here router will chose adapter at index 12 or 15 (just lowest metric), rather than 7 (lowest metric for adapter with Connected state).

Reproduction

Windows sometime choose strange metrics and this leads to that. You can tune metrics manually and test.

Logs

No response

Supporter

Integrity requirements

  • I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
  • I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
  • I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
  • I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.
@nekohasekai nekohasekai added the bug Something isn't working label Sep 14, 2024
@nekohasekai
Copy link
Member

Try b3eddc9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants