yarrick
In the Windows environment, a DNS tunnel has been established, but you cannot ping through it.
I captured the packets on both the server and client using Wireshark, and the results are as follows:
server：
client：
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
What operating system are you running in each end? Which TAP driver version are you using?
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
That sounds like the version that someone had working in #73 . Can you capture the tunnel traffic in each end?
Client:
Server:
Command run: server: iodined -f -P
I have also created the correct NS records and NS pointed to my public ip
i have also noticed this error in the logs of iodined server: ING pkt from user 1 = dupe from impatient DNS server, remembering
Is the server capture with some IP filter? Can you capture all traffic on the tun interface instead?
If you add more debug logging on windows, does it look like it gets anything? Or maybe capture the DNS traffic while you try pings. A screenshot of that wont be enough though.
@yarrick
Same issue for me. Client can send packet to server but server can't send packet to client.
Server: windows server 2025 Client: windows 11
