public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001689] New: PPP Idle Timeout not reset automatically Date: Wed, 17 Oct 2012 15:06:00 -0000 [thread overview] Message-ID: <bug-1001689-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001689 Summary: PPP Idle Timeout not reset automatically Product: eCos Version: 3.0 Platform: All OS/Version: Other Status: UNCONFIRMED Severity: enhancement Priority: low Component: TCP/IP AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: kenkyee@excite.com CC: ecos-bugs@ecos.sourceware.org Class: Advice Request I'm running with the FreeBSD stack if it matters, but what I'm seeing is PPP doesn't seem to reset the PPP timeout the next time it connects.n Code is roughly init_all_network_interfaces(), followed by cyg_ppp_up() which is then allowed to time out from traffic going to idle. Then cyg_ppp_up() is called a few minutes later and eCos seems to be timing out immediately. Info printed to the debug output looks like this: SYSLOG 08: Using interface ppp0 SYSLOG 04: Connect: ppp0 <--> /dev/ser0 SYSLOG 04: local IP address 10.20.20.2 SYSLOG 04: remote IP address 10.20.20.1 SYSLOG 08: Terminating connection due to lack of activity. SYSLOG 04: Connection terminated, connected for 1 minutes Then later on: SYSLOG 08: Using interface ppp0 SYSLOG 04: Connect: ppp0 <--> /dev/ser0 SYSLOG 08: Connect time expired SYSLOG 04: Connection terminated, connected for 1 minutes Note that the second connection doesn't show that termination is due to lack of activity but that connect time has expired. No matter how many times cyg_ppp_up is called again, it never connects again :-( Workaround is to disable PPP Idle timeouts in the PPP options -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-10-17 15:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-17 15:06 bugzilla-daemon [this message] 2012-10-17 15:06 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-1001689-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-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: linkBe 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).