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

In the Windows environment, a DNS tunnel has been established, but you cannot ping through it. #102

Open
Miniko233 opened this issue Nov 26, 2024 · 3 comments

Comments

@Miniko233
Copy link

I captured the packets on both the server and client using Wireshark, and the results are as follows:
server:
image
client:
image
The client sent a ping packet to the server, and the server received the request and responded, but the client did not receive the server's response.
I don't know why this is happening. I looked at other issues, and the TAP version they are using is tap-windows-9.9.2_3.exe

@yarrick
Copy link
Owner

yarrick commented Feb 8, 2025

What operating system are you running in each end? Which TAP driver version are you using?

@0-0eth0
Copy link

0-0eth0 commented Feb 26, 2025

Same issue for me as well.
I am running on windows 11 with TAP Driver version:9.9.2_3 @yarrick

What could go wrong?
Iodine has server started and client also says connection complete but couldn't talk with each other

@yarrick
Copy link
Owner

yarrick commented Feb 26, 2025

That sounds like the version that someone had working in #73 . Can you capture the tunnel traffic in each end?

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

3 participants