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

2x yggstack -socks 127.0.0.1:1080 -autoconf do not fail. The second should fail to bind #16

Open
lostmsu opened this issue Jan 31, 2025 · 3 comments
Open

2x yggstack -socks 127.0.0.1:1080 -autoconf do not fail. The second should fail to bind #16

lostmsu opened this issue Jan 31, 2025 · 3 comments

Comments

@lostmsu
Copy link

lostmsu commented Jan 31, 2025

Second instance of yggstack with the same socks parameter must fail because the socket address is already taken, and the behavior of the proxy from this point on seems undefined.
@basilgello
Copy link
Collaborator

Good catch! Let me try to reproduce it. Which platform do you run yggstack on?

@lostmsu
Copy link
Author

lostmsu commented Feb 6, 2025

I am on Windows

@basilgello
Copy link
Collaborator

Looks the culprit is go ListenAndServe without any error handling.

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
2 participants
@lostmsu @basilgello