On win7 with baloontips disabled you can connect but can't disconnect
via the gui.
Maybe that's your problem?
Am 18.03.2010 14:17, schrieb Gert Doering:
Hi,
On Thu, Mar 18, 2010 at 01:14:22PM +0100, Jan Just Keijser wrote:
took me a while to figure this one out:
the openvpn gui codes sets an 'exit event' (using a win32 API call
CreateEvent) before starting the actual openvpn process; when the user
chooses 'disconnect' this 'exit event' is triggered, which causes the
process to be terminated (using the appropriate win32 signal).
Huh, scary stuff.
How would that win32 signal be delivered to the openvpn.exe process? Will
it just receive a unix-like signal "SIGTERM"? Or does it have to poll
some sort of Windows event queue?
BTW: I just discovered that this is not limited to the openvpn.exe I
built *on* windows, but that my linux-mingw crosscompiled openvpn.exe
does this as well now, and so does the original OpenVPN-provided 2.1.1
binary(!). "Something weird happened to this machine", and I don't
understand what it is.
The question now becomes: what does openvpn do when it receives a
terminate signal? actually, is there a signal being sent to the server
to say "client X is disconnecting" ?
Nothing whatsoever visible in the logs. The last entry in the log (verb 5)
is after successful startup:
"Initialization Sequence Complete"
... and then when pressing<disconnect>, nothing whatsoever happens.
The OpenVPN connection stays alive and healthy(!), packets continue to
get forwarded, just the signal delivery fails.
(If I increase the log verbosity to "verb 9", lots of stuff is going
on, but nothing in there that gives any indication of signals being
received)
gert
