From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: ifconfig ppp0 errors
Date: Fri, 14 Jan 2011 17:28:25 +0000 [thread overview]
Message-ID: <4D3087B9.9000000@workingcode.com> (raw)
In-Reply-To: <Pine.GSO.4.64.1101111527150.23601@sunfire13.eecs.tufts.edu>
Slawomir Skret wrote:
> One comment that I have is that it would be useful to be able to
> retrieve the actual cause of the errors with the pppstats or some other
> way from the ppp driver. When they show up in the ifconfig it is not
> clear what's causing them and it requires some work to get to the actual
> cause.
The information you get from ifconfig -- the count of input errors -- is
essentially all that the driver knows. It knows that it's getting bad
frames, but it can't really know _why_ they're bad. That takes a human.
(It'd be possible to report some more details about edge cases here, and
some of the implementations do just that, but low-level problems that
drop hunks of data are, I think, inherently hard for a PPP driver to
diagnose on its own.)
--
James Carlson 42.703N 71.076W <carlsonj@workingcode.com>
prev parent reply other threads:[~2011-01-14 17:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 20:30 ifconfig ppp0 errors Slawomir Skret
2011-01-11 21:04 ` James Carlson
2011-01-11 21:57 ` Slawomir Skret
2011-01-11 22:50 ` Slawomir Skret
2011-01-11 23:30 ` James Cameron
2011-01-12 2:29 ` Paul Mackerras
2011-01-12 13:21 ` James Carlson
2011-01-12 18:40 ` Slawomir Skret
2011-01-12 19:47 ` James Carlson
2011-01-12 21:05 ` James Cameron
2011-01-12 21:23 ` James Carlson
2011-01-12 21:51 ` James Cameron
2011-01-12 22:17 ` James Carlson
2011-01-14 16:58 ` Slawomir Skret
2011-01-14 17:28 ` James Carlson [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=4D3087B9.9000000@workingcode.com \
--to=carlsonj@workingcode.com \
--cc=linux-ppp@vger.kernel.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.