Ubuntu
knet package

knet failes to connect, incorrect chap-secrets

Bug #71196 reported by Jozef Komenda on 2006-11-10

Affects		Status	Importance	Assigned to	Milestone
	knet (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Even after having locally fixed

https://launchpad.net/distros/ubuntu/+source/knet/+bug/71080

the knet fails to connect via PPPoE. The following PPPD message can be found in the output:

The remote system (hostname) is required to authenticate itself
but I couldn't find any suitable secret (password) for it to use to do so.
(None of the available passwords would let it use an IP address.)

The edgy pppd requires probably the * in the address field in pppd's chap-secrets file (was not the case in dapper).

Revision history for this message

Jozef Komenda (jozef-komenda) wrote on 2006-11-10:

Fix chap-secrets in knet Edit (464 bytes, text/plain)

The following patch fixes the problem for me.

However I'm not sure whether the RE in Opener::createAuthFile should not be changed as well for CHAP. Now it works because the entries in both pap-secrets and chap-secrets begin with the same pattern.

Revision history for this message

Lionel Le Folgoc (mrpouit) wrote on 2007-09-06:

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in knet:
status:	New → Incomplete

Revision history for this message

Ryan Kavanagh (ryanakca) wrote on 2008-03-10:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!