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

BUG: "Bypass Process Name" doesn't work on Linux V2.0 #1575

Open
PeaceByPeace opened this issue Jan 5, 2025 · 2 comments
Open

BUG: "Bypass Process Name" doesn't work on Linux V2.0 #1575

PeaceByPeace opened this issue Jan 5, 2025 · 2 comments

Comments

@PeaceByPeace
Copy link

PeaceByPeace commented Jan 5, 2025

Just wanted to recreate issue, maybe first one was obsolete but it still persists no matter what you are putting in process name (full path or just name itself) even in logs nothing is happening (although processes themselves are being recorded in logs) with process itself it's just there but no message regarding it's work. Program just detects an app but do nothing with it!!! On windows everything works as expected. Have somebody managed to fix an issue, may be there's some sort of custom config or something?

@sub-kek
Copy link

sub-kek commented Jan 5, 2025

Same problem #1574

@PeaceByPeace
Copy link
Author

That's truly interesting: I tried different client: v2rayN and faced the same issue on linux))) And then, out of curiosity, I compared sing-box-vpn.json config for windows and for linux and they actually differs in one json key. On windows there's no mentioning of process_name but on linux there it is (on windows and linux there's config file with all your processes listed, that's why I don't get why sing-box config differs). I don't understand why the same version of sing-box core has different implementation in linux and windows since this json is only wrapper for underlying mechanisms. Then I tried to delete this key from config and see what will happen. Spoiler allert: it changed nothing... which is strange. Maybe someone could explain why?

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

No branches or pull requests

2 participants