pppoe broken in dapper

[eze80]

- Install Kubuntu Breezy
- Install pppoe -> Internet connection works.
- apt-get update/upgrade
- reboot
- pppoe stops working, must run pppoeconf again
- After running for a few seconds the connection stops working, active downloads keep working until they finish but no new connections can be made.
- sudo poff -a / sudo pon dsl-providers solves the problem but only for a few more seconds.

I don't know if this is related to a reported dhclient bug, this message keeps appearing in syslog:

localhost dhclient bound to 10.0.0.3 -- renewal in 27 seconds.
localhost dhclient DHCPACK from 10.0.0.2
localhost dhclient DHCPREQUEST on eth0 to 10.0.0.2 port 67

[eze80 (ezequiel-pozzo)]

This is the file generated by pppoeconf

[eze80 (ezequiel-pozzo)]

More info, I'm back to breezy now, I've notices that the resolv.conf file only had the adress 10.0.0.2 in dapper and not my isp dns servers.....

[Medya (medya)]

have ADSL internet ,I have ethernet modem with LAN Card.

it worked so beautifully in Breezy , and it worked well in LIVE CD and in first boot of Dapper .but now it wont connect to internet anymore

I have collected some infromation that u may use it to fix it.

1- the Net Speed shows my internet as a PPP (dail up) while it used to show it as ETH0 in my breezy and I cant not change it to eth0 (as I was able to do in Breezy)

2- I can connet to internet by some tricks ,
I connect to a SSH PROXY , with this command
ssh -L 8213:localhost:8213 fred@205.234.206.139

and I force programs to use that proxy (localhost:8213)... (but the proxies are slow you know... and I cant force all the programs to use proxy)
so I DO HAVE INTERNET but the ubuntu dapper doenst know how to use it...

I think u can find the problem .... by this thing that I found out .

3- on dapper's start up it takes much time in Configuring Netwrok interface there should be a problem there

I hope my information help you to solve this problem.

[peter (peter-row)]

Had trouble with pppoe. Worked for a bit, then when I rebooted again it stopped working.

Got it to back by opening and closing things, deactivating my ethernet, running pppoeconf again, reactivating ethernet ... guess my time on other operating systems counts for something.

[Gabriel de O. Padoan (gabriel.padoan)]

Here, in Ubuntu Dapper, I configured the pppoe, and get some secods of connection. After this, I lose my connection, and the plog command shows "Modem Hangup". In breezy I don't have any problem. But when I try to upgrade to Dapper, holding the kernel and pppoe, this broke my system. Now, I have no sound, internet and printer devices. I'm Using the Breezy Live now.

[Medya (medya)]

why this bug is not confirmed, I am in pain I have to run these commands everytime I start up to connect to internet... thats painfull .

sudo poff -a
sudo pppoeconf

why u cant solve this problem...

[David K (haldav)]

- running an HP lappie with D-link pcmcia ethernet card recognized as eth0
- ran pppoeconf ok from root
-first time internet connection worked and thought all was fine
- after computer re-booted, no internet connection
- ran pon dsl-provider, no internet
- ran plog and got:

Plugin rppppoe.so loaded.
pppd 2.4.4b1 started by root, uid 0
PPP session is 3182
Using interface ppp1
Connect: ppp1 <> eth0
PAP authentication failed

- repeatedly used pon and poff dsl-provider to toggle the connection
- interface changed from ppp1 to ppp2 to ppp3 to ppp4 (not sequentially, though). I have only one ethernet installed (the d-link)
- finally, internet connection was established when interface toggled to ppp0, which seems to match with the same number designation for my ethernet:

PPP session is 3234
Using interface ppp0
Connect: ppp0 <> eth0
PAP authentication succeeded

My internet connection CONSISTENTLY works when "ppp0 <> eth0". Under this situation, PAP authentication always succeeds. Is there a way to force Ubuntu Dapper to use only "ppp0"? I think this would solve my problem. Furthermore, I tried the fixes found on https://help.ubuntu.com/commuunity/adslpppoe
involved changing "interfaces" file under /etc/network
added lines as was suggested. still a no-go.

so.........any ideas?

Presently, my "interfaces" file reads as follows:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto dsl-provider
iface dsl-provider inet ppp
provider dsl-provider

pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf

perhaps someone can help me...my only ethernet card is eth0. do i need lines like "auto eth1" and "auto ath0" and "auto wlan0"? Are these lines buggering my connection? Also, should my "iface eth0 inet dhcp" line read "iface eth0 inet manual", and if so, what's the diff? I have given this Ubuntu thing one more week, after which I will return to (egads) windows. All I need is a bloody INTERNET connection!

[istoyanov (istoyanov)]

I have experienced exactly the same problem as David, and I *suggest* that it could be somehow connected with the absence of an option equivalent to "SERVICENAME=xxx" in rp-pppoe. I've got this idea while triggering my connection numerous times with "pon dsl-provider -d", and during these attepmts I have noticed that the service name in "PADS: Service-name: 'XXX'" (as visible in the log) has been predominantly "LAN" (connection *failed*), a few times empty (i.e. ' '; connection *failed* again), and only two times until now it has been equivalent to the service name required by the ISP in order to connect (connection *successful*). Therefore I wonder if there is a way to specify the service name explicitly somewhere in the configuration files to test my hypothesis. Or could this be interpreted as a misconfiguration of the ISP infrastructure?

Thank you in advance!

[istoyanov (istoyanov)]

Well, my previous comment turned out to be a result of a misconfiguration, rather than a bug.

I had to put the following line in my /etc/ppp/peers/dsl-provider:

plugin rp-pppoe.so rp_pppoe_service <the_service_name> eth0

NOTE: actually, it was only the "rp_pppoe_service <...>" part that was necessary to be inserted.

Afterwards, I was able to connect to the ISP at wish, without any problems.