windows binary
Hi, with the current windows build (version 0.7.0) from yarrick I can connect successful to my server, but are not able to ping or make any other connection to the server. The Server Firewall is not the problem, what I have verified. On the net I found also 2 other ppl which have the problem.
- https://hardforum.com/threads/anyone-use-iodine.1843748/
- http://lists.wpkg.org/pipermail/iodine-users/2011-August/000355.html With the android client andiodine I can successful connect and establish connection to the server. So it must me a problem on the Windows client.
So possible your fork/code fixed any problem which is involved? Have you any prebuild binarys for windows?
hi, after reading more and more I stumbled over the problem: the TAP driver version. I also use current OpenVPN, which comes with the current NDIS 6 TAP driver. On the Readme (I should read it surely before) I found the notice, that it is not compatible. It is mentioned, to use the NDIS version 5 driver, which is made for Win XP. I use myself Windows 10.. NDIS 6 is made for Windows Visa... Is there anything we can do, to fix the compatibility problem? Or someone has fixed it and we only miss a current windows build?
I have not made any changes to windows-related components of iodine except to ensure that it builds correctly on Linux. You are welcome to set up a Windows build environment (such as using a mingw toolchain) and do some debugging to find out the issue causing iodine to not work correctly on Windows.
Also see if you can install the NDIS 5 driver on Windows 10, that might just work.
Unfortunately I do not have any prebuilt binaries for windows so you will have to make those yourself (see above with mingw).
As mentioned in issue #18 Windows is currently not supported, however a Linux VM is fairly easy to set up if you want to use the latest builds of iodine.