Hi,
On Fri, Dec 1, 2017 at 8:53 AM, Arne Schwabe <a...@rfc2549.org> wrote:
> Am 30.11.2017 um 03:03 schrieb Selva Nair:
>
> Cross-posting to users and devel as this may be of interest to both.
>
> Hi,
>
> I have made a draft implementation of this feature that was discussed in a
> previous thread. A test executable (GUI only) is in this pre-release:
>
> https://github.com/selvanair/openvpn-gui/releases/tag/v11-echo-msg
>
> It would be great if anyone can test this out[*].
>
> Thanks,
>
> Selva
>
> [*] Although virtually any text can be sent, some familiarity with openvpn
> config/ccd parsing/quoting and push processing is necessary to get it
> right for non-trivial messages that contain comment characters, commas, new
> lines etc... Short and simple messages must be easy, though.
>
>
> Could we have some text stating that clients might only display one
> message per connect? At the moment you can have multiple "echo msg-notify
> message-title" pushed by the server. I would like to avoid in my client to
> implement logic to display multiple messages. If one message allowed the
> message can become just an Android notification without special logic
>
Yes, we can and probably should document that some clients may only
display one message. Do you also want to say that some clients may
interpret msg-window as msg-notify?
Even in case of Windows desktop, I think it may be better to display
only one message per connection as otherwise it starts to get very
noisy. At most one message window and one notification.
Jon, do you plan to document the proposed "echo msg" specs in management
notes or elsewhere? The single message per connect limitation
could be specified there.
> > msg-window : displayed only when starting from a disconnected state
> > not when reconnecting by SIGUSR1 or SIGHUP
>
> We need to clarify this a bit. You probably mean "reconnecting after a
> successful" connection. If there are multiple remote in the config and only
> the 3rd works you already have had two internal SIGUSR1.
>
Ah, I didn't think of that. In my current implementation, it'll miss the
message if a second remote succeeds after a failure with first remote.
I'll fix this.
If a successful connection moves to a new remote, we
may get a new message worth showing to the user but will be ignored
(unless its a notification). This may not be ideal but I want to avoid
displaying popups when the user may not be even at the desktop.
Any thoughts on this?
Thanks,
Selva
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
