KPPP fails to connect.

Bug #16269 reported by Giorgos Akrivas on 2005-04-20
This bug report is a duplicate of:  Bug #36655: pppd dies on connection. Edit Remove
14
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Medium
Jonathan Riddell

Bug Description

KPPP fails to connect, because authentication fails. Workaround: comment the auth line
in /etc/ppp/options . However, this file mentions that commenting out this line is not
advised.

Michael Mauch (michael-mauch) wrote :

I also had this problem. The solution is in /usr/share/doc/kppp/README.Debian:

uncomment the "#" before the "noauth" in /etc/ppp/peers/kppp-options

Please maintainers, can this "#" be removed by default? Or if that can't be
done, could the friendly installer send a mail to tell users that we have to do
that on our own?

seanlynch (sean-lynch) wrote :

During installation an option should be added during network set-up for dial up modem users. This option can set
the comment "#" before the "noauth" in kppp-options for people who only use a dial up modem for connectivity, as
well as setting up other kppp options at that time. The script for modem users should also create the empty
file /etc/resolv.conf for dial up modem users so kppp does not display that error message on startup.

Currently their is no option for setting up dial-up connectivity during install, only network set up options
occur during install.

From #kubuntu-devel, the suggestion was:

-Ask for this using debconf

OR

- Activate it by default, unless there are any unintended side-effects in doing this.

Waiting for someone who's good with debconf, probably riddell's input on this.

artson (artson) wrote :

Seanlynch's comment is dead on. This is a needless hurdle for modem users and it has been around since at least kubuntu 5.04.

There is an easy way to ensure it never happens again: keep a machine around with a dial-up modem and install new kubuntu versions on it. Until this happens, ubuntu/kubuntu cannot claim to support users with dial-up connections. Granny shouldn't have to create empty files or use sudo and a text editor to amend kppp-options.

Changed in kdenetwork:
status: Unconfirmed → Confirmed
Uqbar (uqbar) wrote :

I've found that the actual "bug" is in /etc/ppp/peers/kppp-options.
Infact it shows a line saying:
#noauth
thus requiring all peers to authenticate. Usually provider ask you to authenticate but don't answer to authentication requests.
On the other side, if you change /etc/ppp/options, you'll change systemwide behaviopur, while the focus is on the kppp alone.
This is my EUR 0.01 contribution.

Confirmed on 6.06 - since in most cases noauth is necessary, it should be added by default.

No enlightening message to point that out either, when kppp fails - the average user becomes quite frustrated due to lack of a sensible default.

The person who dials to some system that needs to authenticate itself will know how to do this... so the default should make the clueless user's life easier.

cuberantcamper (redrock711) wrote :

I encountered this but in 5.10, I had high hopes for 6.06 but it is still there. I use dial-up. I have used the kppp dialer to connect with Lindows, Linspire, Suse, Mepis. Xandros, and Knoppix. With Kubuntu I have not been able to connect to the internet. I have not been able to find instructions to fix this problem that will work. Maybe someone, someday, somehow, will fix this problem. In the mean time I will move on to another distro if this bug is not fixed in 6.10. I feel that a working dailer is a basic function that should be more that a "medium" problem.

Jacob Popov (j-a-popov) wrote :

While creating localized Russian distro for distribution inmy native town, I've implemented the two workarounds:
1. Commented out 'auth' line in /etc/ppp/options
2. Created an empty /etc/resolv.conf file

So far I've encountered no errors or side-effects, everything works fine, including different scripts.

On 10/2/06, jaded Phoenix <email address hidden> wrote:
>
> While creating localized Russian distro for distribution inmy native town,
> I've implemented the two workarounds:
> 1. Commented out 'auth' line in /etc/ppp/options
> 2. Created an empty /etc/resolv.conf file
>
> So far I've encountered no errors or side-effects, everything works
> fine, including different scripts.
>
> --
> KPPP fails to connect.
> https://launchpad.net/bugs/16269
>

That's excellent! I wonder what I would need to do to make the same
correction you have done and then burn it onto a CD?

Jacob Popov (j-a-popov) wrote :

2artson:

First, read https://help.ubuntu.com/community/LiveCDCustomization/6.06
You should follow all the steps as described there to get a new customized cd image.

Two remarks though:
1. Don't forget to copy the 'filesystem.manifest' file to 'filesystem.manifest-desktop' and edit the latter, deleting some lines (compare them on the original cd to learn which lines to remove). This step is described just below all other so don't miss it

2. Don't delete the '/etc/resolv.conf' file

good luck!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.