Bug 52360 - takes many attempts to connect to ISP
Summary: takes many attempts to connect to ISP
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-28 03:11 UTC by hounsell
Modified: 2023-01-22 05:05 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hounsell 2002-12-28 03:11:53 UTC
Version:           2.4.1 (using KDE KDE 3.0.3)
Installed from:    Mandrake RPMs
Compiler:          Mandrake 9.0 distribution with patches 
OS:          Linux

It can take twenty minutes or more to get a connection to my ISP. My windows computer connects almost every single time. I have an external Sportser 56K modem. Often I see the connect at 56K and then garbage in the log window, after which the coneection dies. Is there some way of setting this up so I can get connected without having to try, try, try again? Once the connection is established things work fine but it take why too log to get connected. Please help.

Cheers
Paul

Here is a log files of the latest failure. 

Dec 27 20:09:01 p1 pppd[16558]: pppd 2.4.1 started by paul, uid 501
Dec 27 20:09:01 p1 pppd[16558]: using channel 36
Dec 27 20:09:01 p1 pppd[16558]: Using interface ppp0
Dec 27 20:09:01 p1 pppd[16558]: Connect: ppp0 <--> /dev/tts/0
Dec 27 20:09:01 p1 pppd[16558]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9ed3a5cb> <pcomp> <accomp>]
Dec 27 20:09:04 p1 pppd[16558]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9ed3a5cb> <pcomp> <accomp>]
Dec 27 20:09:31 p1 pppd[16558]: Terminating on signal 15.
Dec 27 20:09:31 p1 pppd[16558]: sent [LCP TermReq id=0x2 "User request"]
Dec 27 20:09:31 p1 pppd[16558]: rcvd [LCP ConfReq id=0x1 < 00 04 00 00> <mru 1524> <asyncmap 0x0> <auth pap> <pcomp> <accomp> <mrru 1524> <endpoint [MAC:00:c0:7b:98:f2:a7]> < 17 04 a6 04>]
Dec 27 20:09:31 p1 pppd[16558]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x9ed3a5cb> <pcomp> <accomp>]
Dec 27 20:09:31 p1 pppd[16558]: rcvd [LCP ConfReq id=0x1 < 00 04 00 00> <mru 1524> <asyncmap 0x0> <auth pap> <pcomp> <accomp> <mrru 1524> <endpoint [MAC:00:c0:7b:98:f2:a7]> < 17 04 a6 04>]
Dec 27 20:09:31 p1 pppd[16558]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x9ed3a5cb> <pcomp> <accomp>]
Dec 27 20:09:32 p1 pppd[16558]: rcvd [LCP TermAck id=0x2]
Dec 27 20:09:32 p1 pppd[16558]: Connection terminated.
Dec 27 20:09:32 p1 pppd[16558]: Exit.
Comment 1 Andrew 2006-11-14 09:05:02 UTC
I've gotten this far with Kubuntu (many times) and FC4 (once), and it -always- disconnects very much at the "I can see garbage" stage.

I can put a pause in the kppp script for as long as I want to watch the garbage but it fails immediately after. Sorry if this sounds different but I'm hoping to resolve a nearly identical failure.
Comment 2 Andrew Crouthamel 2018-11-02 04:26:25 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-16 02:47:19 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 4 hounsell 2018-11-18 21:25:32 UTC
You can close this ticket. I no longer have the equipment to test the issue any more
Comment 5 Justin Zobel 2022-12-23 00:28:08 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-07 05:21:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-01-22 05:05:25 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!