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

Under WSl2 environment, client-2 started failed #2

Open
zjb1001 opened this issue Jan 30, 2024 · 2 comments
Open

Under WSl2 environment, client-2 started failed #2

zjb1001 opened this issue Jan 30, 2024 · 2 comments

Comments

@zjb1001
Copy link

zjb1001 commented Jan 30, 2024

Environment:

PS C:\Users\ui> wsl -l -v
NAME STATE VERSION

  • Ubuntu Running 2
    docker-desktop Stopped 2
    docker-desktop-data Stopped 2

Client-2 start error info:
pg@HW:build-your-own-zerotier$ sudo ./vport 172.30.201.250 9999
[sudo] password for pg:
fail to tap_alloc: Device or resource busy

Any suggestion to fix it?

@peiyuanix
Copy link
Owner

I haven't tested the program in wsl2.
It looks like your error info is related to linux tun/tap device.
Maybe, you can confirm if /dev/net/tun exists.

And these keywords may be helpful: wsl2 tun tap

@zjb1001
Copy link
Author

zjb1001 commented Feb 3, 2024

Summary my test result, we can not assign two clients under the same kernel (here is the wsl2 kernel), because the tap device had been created after once one client was created, then it will conflict the when the second client was created.

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