Bug 90100 - Interpretation of errors from pppd could be improved
Summary: Interpretation of errors from pppd could be improved
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kppp
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-23 15:41 UTC by Oliver Story
Modified: 2025-06-09 20:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Story 2004-09-23 15:41:43 UTC
Version:           unknown (using KDE 3.2.2,  (testing/unstable))
OS:                Linux (i686) release 2.6.5

I'm using Knoppix installed on the hard drive to create some kind of debian derivative.

When using kppp to log in to my ISP, sometimes the pppd daemon dies with an error code, which kppp says it is unable to provide help for. It would be helpful to me to at least have a description of the error code rather than just a numeric. For example:

- when the error code was 19 - according to the pppd manual this means "We failed to authenticate ourselves to the peer", or in simpler language that I got the username or password wrong

- when the error code was 16 - according to the pppd manual this means " The link was terminated by the modem hanging up" which could, I'm sure, be caused by many things; in my case if it occurs on connection it most often means that I've run out of credit with my ISP. This is evident if I use "terminal" as the connection method because the ISP login screen will say so. Possibly if the connection had been established for some time it could mean someone picked up the phone somewhere else in the house :-)

I've got two suggestions:
1. give a description of the error - it took me a while as a new user to realise I could look this up in the man page for pppd, but in any case it would be easier if it was immediately available

2. if there's any kind of connection script running behind the scenes, it could be useful to display that to the user when something goes wrong - eg when using PAP/CHAP is there any equivalent to the login text when using "terminal" as the connection method that could be displayed to help pinpoint the error?
Comment 1 Harri Porten 2004-09-23 16:19:05 UTC
Good suggestions. Would this be something that could be your entry point to KDE programming? :)
Comment 2 Christoph Cullmann 2025-06-09 20:48:35 UTC
This project is unfortunately no longer maintained.

If a new maintainer wants to step up and take care, the project is archived here:

https://invent.kde.org/unmaintained/kppp

You can just clone it in your private namespace on invent.kde.org and if you have started to work on it and fixed/implemented something get it reviewed and the project unarchived.

Sorry for the inconveniences.