lost pppoe configuration on reboot

[Patrice Vetsel]

After a reboot my pppoe configuration don't work.
Go to root xterm and :
satori:/home/kagou# pon
/usr/sbin/pppd: In file /etc/ppp/peers/provider: unrecognized option '/dev/modem'
satori:/home/kagou#

So i re-launch pppoeconf to have Internet access.
For informations pppoeconf remember my last entry.

[Matt Zimmerman (mdz)]

What does:

ls -l /dev/modem

show after you run pppoeconf?

[Patrice Vetsel (vetsel-patrice)]

satori:/home/kagou# ls -l /dev/modem
ls: /dev/modem: Aucun fichier ou répertoire de ce type
satori:/home/kagou#

[Matt Zimmerman (mdz)]

I need for you to restate the bug more clearly. This is what I think you are
saying:

1. You run pppoeconf, configure your connection
2. You run pon, and it works
3. You reboot
4. You run pon, and it does not work
5. You run pppoeconf, configure your connection again
6. You run pon, and it works

Is that correct?

Please send:

- a copy of /etc/ppp/peers/provider
- output from the "dmesg" command

at a time when you have run pppoeconf and your connection is working.

[Patrice Vetsel (vetsel-patrice)]

It's exact.
var/log/message:
Sep 12 19:37:33 localhost kernel: hdc: lost interrupt
Sep 12 19:37:45 localhost last message repeated 2 times
sep 12 19:37:51 localhost gconfd (root-5194): démarrage (version 2.7.92), pid
5194 utilisateur « root »
sep 12 19:37:51 localhost gconfd (root-5194): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration
source at position 0
sep 12 19:37:51 localhost gconfd (root-5194): Resolved address
"xml:readwrite:/root/.gconf" to a writable configuration source at position 1
sep 12 19:37:51 localhost gconfd (root-5194): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source
at position 2
Sep 12 19:37:51 localhost kernel: hdc: lost interrupt
Sep 12 19:38:03 localhost last message repeated 2 times
Sep 12 19:38:03 localhost kernel: CSLIP: code copyright 1989 Regents of the
University of California
Sep 12 19:38:03 localhost kernel: PPP generic driver version 2.4.2
Sep 12 19:38:03 localhost hal.hotplug[5216]: waiting for ppp info at /class/ppp/ppp
Sep 12 19:38:03 localhost hal.hotplug[5216]: Dont know how to wait for ppp at
/class/ppp/ppp; sleeping 1000 ms
Sep 12 19:38:03 localhost kernel: NET: Registered protocol family 24
Sep 12 19:38:04 localhost hal.hotplug[5243]: waiting for firmware info at
/class/firmware/0000:00:0a.0
Sep 12 19:38:04 localhost hal.hotplug[5243]: Dont know how to wait for firmware
at /class/firmware/0000:00:0a.0; sleeping 1000 ms
Sep 12 19:38:05 localhost kernel: NET: Registered protocol family 17
Sep 12 19:38:09 localhost kernel: hdc: lost interrupt
Sep 12 19:38:27 localhost last message repeated 3 times
Sep 12 19:38:32 localhost pppd[5382]: Plugin rp-pppoe.so loaded.
Sep 12 19:38:32 localhost pppd[5382]: RP-PPPoE plugin version 3.3 compiled
against pppd 2.4.2
Sep 12 19:38:32 localhost pppd[5383]: pppd 2.4.2 started by root, uid 0
Sep 12 19:38:33 localhost pppd[5383]: PPP session is 5649
Sep 12 19:38:33 localhost pppd[5383]: Using interface ppp0
Sep 12 19:38:33 localhost pppd[5383]: Connect: ppp0 <--> eth1
Sep 12 19:38:33 localhost pppd[5383]: Couldn't increase MTU to 1500
Sep 12 19:38:33 localhost pppd[5383]: Couldn't increase MRU to 1500
Sep 12 19:38:33 localhost hal.hotplug[5393]: waiting for net info at /class/net/ppp0
Sep 12 19:38:33 localhost hal.hotplug[5393]: Dont know how to wait for net at
/class/net/ppp0; sleeping 1000 ms
Sep 12 19:38:33 localhost pppd[5383]: Couldn't increase MRU to 1500
Sep 12 19:38:33 localhost pppd[5383]: CHAP authentication succeeded
Sep 12 19:38:33 localhost pppd[5383]: peer from calling number 00:90:1A:41:04:2E
authorized
Sep 12 19:38:33 localhost kernel: hdc: lost interrupt
Sep 12 19:38:33 localhost pppd[5383]: local IP address 83.113.108.63
Sep 12 19:38:33 localhost pppd[5383]: remote IP address 193.253.160.3
Sep 12 19:38:33 localhost pppd[5383]: primary DNS address 80.10.246.130
Sep 12 19:38:33 localhost pppd[5383]: secondary DNS address 80.10.246.3

dmesg :
17, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI h...

[Matt Zimmerman (mdz)]

It sounds like something is creating a /dev/modem symlink (which allows it to
work temporarily), but of course this is lost when rebooting. I do not have a
PPPoE connection to use to test this, nor do I see any code responsible for
doing this.

Given your configuration, /dev/modem must exist at some point, or it would not
work for you at all

[Patrice Vetsel (vetsel-patrice)]

When my pppoe configuration is on, I do not have any /dev/modem link.

May be there is a problem with the presence of a winmodem (not configured at
all) on the main board of my notebook ?!

