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

Fix auto-transport creation for vpn-client #1211

Closed
ersonp opened this issue May 19, 2022 · 0 comments
Closed

Fix auto-transport creation for vpn-client #1211

ersonp opened this issue May 19, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@ersonp
Copy link
Contributor

ersonp commented May 19, 2022 •
edited
Loading

Describe the bug
Currently if a vpn-server is available on sudph, stcpr and dmsg the auto-transport logic creates transport for both sudph and stcpr but uses stcpr for the connection.

Environment information:
vpn-server

  • OS: e.g. Linux
  • Platform: Linux 5.12.14-arch1-1 x86_64

vpn-client

  • OS: e.g. Linux
  • Platform: Linux 5.13.0-41-generic x86_64

Steps to Reproduce
Steps to reproduce the behavior:

  1. Start Visor A with public IP and start vpn-server.
  2. Start Visor B with public IP.
  3. Connect vpn-client of visor B to the vpn-server of visor A.
  4. Check the transports in the UI.

Actual behavior
image
@ersonp ersonp added the bug Something isn't working label May 19, 2022
@mrpalide mrpalide mentioned this issue Jun 3, 2022
Merged
@mrpalide mrpalide closed this as completed Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ersonp @mrpalide