M
> >> To: Vladislav Grishenko ; openvpn-
> >> de...@lists.sourceforge.net
> >> Subject: Re: [Openvpn-devel] [PATCH] Fix --remote protocol can't be
> >> set without port argument
> >>
> >> On 03/09/2020 13:44, Vladislav Grishenko wrote:
> >
On 08/09/2020 21:01, Vladislav Grishenko wrote:
> Hi David,
>
>> -Original Message-
>> From: David Sommerseth
>> Sent: Tuesday, September 8, 2020 6:23 PM
>> To: Vladislav Grishenko ; openvpn-
>> de...@lists.sourceforge.net
>> Subject: Re: [Op
Hi David,
> -Original Message-
> From: David Sommerseth
> Sent: Tuesday, September 8, 2020 6:23 PM
> To: Vladislav Grishenko ; openvpn-
> de...@lists.sourceforge.net
> Subject: Re: [Openvpn-devel] [PATCH] Fix --remote protocol can't be set
> without
> port a
On 03/09/2020 13:44, Vladislav Grishenko wrote:
> According client-options.rst additional argumets ``port`` and ``proto``
> are both optional and it's allowed to have port absent and protocol set:
> --remote args
> Examples:
> remote server.example.net tcp
>
> But when protocol
According client-options.rst additional argumets ``port`` and ``proto``
are both optional and it's allowed to have port absent and protocol set:
--remote args
Examples:
remote server.example.net tcp
But when protocol is set without preceeding port argument, it is being
misparsed
