PPPoE keeps dropping/reconnecting

[Fire69]

Hi,

I was looking at my log because of a port forwarding problem (I'll make another topic about that... ) and discovered that my connection keeps dropping.

I hadn't really noticed anything because it immediately reconnects, but now that I tried a continuous ping I can see it time-out about every minute.
Here is a partial systemlog showing the drop/reconnect a couple of times

Code: [Select]

Oct 19 22:39:03 AlmondPlus daemon.warn pppd[26143]: LCP: timeout sending Config-Requests
Oct 19 22:39:03 AlmondPlus daemon.notice pppd[26143]: Connection terminated.
Oct 19 22:39:03 AlmondPlus daemon.notice pppd[26143]: Modem hangup
Oct 19 22:39:07 AlmondPlus daemon.err pppoe[26147]: Timeout waiting for PADO packets
Oct 19 22:39:07 AlmondPlus daemon.info pppd[26143]: Exit.
Oct 19 22:39:07 AlmondPlus daemon.notice pppoe-connect: PPPoE connection lost; attempting re-connection.
Oct 19 22:39:12 AlmondPlus daemon.notice pppd[26183]: pppd 2.4.4 started by root, uid 0
Oct 19 22:39:12 AlmondPlus daemon.info pppd[26183]: Using interface ppp0
Oct 19 22:39:12 AlmondPlus daemon.notice pppd[26183]: Connect: ppp0 <--> /dev/pts/0
Oct 19 22:39:43 AlmondPlus daemon.warn pppd[26183]: LCP: timeout sending Config-Requests
Oct 19 22:39:43 AlmondPlus daemon.notice pppd[26183]: Connection terminated.
Oct 19 22:39:43 AlmondPlus daemon.notice pppd[26183]: Modem hangup
Oct 19 22:39:47 AlmondPlus daemon.err pppoe[26187]: Timeout waiting for PADO packets
Oct 19 22:39:47 AlmondPlus daemon.info pppd[26183]: Exit.
Oct 19 22:39:47 AlmondPlus daemon.notice pppoe-connect: PPPoE connection lost; attempting re-connection.
Oct 19 22:39:52 AlmondPlus daemon.notice pppd[26247]: pppd 2.4.4 started by root, uid 0
Oct 19 22:39:52 AlmondPlus daemon.info pppd[26247]: Using interface ppp0
Oct 19 22:39:52 AlmondPlus daemon.notice pppd[26247]: Connect: ppp0 <--> /dev/pts/0
Oct 19 22:40:21 AlmondPlus user.info sysinit: RECV Membership query   from 192.168.0.1     to 224.0.0.1
Oct 19 22:40:23 AlmondPlus daemon.warn pppd[26247]: LCP: timeout sending Config-Requests
Oct 19 22:40:23 AlmondPlus daemon.notice pppd[26247]: Connection terminated.
Oct 19 22:40:23 AlmondPlus daemon.notice pppd[26247]: Modem hangup
Oct 19 22:40:27 AlmondPlus daemon.err pppoe[26251]: Timeout waiting for PADO packets
Oct 19 22:40:27 AlmondPlus daemon.info pppd[26247]: Exit.
Oct 19 22:40:27 AlmondPlus daemon.notice pppoe-connect: PPPoE connection lost; attempting re-connection.
Oct 19 22:40:32 AlmondPlus daemon.notice pppd[26312]: pppd 2.4.4 started by root, uid 0
Oct 19 22:40:32 AlmondPlus daemon.info pppd[26312]: Using interface ppp0
Oct 19 22:40:32 AlmondPlus daemon.notice pppd[26312]: Connect: ppp0 <--> /dev/pts/0
Oct 19 22:40:38 AlmondPlus user.info sysinit: RECV Membership query   from 192.168.1.1     to 224.0.0.1
Oct 19 22:40:39 AlmondPlus user.info sysinit: RECV V2 member report   from 192.168.1.7     to 239.255.255.250
Oct 19 22:40:39 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #0
Oct 19 22:40:41 AlmondPlus user.info sysinit: RECV V2 member report   from 192.168.1.5     to 239.255.255.250
Oct 19 22:40:41 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #0
Oct 19 22:40:43 AlmondPlus user.info sysinit: RECV V2 member report   from 192.168.1.8     to 224.0.0.1
Oct 19 22:40:43 AlmondPlus user.info sysinit: Updated route entry for 224.0.0.1 on VIF #0
Oct 19 22:40:47 AlmondPlus daemon.info hostapd: wlan00: STA 3c:a9:f4:0a:45:38 IEEE 802.11: associated
Oct 19 22:40:47 AlmondPlus daemon.info hostapd: wlan00: STA 3c:a9:f4:0a:45:38 RADIUS: starting accounting session 5442ED07-00000004
Oct 19 22:40:47 AlmondPlus daemon.info hostapd: wlan00: STA 3c:a9:f4:0a:45:38 WPA: pairwise key handshake completed (RSN)
Oct 19 22:40:47 AlmondPlus daemon.info dnsmasq-dhcp[4840]: DHCPREQUEST(br-lan) 192.168.1.21 3c:a9:f4:0a:45:38
Oct 19 22:40:47 AlmondPlus daemon.info dnsmasq-dhcp[4840]: DHCPACK(br-lan) 192.168.1.21 3c:a9:f4:0a:45:38 LaptopHPFire69Wifi
Oct 19 22:40:47 AlmondPlus user.info sysinit: RECV V2 member report   from 192.168.1.8     to 239.255.255.250
Oct 19 22:40:47 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #0
Oct 19 22:40:50 AlmondPlus user.info sysinit: RECV V2 member report   from 192.168.1.21    to 239.255.255.250
Oct 19 22:40:50 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #0
Oct 19 22:40:51 AlmondPlus user.info sysinit: RECV V2 member report   from 192.168.1.21    to 239.255.255.250
Oct 19 22:40:51 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #0
Oct 19 22:41:03 AlmondPlus daemon.warn pppd[26312]: LCP: timeout sending Config-Requests
Oct 19 22:41:03 AlmondPlus daemon.notice pppd[26312]: Connection terminated.
Oct 19 22:41:03 AlmondPlus daemon.notice pppd[26312]: Modem hangup
Oct 19 22:41:07 AlmondPlus daemon.err pppoe[26316]: Timeout waiting for PADO packets
Oct 19 22:41:07 AlmondPlus daemon.info pppd[26312]: Exit.
Oct 19 22:41:07 AlmondPlus daemon.notice pppoe-connect: PPPoE connection lost; attempting re-connection.
Oct 19 22:41:12 AlmondPlus daemon.notice pppd[26352]: pppd 2.4.4 started by root, uid 0
Oct 19 22:41:12 AlmondPlus daemon.info pppd[26352]: Using interface ppp0
Oct 19 22:41:12 AlmondPlus daemon.notice pppd[26352]: Connect: ppp0 <--> /dev/pts/0


[eldaria]

Since I do not have any possibility to test PPPoE I canät confirm if this is possible on the Almond+.

However, it seems to fail due to this error sincde there is some time before the previous log entry:
LCP: timeout sending Config-Requests

I did a google search and it seem you need to enable debug logging to see the actual error.
http://pptpclient.sourceforge.net/howto-diagnosis.phtml#lcp_timeout

[Fire69]

Thanks for the research, I'll try to find out how to add the logging when I get home.

[Fire69]

I've been looking around where to enable this logging, but I can't figure it out.
In the startup, you have pppoe-client and pptpd.

As far as I can find (I'm no genie with linux...) pppoe-client has no config-file.
pptpd has a config file in /etc/ppp/options.pptp

Do I have to add something there to enable logging?

[edit]
Hm, just noticed in OpenWRT - startup of pptpd is disabled.  Does that mean that it's not used for the pppoe-connection?

[eldaria]

Well not sure either, but I had a look in the /etc/ppp directory and in one of the files (options) there is this:

Code: [Select]

#debug
logfile /dev/null

Try to change that to:

Code: [Select]

debug
logfile /tmp/ppp.log

Note that I set the logfile to save to a tempfs with only a few hundred megs available, so do monitor the file so it does not grow out of proportion, I have no idea how much data the debug writes.

You can use:

Code: [Select]

tail -f /tmp/ppp.log
to see a live stream of changes to the file.

[Fire69]

Here is the log-file:
http://pastebin.com/zMqHGTkF

As you can see, it is really constant in the connect/disconnect-cycle...

[LGNilsson]

We're running PPPoE here in the office and we haven't had any problems like that.
Can you please provide details about the specific modem/router you're using as well as the service provider?

[Fire69]

My provider is Belgacom (Belgium) and the router is an BBOX3.
On the BBOX3 I disabled the wifi and the PPPoE.
It's connected through a VDSL 30Mbit.
The A+ is connected to a LAN-port and is given a 192.168.0.x-address.

I will try to contact some Belgacom-technicians (I work there ;-) ) and see if I can get more info about the PPPoE-connection...

[eldaria]

So it looks as if you get a connection, and it seems you do not get GRE packets and then the connection get terminated.
http://pptpclient.sourceforge.net/howto-diagnosis.phtml#client_no_gre_rx

Again I'm just reading what it says on that page, but they seem to have good documentation for troubleshooting. :-)

[LGNilsson]

Wow, that looks like a Nest smoke alarm... in a bad way...
That said, it should be working, so not quite sure what's going on.

[Fire69]

Well, I spoke to guy responsible of testing the bbox3 and it's firmwares, apparently I'm not the first complaining about this problem.
So either it has nothing to do with the A+ or it's the combination of my isp with some routers that implement something in a different way

I'm taking the A+ with me tomorrow and they are going to do some tests with it.

I'll keep you guys up to date.

[LGNilsson]

Interesting, let us know what the outcome is, especially if we need to add some specific support for something or the other.

[Fire69]

I took the A+ to work with me today.  Before giving it to the team that was going to investigate the problem, I connected it to the BBOX3 at my desk.
Result => no pppoe being dropped!!

So before they were going to spend their time on checking logs and so, they asked me to test at home with another modem to be sure it was not my modem causing the problem.
If was planning on doing that this weekend, for now I connected everything as it was.

I've been checking the logs now for the past 30 minutes => no dropped pppoe!!!
In other words, nothing changed but the problem is gone...

[Kit]

Same issue reported by my ISP here. The PPPoE seems to drop its connection once it is connected, making connection impossible.