All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven <liu-dj@neusoft.com>
To: ofono@ofono.org
Subject: Re: About ppp_receive()
Date: Wed, 25 Aug 2010 11:22:59 +0800	[thread overview]
Message-ID: <4C748C93.1000401@neusoft.com> (raw)
In-Reply-To: <4C748662.2080605@gmail.com>

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

Denis Kenzior wrote:
> Hi Steven,
> 
>>>> But some carriers, like China Telecom or Sprint Network etc, will
>>>> support the full configuration
>>>> options(Magic-Number,Protocol-Field-Compression,Address-and-Control-Field-Compression),
>>>>
>>>> So if PFC option is used ,our code will got wrong with ppp_receive().
> 
> We explicitly do not advertise capability to receive PFC or ACFC
> packets.  If the remote peer PPP stack is compliant it should not be
> sending such packets in the first place.

Yes,We do not advertise capability to receive PFC or ACFC, just like i 
have said

 >>>In our current source code, because we only negotiate two
 >>> configuration options - REQ_OPTION_MRU and REQ_OPTION_ACCM. so it's
 >>> okey for our PPP stack.

> 
> Are you saying you're working with a PPP stack that is not compliant and
> not honoring our request not to send ACFC or PFC packets?
> 

NO, just as the above have said ,we only negotiate two options, it's ok 
for our PPP stack and it runs correctly.

>> anyway, if we want to implement a full PPP stack, we have a long way to go.
>>
> 
> That's the point, we actually do not want to implement a full PPP stack.
>  Only enough to talk to the relatively unsophisticated PPP stacks
> running inside the modem firmware.  Remember, PPP is simply used host to
> modem.  It is not used over the air.

yes, i got it.

B.R

Steven
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosure or copying 
is strictly prohibited, and may be unlawful.If you have received this communication in error,please 
immediately notify the sender by return e-mail, and delete the original message and all copies from 
your system. Thank you. 
---------------------------------------------------------------------------------------------------


  reply	other threads:[~2010-08-25  3:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23  5:42 About ppp_receive() Steven
2010-08-23  9:12 ` Marcel Holtmann
2010-08-24 10:17 ` Zhang, Zhenhua
2010-08-25  1:31   ` Steven
2010-08-25  1:56     ` Zhang, Zhenhua
2010-08-25  2:04       ` Steven
2010-08-25  2:17         ` Zhang, Zhenhua
2010-08-25  2:17       ` Steven
2010-08-25  2:56         ` Denis Kenzior
2010-08-25  3:22           ` Steven [this message]
2010-08-25  3:26             ` Denis Kenzior
2010-08-25  3:48               ` Steven
2010-08-25  4:18                 ` Marcel Holtmann
2010-08-25  4:22                   ` Steven
2010-08-25  5:07                     ` Marcel Holtmann
2010-08-25  5:36                       ` Steven
2010-08-25  5:49                         ` Steven
2010-08-25  4:12     ` Marcel Holtmann

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=4C748C93.1000401@neusoft.com \
    --to=liu-dj@neusoft.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.