[Openvpn-devel] ovpn daemon not seeing my plugin thread...

Hi, I am writing a plugin that creates a thread at plugin-open time. But when I start ovpn as a daemon the ovpn code has no knowledge of that thread. The reason is obviously the fact that the thread-creation occurred *before* the daemon() call (that forked off a child which has no way of inheritin

Re: [Openvpn-devel] [Openvpn-users] Is it possible to access Windows XP shares over port 445?

Gert Doering wrote: Hi, On Wed, Jun 23, 2010 at 09:10:10AM +0200, Jan Just Keijser wrote: assigns a 169.254 address. If this works for you as well then maybe the tap-win32 developers can dive deeper into this and find out why windows treats the 'always connected' adapter differently from an

[Openvpn-devel] Topics for today's meeting

Hi, Topic list for today's (18:00 UTC, #openvpn-de...@irc.freenode.net) meeting is a little short. David suggested discussing (and perhaps giving an ACK to) this patch: If you have any other topics you'd like to have discussed, please l

Re: [Openvpn-devel] ovpn daemon not seeing my plugin thread...

> The reason is obviously the fact that the thread-creation occurred > *before* the daemon() call (that forked off a child which has no way > of inheriting a copy of that thread). > So does this mean then that the ovpn daemon infrastructure will only > work with plugins that don't do threading of t

Re: [Openvpn-devel] ovpn daemon not seeing my plugin thread...

Perfect! The following worked: I defined openvpn_plugin_select_initialization_point_v1() to return OPENVPN_PLUGIN_INIT_POST_DAEMON and now it all works since the plugin invocation now gets delayed to be after the daemon thread starts up. Thanks a lot, Vineet On Thu, Jun 24, 2010 at 4:58 AM, chant