On Mon, Oct 19, 2015 at 4:14 PM, Fish Wang <fish.t...@gmail.com> wrote:
> Regarding Windows OpenVPN GUI: I have an internal fork of this OpenVPN GUI > (https://github.com/jochenwierum/openvpn-manager) from jochenwierum, with > many bug fixes and improvements, and it works fairly well on Windows. Maybe > I should tidy my patches and open source it on github? > That would be great, but eventually we need something more than bug fixes and some improvements. The biggest problem with the present GUI is the need to run it as administrator. A windows service exists but its not stable enough and the GUI (I mean the official one) cannot control it in any meaningful way. The so-called "new GUI" that is bundled with the windows build is supposedly using the management interface but it can do that only when the openvpn executable is started by the GUI itself.. That defeats most of the advantages offered by the management interface. I feel a framework such as the "interactive service" -- which is now and again mentioned in the mailing lists but no idea what it is --- with new GUI or a partial rewrite of the current one to effectively use the management interface plus a stable service is needed. Alternatively the current GUI could be adapted to use the "interactive service" if its ready for prime time. I can offer some coding/testing/debugging time but I've no real expertise in windows programming or GUI in general. I'm an old style CLI guy who wouldn't miss much if init is a symlink to vi or emacs:) Selva > Best, > Fish > > -----Original Message----- > From: Morris, Russell [mailto:rmor...@rkmorris.us] > Sent: Monday, October 19, 2015 7:59 AM > To: Heiko Hund <heiko.h...@sophos.com>; sam...@openvpn.net > Cc: openvpn-devel@lists.sourceforge.net > Subject: Re: [Openvpn-devel] Creating a Windows team for OpenVPN? > > Hi, > > Just a couple thoughts here, from a (absolutely!) non-expert ... :-(. > > I have been trying to develop my own "GUI" - not because the current one > doesn't work (not at all!), but because I want a bit of an extended feature > set ... to be able to change Tray Icon color with traffic (Tx/Rx), and plot > ping timing to a remote machine over the link, and as well traffic and bit > rate plots in the UL and DL. > > That all said, I can definitely see that the network adapter (TAP) and > openvpn.exe really are up and down (a lot!) on Windows ... :-(. I am trying > to use NSSM to at least keep openvpn.exe up (i.e. restart it), but the > network connection is a challenge also - often having to be reset (disabled > and enabled). So to the question below ... yes, Windows does need some work. > > I'd be happy to help out - but as above, I'm not an expert. So definitely > willing, but usefulness may be questionable unfortunately ... ;-). > > Thanks! > > ... Russell > > > > -----Original Message----- > From: Heiko Hund [mailto:heiko.h...@sophos.com] > Sent: Monday, October 19, 2015 9:16 AM > To: sam...@openvpn.net > Cc: openvpn-devel@lists.sourceforge.net > Subject: Re: [Openvpn-devel] Creating a Windows team for OpenVPN? > > On Monday 19 October 2015 10:20:23 sam...@openvpn.net wrote: > > > > I'm thinking it might make sense to create a dedicated Windows team > > > > that could share the burden of Windows issues amongst themselves, > > > > without any one person gettings tagged the "Windows guy". > > > > > > Judging from the review the Windows patches received I think this > might be > > > an too ambitious goal. Obviously not many care besides the regulars > who > > > make a > > > > Anyways, not many seemed to care about about easy-rsa before it became a > > separate project in GitHub. Now we have easy-rsa 3 by pekster and ecrist. > > Similarly for openvpn-build we have/had Alon, pekster, me and syzzer. I'm > > sure more examples could be found from other projects. > > > > I'm also not speaking primarily of Windows patches, but also all the > other > > stuff such as debugging, user support, ticket review, packaging, etc. > > Ok, I think here is the main misunderstanding. My understanding was that > you > want a Windows development team. That I think would be counter productive. > For > the other topics I do not have a opinion. > > > > > am working on a replacement for openvpnserv.exe. > > > > > > Please consider reviewing and improving the interactive service patch > > > instead of duplicating work. > > > > Are you saying that the interactive service also doubles as a Windows > system > > service? If so, can it be configured to autostart selected openvpn > > connections on boot and restart them if they crash/stop? > > No, and I do not think that the service should take care of that. That's > rather things that can be handled by the GUI. > > > Now, can anyone provide proof that having a Windows team would actually > > _hurt_ the project? If not, what does it matter if it fails? We could > just > > scrap the idea retroactively. > > Hehe nice turn demanding proof, that'll shut up ppl. =) > > Heiko > > > Sophos Technology GmbH, Amalienbadstraẞe 41/Bau 52, D-76227 Karlsruhe, > Deutschland > Tel +49 (0)721 25516 0 Fax +49 (0)721 25516 200 E-Mail i...@sophos.de > www.sophos.de > Sitz der Gesellschaft: Karlsruhe, Amtsgericht Mannheim HRB 712658 > Geschäftsführer: Nicholas Bray, Pino von Kienlin, Wolfgang Hilpert, > Jennifer Onslow. > Sophos GmbH, Gustav-Stresemann-Ring 1, 65189 Wiesbaden, Deutschland > Tel +49 (0) 611 5858-0 Fax +49 (0) 611 5858-1042 E-Mail i...@sophos.de > www.sophos.de > Sitz der Gesellschaft: Wiesbaden, Amtsgericht Wiesbaden HRB 25915 > Geschäftsführer: Nicholas Bray, Wolfgang Hilpert, Pino von Kienlin, > Jennifer Onslow > > > ------------------------------------------------------------------------------ > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel > > ------------------------------------------------------------------------------ > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel >
