public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001873] Patches to upgrade lwip to 1.4.1
Date: Fri, 06 Jun 2014 07:46:00 -0000	[thread overview]
Message-ID: <bug-1001873-777-uDtfl80vKT@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001873-777@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001873

--- Comment #46 from Oleg Uzenkov <o.uzenkov@unicore.co.ua> ---
Hi Ilija,

Thanks for your advice. I will do what you suggested. If the upgrade is
successful I will upload it here. 

As to the work of PPP in the vanilla lwip 1.4.1, when trying to connect, quite
often I used to receive the following debug log:

++++++++++++++++++++++

[DEBUG] Initializing PPP
lcp_init: xmit_accm=0 0 0 0
upap_init: 0
pppOverSerialOpen: unit 0: Connecting
pppStart: unit 0
ppp_set_xaccm[0]: outACCM=0 0 0 0
ppp_send_config[0]: outACCM=FF FF FF FF
ppp_recv_config[0]: inACCM=0 0 0 0
lcp_lowerup: asyncmap=0 0 0 0
LCP: lowerup state 0 (LS_INITIAL) -> 2 (LS_CLOSED)
auth_reset: 0
lcp_addci: L opt=2 0
lcp_addci: L opt=5 2FF6F209
lcp_addci: opt=7
lcp_addci: opt=8
pppWrite[0]: len=46
fsm_sdata(LCP): Sent code 1,1,20.
LCP: sending Configure-Request, id 1
LCP: open state 2 (LS_CLOSED) -> 6 (LS_REQSENT)
pppStart: finished
LCP: timeout resending Config-Request state=6 (LS_REQSENT)
lcp_addci: L opt=2 0
lcp_addci: L opt=5 2FF6F209
lcp_addci: opt=7
lcp_addci: opt=8
pppWrite[0]: len=45
fsm_sdata(LCP): Sent code 1,1,20.
LCP: sending Configure-Request, id 1
LCP: timeout resending Config-Request state=6 (LS_REQSENT)
lcp_addci: L opt=2 0
lcp_addci: L opt=5 2FF6F209
lcp_addci: opt=7
lcp_addci: opt=8
pppWrite[0]: len=45
fsm_sdata(LCP): Sent code 1,1,20.
LCP: sending Configure-Request, id 1
LCP: timeout resending Config-Request state=6 (LS_REQSENT)
++++++++++++++++++++++++++++++

(This is just a snipet from the log.)
Apparently, it meant that I did not receive anything from GPRS modem through
the serial port. That happened quite often, however, successful connection did
happen also.

But when I started using GPRS VPN service from my cellular network provider
this problem has not shown up yet. I have tested it several times and there was
always  a successfull connection. So I believe now, the problem was related to
the quality of service and not to the PPP (1.4.1) implementation.

Oleg

