| Summary: | Several initialisation strings for a modem | ||
|---|---|---|---|
| Product: | [Unmaintained] kppp | Reporter: | jose |
| Component: | general | Assignee: | Harri Porten <porten> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
jose
2001-02-02 14:13:13 UTC
*** This bug has been confirmed by popular vote. *** Better late than never, i suppose :-) Personally i dont use a modem or ISDN adapter anymore, but having worked in tech support not so long ago the problem of course still persists. An improvement idea related to this bug, would be to have a kppp mode where the line automaticly is probed (only modems)and line speed is locked and written to a profile. The problem with noisy phonelines is rather simple, and is that modems tend to initially negotiate the correct line speed (40000 bps, 41333 bps etc) but during the session increase speed. Assume ideal linespeed is 40000 bps: increasing linespeed from ex. 4000 bps to 41333bps can result in so many transmission errors that line-speed never returns to the ideal 40000bps. Just locking maximum speed to initial nogtiation speed - the 40000 bps - will solve loads of problems. I guess near 80% of modem could be solved this way - this is based on 4+ yeafs experience with modem related problems. 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. |