Problems with PPPoE under Dapper

[email.listen at googlemail.com]

Am Sat, 4. March 2006 09:31 schrieb Mark Derricutt:
> Hi there,
>
> I just upgraded a home machine to dapper via apt-get to give it a bash and
> find that my PPPoE connections no longer last longer than 4-5 seconds.
>
> However, according to the ISP I'm properly connected.
>
> My logs show the following:
>
> Mar  3 07:58:54 spawn pppd[4888]: Timeout waiting for PADO packets
> Mar  3 07:59:05 spawn pppd[5289]: Plugin rp-pppoe.so loaded.
> Mar  3 07:59:05 spawn pppd[5292]: pppd 2.4.4b1 started by root, uid 0
> Mar  3 07:59:30 spawn pppd[5302]: Plugin rp-pppoe.so loaded.
> Mar  3 07:59:30 spawn pppd[5304]: pppd 2.4.4b1 started by root, uid 0
> Mar  3 07:59:40 spawn pppd[5292]: Timeout waiting for PADO packets
> Mar  3 07:59:55 spawn pppd[5095]: No response to 4 echo-requests
> Mar  3 07:59:55 spawn pppd[5095]: Serial link appears to be disconnected.
> Mar  3 07:59:55 spawn pppd[5095]: Connect time 3.5 minutes.
> Mar  3 07:59:55 spawn pppd[5095]: Sent 114327 bytes, received 564192 bytes.
> Mar  3 07:59:59 spawn pppd[5120]: Timeout waiting for PADO packets
> Mar  3 07:59:59 spawn pppd[5169]: Timeout waiting for PADO packets
> Mar  3 07:59:59 spawn pppd[5137]: Timeout waiting for PADO packets
> Mar  3 07:59:59 spawn pppd[5077]: Timeout waiting for PADO packets
> Mar  3 07:59:59 spawn pppd[5148]: Timeout waiting for PADO packets
> Mar  3 07:59:59 spawn pppd[5084]: Timeout waiting for PADO packets
> Mar  3 07:59:59 spawn pppd[4841]: Timeout waiting for PADO packets
> Mar  3 07:59:59 spawn pppd[4888]: Timeout waiting for PADO packets
> Mar  3 07:59:59 spawn pppd[4888]: Exit.
> Mar  3 08:00:01 spawn pppd[5095]: Connection terminated.
> Mar  3 08:00:01 spawn pppd[5095]: Modem hangup
> Mar  3 08:00:05 spawn pppd[5304]: Timeout waiting for PADO packets
>
> Everything worked fine with Breezy prior to the Dapper update, are there
> any known PPPoE issues currently in Dapper or any suggested routes I could
> try to fix, or further diagnose the problem?
>
> The rest of Dapper all loooks NICE and seems to be working fine, now if
> only I could get online with it again :)

It might be that the mru has to be set to a value less than 1500 (which is the 
default). 

Have a look to the file
 /etc/ppp/options 
there you will find a line 
 #mru 1470
Delete the comment sign (#) and try again to connect to your isp.


If this don't work there are two ways to isolate the problem.

1. you may reconfigure your pppoe connection by using pppoeconf
For this start pppoeconf and follow the instructions.

2. Have a closer look what eactly is going on during a connect.
For t his you have to capture the traffic of the ppp0 device by capturing the 
eth device ppoe is using. 

For this first stop your pppoe connection.
Open a terminal and become root typing
 sudo -s
Stop pppoe with
 poff -a
This should stop pppoe from running. You may check this with
 pidof pppd

Start ethereal as root.(You wil find it in the gnome-panel menu ' Internet -> 
Ethereal (as root)'
Set the capturing device to eth0 (or eth1, depends on the eth device ppoe is 
using).
If you don't know which eth device pppoe is using have a look to the file 
 /etc/ppp/peers/dsl-provider

You will find a line
 plugin rp-pppoe.so eth0
if pppoe uses eth0. It will be eth1 or another device if pppoe uses another 
eth device. (dsl-provider is the most common used name for pppoe connections, 
in some rare  cases, eg. you decided to use another name, it will be 
different. But it will always be a file in the /etc/ppp/peers/ directory)

Now open a terminal and start the connection with the command 
 pon dsl-provider 

Now ethereal will do the capturing. 
Then stop the capture and go to the menu entry 'File -> Export -> As plain 
text file' and export the capture as plain text.

Please place this capture file somwhere in the internet and post the url here. 
(If you don't be able to do this post it to the list)
The first  10 to 20 lines will be enough I would say.

Then we will have a closer look to figure out what may be the problem. 
BTW this capture file is also helpfull for your provider to find a problem. 
(The common used term for such a file is tracedump)

It will also be helpfull to know which isp you are using.

regards,
Thomas