-
Notifications
You must be signed in to change notification settings - Fork 989
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:Failed to setup adapter (problem code: 0x34) #1136
Comments
Hi @futurecad - please fill out the logs and config section and give a little more detail as to how you ran into this error. Thanks. |
time="2024-05-07T14:37:55+08:00" level=error msg="Failed to get a tun/tap device" error="create Wintun interface failed, create TUN device failed: Error creating interface: The device is not ready for use." |
@futurecad There is some info here that may be relevant to your issue: tailscale/tailscale#4225 (comment) Can you provide logs from the referenced file? Also curious if any of the listed workarounds help. |
I've seen this and I'm also looking for the specific impact. |
Another problem I encountered was that the log reported an error failed to set address: Element not found. |
@futurecad Waiting on logs from |
level=fatal msg="failed to set address: Element not found." |
There are also two virtual network cards appearing. |
This will result in access to only Nebula authorized networks and no other networks. |
The phenomenon is that the virtual network card appears and then disappears. |
@futurecad Do you know what |
@johnmaguire This is the program I packaged in the outer layer. Currently, there are many problems on Windows 7. |
Can you please describe the problems? I cannot help if I don't know what's going on. Unfortunately, Windows performance relies on the use of Registered IO which was added in Windows 8. Additionally, since Nebula v1.9.0, we don't support versions older than Windows 10.
|
Are there any other solutions to solve the slow network problem before Windows 8? |
After I enable nebula, downloading files becomes very slow. |
Enabling Nebula will not slow down underlay networks. Network traffic sent/received over Nebula prior to Windows 8 does have bottlenecks compared to Linux/macOS and newer versions of Windows. The best solution is to upgrade to Windows 8. I don't understand what Nebula is slowing down when that the logs you've provided show it's unable to start.
|
After successful startup, accessing the network in unsafe_router to download files will be very slow. Indeed, this only occurs in versions before Windows 8. The logs I mentioned above are what happened on another computer. |
Thanks for the clarification. Have you seen the repeated question regarding VMware software? It is relevant to your original question. Or, have you tried steps here or here to resolve it? |
The computer in the original question did not have vmware installed. After starting Nebula, the network card appeared and then disappeared. Log: level=fatal msg="failed to set address: Element not found." |
|
Thank you. Are you able to try the following steps on the machine receiving "Element not found"?
|
@futurecad I just experienced a similar (but different) issue with the Wintun driver in a VM. I'm not sure the cause, but I resolved it through a two-step process:
Let me know if this improves your situation. |
I faced the same issue, workaround above works. |
I face with the same questions,and I solved it by 3 steps; |
What version of
nebula
are you using? (nebula -version
)1.8.2
What operating system are you using?
windows
Describe the Bug
Failed to setup adapter (problem code: 0x34):The display device needs to be reinitialized due to a hardware error
Logs from affected hosts
Config files from affected hosts
The text was updated successfully, but these errors were encountered: