All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH ppp] ppp: Apply configuration options from a DCE request if ACK it
Date: Mon, 04 Jan 2021 11:20:11 -0600	[thread overview]
Message-ID: <9030bebb-1d58-8e5b-55fc-d357ebd4ebc7@gmail.com> (raw)
In-Reply-To: <20210101210412.23976-1-s.e.golubtsov@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

Hi Sergei,

On 1/1/21 3:04 PM, s.e.golubtsov(a)gmail.com wrote:
> From: Sergei Golubtsov <s.e.golubtsov@gmail.com>
> 
> Apply configuration options if the DCE sends a PPP LCP configure request
> and the DTE is going to ACK the request. Otherwise some options such as
> the ACCM may not correspond to the configuration negotiated with the
> DCE.
> ---
>   gatchat/ppp_cp.c | 7 +++++--
>   1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/gatchat/ppp_cp.c b/gatchat/ppp_cp.c
> index f3f2cc4f..371055e4 100644
> --- a/gatchat/ppp_cp.c
> +++ b/gatchat/ppp_cp.c
> @@ -660,9 +660,12 @@ static void pppcp_generate_event(struct pppcp_data *data,
>   	if (actions & SCR)
>   		pppcp_send_configure_request(data);
>   
> -	if (actions & SCA)
> +	if (actions & SCA) {
> +		/* Apply local options */
> +		if (data->driver->rca)
> +			data->driver->rca(data, packet);

So this is incorrect.  You're applying options of the wrong 'side'.  See my 
reply in the other thread for  a more detailed explanation.

>   		pppcp_send_configure_ack(data, packet);
> -	else if (actions & SCN)
> +	} else if (actions & SCN)
>   		pppcp_send_configure_nak(data, packet);
>   
>   	if (actions & STR)
> 

Regards,
-Denis

      reply	other threads:[~2021-01-04 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-01 21:04 [PATCH ppp] ppp: Apply configuration options from a DCE request if ACK it s.e.golubtsov
2021-01-04 17:20 ` Denis Kenzior [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9030bebb-1d58-8e5b-55fc-d357ebd4ebc7@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.