Vineet, I think you could use Packet filtering plugin hook and use the [KILL] tag at the end of the pf file .
See http://openvpn.git.sourceforge.net/git/gitweb.cgi?p=openvpn/openvpn-testing.git;a=blob;f=openvpn-plugin.h;h=56b0a701574e6913b3a714e941cdc4899dbea8e1;hb=HEAD#l316 I have never used it myself, but I think that should sort you out. The doc says that this file may be dynamically updated during a client session. I assume the main process will pick up the change quick fast. Chantra On Mon, 2010-12-13 at 15:16 -0800, Vineet Kumar wrote: > Hi, > If my openvpn plugin spawns its own thread and from that thread > wants to kill a tunnel specified by IP:port how can that be done? > (something like what the 'telnet' management provides: "kill IP:port") > This plugin is meant to do other stuff and in certain scenarios wants > to close specific tunnels. > First I thought of using the plugin to write code to establish a > telnet-client sessions and send over "kill IP:port" command. But I > notice an issue with the management listener: if I run more than 1 > telnet session only the first one can pass through data whereas all > others' telnet sessions just hang. > > Is this even possible? > > Vineet > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel > -- http://www.debuntu.org