-- 
You are receiving this mail because:
You are the assignee for the bug.


  parent reply	other threads:[~2014-06-06  7:46 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28  6:50 [Bug 1001873] New: " bugzilla-daemon
2013-06-28  6:50 ` [Bug 1001873] " bugzilla-daemon
2013-06-28  6:50 ` bugzilla-daemon
2013-06-28  6:51 ` bugzilla-daemon
2013-06-28  6:51 ` bugzilla-daemon
2013-06-28  6:51 ` bugzilla-daemon
2013-06-28  6:51 ` bugzilla-daemon
2013-06-28  6:52 ` bugzilla-daemon
2013-06-28  6:52 ` bugzilla-daemon
2013-06-30 22:03 ` bugzilla-daemon
2013-07-01 11:54 ` bugzilla-daemon
2013-07-01 11:55 ` bugzilla-daemon
2013-07-01 11:55 ` bugzilla-daemon
2013-07-01 11:56 ` bugzilla-daemon
2013-07-01 11:56 ` bugzilla-daemon
2013-07-01 11:56 ` bugzilla-daemon
2013-07-01 11:57 ` bugzilla-daemon
2013-07-01 11:57 ` bugzilla-daemon
2013-07-01 11:57 ` bugzilla-daemon
2013-07-01 11:58 ` bugzilla-daemon
2013-07-01 13:34 ` bugzilla-daemon
2013-08-09 16:13 ` bugzilla-daemon
2013-08-10 15:51 ` bugzilla-daemon
2013-09-06  7:00 ` bugzilla-daemon
2013-09-06  7:01 ` bugzilla-daemon
2013-09-13 20:30 ` bugzilla-daemon
2014-02-15  2:58 ` bugzilla-daemon
2014-02-25 15:44 ` bugzilla-daemon
2014-02-25 15:46 ` bugzilla-daemon
2014-02-25 15:47 ` bugzilla-daemon
2014-02-25 15:48 ` bugzilla-daemon
2014-02-25 15:48 ` bugzilla-daemon
2014-02-25 15:48 ` bugzilla-daemon
2014-02-25 15:49 ` bugzilla-daemon
2014-02-25 15:49 ` bugzilla-daemon
2014-02-25 15:50 ` bugzilla-daemon
2014-02-25 16:09 ` bugzilla-daemon
2014-02-25 16:09 ` bugzilla-daemon
2014-03-11 22:25 ` bugzilla-daemon
2014-05-07 14:57 ` bugzilla-daemon
2014-06-04 14:38 ` bugzilla-daemon
2014-06-06  7:46 ` bugzilla-daemon [this message]
2014-06-10  8:27 ` bugzilla-daemon
2013-06-28  6:50 [Bug 1001873] New: " bugzilla-daemon
2013-06-28  6:50 ` [Bug 1001873] " bugzilla-daemon
2013-06-28  6:50 ` bugzilla-daemon
2013-06-28  6:51 ` bugzilla-daemon
2013-06-28  6:51 ` bugzilla-daemon
2013-06-28  6:51 ` bugzilla-daemon
2013-06-28  6:51 ` bugzilla-daemon
2013-06-28  6:52 ` bugzilla-daemon
2013-06-28  6:52 ` bugzilla-daemon
2013-06-30 22:03 ` bugzilla-daemon
2013-07-01 11:54 ` bugzilla-daemon
2013-07-01 11:55 ` bugzilla-daemon
2013-07-01 11:56 ` bugzilla-daemon
2013-07-01 11:56 ` bugzilla-daemon
2013-07-01 11:56 ` bugzilla-daemon
2013-07-01 11:56 ` bugzilla-daemon
2013-07-01 11:57 ` bugzilla-daemon
2013-07-01 11:57 ` bugzilla-daemon
2013-07-01 11:57 ` bugzilla-daemon
2013-07-01 11:58 ` bugzilla-daemon
2013-07-01 13:34 ` bugzilla-daemon
2013-08-09 16:13 ` bugzilla-daemon
2013-08-10 15:51 ` bugzilla-daemon
2013-09-06  7:01 ` bugzilla-daemon
2013-09-06  7:01 ` bugzilla-daemon
2014-02-25 15:44 ` bugzilla-daemon
2014-02-25 15:46 ` bugzilla-daemon
2014-02-25 15:47 ` bugzilla-daemon
2014-02-25 15:48 ` bugzilla-daemon
2014-02-25 15:48 ` bugzilla-daemon
2014-02-25 15:48 ` bugzilla-daemon
2014-02-25 15:49 ` bugzilla-daemon
2014-02-25 15:49 ` bugzilla-daemon
2014-02-25 15:50 ` bugzilla-daemon
2014-02-25 16:09 ` bugzilla-daemon
2014-02-25 16:09 ` bugzilla-daemon
2014-03-12  9:17 ` bugzilla-daemon
2014-03-12  9:36 ` bugzilla-daemon
2014-05-05 23:08 ` bugzilla-daemon
2014-06-04 14:38 ` bugzilla-daemon
2014-06-05 10:06 ` bugzilla-daemon
2014-06-06  7:46 ` bugzilla-daemon
2014-06-10  8:27 ` bugzilla-daemon
2014-06-10 11:05 ` bugzilla-daemon

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=bug-1001873-777-uDtfl80vKT@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=unassigned@bugs.ecos.sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).