Hi Bruno,
> Another reason which incited me to continue using the "Connect" client > was the fact that for rather old people not very accustomed to VPNs and > the like (my "customers" are mostly retired people in their sixties or > seventies), having a big window open, with a clear feedback showing data > flowing in and out and displaying quite clearly valuable information as > the local IP address and the server's address, seemed easier to use and > also for me to diagnose when problems occur. > Thanks for the feedback. As Gert said, knowing what users want/expect will help us improve the UI. When I had users I used to tell them to just check whether the icon turns green and complain if it doesn't. In my case the VPN was for access to the office/corporate network from outside, and the only thing that mattered was whether they can access internal resources such as files, software license servers etc. Once setup, OpenVPN-GUI run with "silent_connection" worked very well for that. Until the next time I decided to tweak the setup and break it. By the way, the GUI does show the tunnel IP in the tray icon popup as well as on the status window. But not the remote IP --- we show the connected profile name instead. Unfortunately, there is very limited space in a tray icon popup, but we could add this to the status window which opens up when you double click the tray icon when connected/connecting. My users never could diagnose anything on their own, and I preferred to go through the client and server logs. Regards, Selva
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