[Matt Zimmerman (mdz)]

Well, we need to find out what is changing when you reboot which causes it to
stop working. Perhaps you can check the ppp command line (ps aux | grep ppp) in
these two cases and see if they differ

[Patrice Vetsel (vetsel-patrice)]

After a configuration with pppoeconf if i use poff, pon don't work, with the
same error.

pon launch ppp_on_boot
ppp_on_boot is a link to ppp_on_boot.dsl
But ppp_on_boot.dsl is not present. I think that this is the file who launch
pppd with dsl-provider. So pppd use the default provider who is not configured.

[Patrice Vetsel (vetsel-patrice)]

This not really a bug .....
I do not have the pppoe package installed !!! So the link
ppp_on_boot->ppp_on_boot.dsl can't work because ppp_on_boot.dsl is provided by
pppoe.
Now all is working
Please verify that pppoe is well installed by default.

If yes, so you can close this bug report.
Thanks

[Patrice Vetsel (vetsel-patrice)]

If pppoeconf is installed i think he must require pppoe package.

[Matt Zimmerman (mdz)]

The pppoe package should not be required, as the ppp package now supports pppoe.
 It sounds like pppoeconf is not properly supporting that configuration, though
I think it is supposed to in the current version

[Bronsen (housetier-deactivatedaccount)]

Does using "pon dsl-provider" work? if so, you could symlink
/etc/ppp/peers/provider to /etc/ppp/peers/dsl-provider. IIRC "pppoeconf" creates
a "dsl-provider"...

hth

[Patrice Vetsel (vetsel-patrice)]

Created an attachment (id=127)
my hacked pppoeconf

[Patrice Vetsel (vetsel-patrice)]

(From update of attachment 127)
This pppoeconf works.
"pon" "poff" "/etc/init.d/ppp start" works too.

The only problem is that on boot the connection is not established

[Patrice Vetsel (vetsel-patrice)]

(From update of attachment 127)
(From update of attachment 127 [edit])
This pppoeconf hacked by me works.
"pon" "poff" "/etc/init.d/ppp start" works too.

The only problem is that on boot the connection is not established

[Patrice Vetsel (vetsel-patrice)]

I think that the problem came from hal.
With debug mode on i hav this :
Sep 20 19:29:07 satori pppd[5366]: Plugin rp-pppoe.so loaded.
Sep 20 19:29:07 satori pppd[5366]: RP-PPPoE plugin version 3.3 compiled against
pppd 2.4.2
satori pppd[5367]: pppd 2.4.2 started by root, uid 0
satori pppd[5367]: PPP session is 6907
satori pppd[5367]: Using interface ppp0
satori pppd[5367]: Connect: ppp0 <--> eth1
satori pppd[5367]: Couldn't increase MTU to 1500
satori pppd[5367]: Couldn't increase MRU to 1500
satori hal.hotplug[5375]: waiting for net info at /class/net/ppp0
Sep 20 19:29:08 satori hal.hotplug[5375]: Dont know how to wait for net at
/class/net/ppp0; sleeping 1000 ms

[Patrice Vetsel (vetsel-patrice)]

Created an attachment (id=132)
New pppoeconf

New version.
Create ppp_on_boot.dsl like the pppoe package does.

Always the problem with hal (i suppose) on boot

[Patrice Vetsel (vetsel-patrice)]

It seem's that with the last modifications of pppoeconf, all is working.

[Matt Zimmerman (mdz)]

Before, the pppoe package provided a program to implement pppoe, and also a
script /etc/ppp/ppp_on_boot.dsl which loaded the module.

Now, the ppp package provides a plugin for pppd which implements pppoe, and
/etc/ppp/ppp_on_boot.dsl is missing. pppoeconf configures the system as if
it is present, though, and this is why it doesn't work.

The file needs to move out of the obsolete pppoe package into a modern
package (probably ppp itself). The problem is that the file is a dpkg
conffile owned by pppoe. This means that it is difficult to manage a
transition with the traditional mechanisms, due to conffile syntax (even if
the pppoe package is removed, the file remains).

Given that conffile transitions are awkward, I think we should just rename the
file to something else, and pppoeconf modified to use that name. Sound good?

[Patrice Vetsel (vetsel-patrice)]

Yes, you are right.

[Matt Zimmerman (mdz)]

OK, the solution seems pretty clear now; Daniel, please implement it

[Daniel Stone (daniels)]

I'll rename it to pppoe_on_boot.

[Daniel Stone (daniels)]

Fixed in ppp 2.4.2+20040428-2ubuntu2/pppoeconf 1.0.8ubuntu2.

[Cory Seefurth (cseefurth)]

I am still having this issue. My configuration is not saved after reboot.

Running
ppp 2.4.2+20040428-2ubuntu2
pppoeconf 1.0.8ubuntu2.

pppoe_on_boot does exists, which I believe is good, but ppp_on_boot also exists
and points to /etc/ppp/ppp_on_boot.dsl (broken link).

I also receive this message after running pppoeconf:

ubuntu:/home/cory# pppoeconf
ln: `/etc/ppp/ppp_on_boot': File exists
Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2
ubuntu:/home/cory# ls -l /dev/modem

[Daniel Stone (daniels)]

Fixed in 2.4.2+20040428-2ubuntu5.

[Cory Seefurth (cseefurth)]

Works - thanks

Is this something that needs to be changed in the installer for the release?

Thanks again. Great distro