OpenVPN for PocketPC forum

Added support for 'proto tcp'. Several folks asked for this.

Previously, CPU usage become so high that the device was unusable. This ultimately stemmed from an implementation oddness in CE's Winsock that caused it to fail to queue an overlapped IO request if it couldn't be immediately satisfied, saying there were too many outstanding. openvpn.exe never has more than one oustanding though, so that seems odd; plus it works fine for udp. This caused openvpn to continue to work handling the error and trying to schedule a read for later.

Anyway, queued reads are now handled in a worker thread for 'proto tcp' scenarios, which causes openvpn.exe to relinquish it's timeslice when idle and restore the system to usabilty.

great!!!!!

downloading and testing now.

proto tcp works on my jasjar. Great!

Tested via wifi and umts. I connected to my openvpn server at home (on a nslu2) and checked programmed recordings on my dreambox using opera. Isn't that damn cute?

Still remains the quirck that makes "disappear" the running vpn instance... even if the tunnel is up and usable, the tap device is "in use", and everything works fine. "signal stop all" helps anyway quit the connection.

As I told you... this is very very rc instead of alpha

Bye
Drakpz

What is the quirk? Are you saying that the instance is running, but when you switch to the VPN pane, it is not listed at all?

Yep. The vpn is running, but if i click on "vpn instances", it gets nothing (and the vpn pane is missing).

It happened also once that the instance was there, but in state "orphaned". Even in that case the tunnel was still running.

Please note that I kept on using the tunnel for about 30 minutes, and it kept working liche a charm

I see. OK, when 'orphaned' it probably means the management connection was lost. Not having anything at all is truly odd, however. The way the VPN instances works is:

* enumerate proceses
* filter on openvpn.exe
* correlate those pids with ones we know ovpncmgr (the gui) created

So even if the managment connection was lost I would still expect it to show as 'orphaned' as you mentioned, but not altogether invisible. That sounds more like it wasn't even enumerated (odd) or possibly some other weirdness causing it to be dropped from the executable name filter. Hmm....

well.. a couple of times since yesterday it appeared as orphaned... but most of the time there's no instance visible and no "instance pane".

Let me know if I can get some information to get you through this issue.