Linux PPP protocol development
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: linux-ppp@vger.kernel.org
Subject: pppoe uplink goes down several times a day, what is wrong
Date: Mon, 21 Dec 2009 13:15:08 +0000	[thread overview]
Message-ID: <4B2F74DC.4040204@powercraft.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 851 bytes --]

Hello everybody,

I got a PPPoE uplink to a big Dutch internet service provider, and I
am having stability issues. My uplink is going down for very short
times but it happens several times a day.

I just had major network move and the physical copper line changed so
I think I can rule out bad coper connections now. I had the same
issues on the old location though.

The modem I use is a DrayTek Vigor 3100V (latest firmware) in PPPoE
bridge mode (1) it behaves complete transparent, so I let the Linux
server do as much as possible.

I am wondering what I am doing wrong, is there something I should
change on the software side? Should I change the modem configuration?
Stop using PPPoE?

Please see the attachment for the configuration and debug information.

1) http://imagebin.ca/img/aSt5Wc-c.png

Any help is appreciated,

Best regards,

Jelle


[-- Attachment #2: setup-sammy-pppoe-debug01.txt --]
[-- Type: text/plain, Size: 4392 bytes --]

------------------------------------------------------------------------

# pppoe uplink goes down several times a day, what is going wrong?

------------------------------------------------------------------------

# grep -i pppd /var/log/syslog
Dec 21 06:37:24 sammy pppd[2954]: No response to 4 echo-requests
Dec 21 06:37:24 sammy pppd[2954]: Serial link appears to be disconnected.
Dec 21 06:37:24 sammy pppd[2954]: Connect time 2681.4 minutes.
Dec 21 06:37:24 sammy pppd[2954]: Sent 198282561 bytes, received 314194095 bytes.
Dec 21 06:37:30 sammy pppd[2954]: Connection terminated.
Dec 21 06:37:30 sammy pppd[2954]: Modem hangup
Dec 21 06:37:50 sammy pppd[2954]: PPP session is 6
Dec 21 06:37:50 sammy pppd[2954]: Using interface ppp0
Dec 21 06:37:50 sammy pppd[2954]: Connect: ppp0 <--> eth5
Dec 21 06:37:54 sammy pppd[2954]: PAP authentication succeeded
Dec 21 06:37:54 sammy pppd[2954]: peer from calling number 00:50:7F:DB:D3:48 authorized
Dec 21 06:37:54 sammy pppd[2954]: Cannot determine ethernet address for proxy ARP
Dec 21 06:37:54 sammy pppd[2954]: local  IP address 188.201.xxx.xxx
Dec 21 06:37:54 sammy pppd[2954]: remote IP address 62.12.4.28
Dec 21 06:37:54 sammy pppd[2954]: primary   DNS address 213.75.63.36
Dec 21 06:37:54 sammy pppd[2954]: secondary DNS address 213.75.63.70
Dec 21 08:32:56 sammy pppd[2954]: No response to 4 echo-requests
Dec 21 08:32:56 sammy pppd[2954]: Serial link appears to be disconnected.
Dec 21 08:32:56 sammy pppd[2954]: Connect time 115.1 minutes.
Dec 21 08:32:56 sammy pppd[2954]: Sent 10170461 bytes, received 28994956 bytes.
Dec 21 08:33:02 sammy pppd[2954]: Connection terminated.
Dec 21 08:33:02 sammy pppd[2954]: Modem hangup
Dec 21 08:33:22 sammy pppd[2954]: PPP session is 6
Dec 21 08:33:22 sammy pppd[2954]: Using interface ppp0
Dec 21 08:33:22 sammy pppd[2954]: Connect: ppp0 <--> eth5
Dec 21 08:33:27 sammy pppd[2954]: PAP authentication succeeded
Dec 21 08:33:27 sammy pppd[2954]: peer from calling number 00:50:7F:DB:D3:48 authorized
Dec 21 08:33:27 sammy pppd[2954]: Cannot determine ethernet address for proxy ARP
Dec 21 08:33:27 sammy pppd[2954]: local  IP address 188.201.xxx.xxx
Dec 21 08:33:27 sammy pppd[2954]: remote IP address 62.12.4.28
Dec 21 08:33:27 sammy pppd[2954]: primary   DNS address 213.75.63.36
Dec 21 08:33:27 sammy pppd[2954]: secondary DNS address 213.75.63.70

------------------------------------------------------------------------

# grep -i e1000 /var/log/syslog
Dec 21 06:35:19 sammy kernel: [557976.760139] e1000: eth5 NIC Link is Down
Dec 21 06:35:21 sammy kernel: [557978.616469] e1000: eth5 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Dec 21 06:35:24 sammy kernel: [557982.236149] e1000: eth5 NIC Link is Down
Dec 21 06:35:27 sammy kernel: [557984.468468] e1000: eth5 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Dec 21 08:30:41 sammy kernel: [564898.420139] e1000: eth5 NIC Link is Down
Dec 21 08:30:42 sammy kernel: [564900.372459] e1000: eth5 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Dec 21 08:30:46 sammy kernel: [564903.892134] e1000: eth5 NIC Link is Down
Dec 21 08:30:48 sammy kernel: [564906.156460] e1000: eth5 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX

------------------------------------------------------------------------

# cat /etc/ppp/peers/dsl-provider
# Minimalistic default options file for DSL/PPPoE connections

noipdefault
defaultroute
replacedefaultroute
hide-password
#lcp-echo-interval 30
#lcp-echo-failure 4
noauth
persist
#mtu 1492
maxfail 0
holdoff 20
plugin rp-pppoe.so eth5
usepeerdns
user "KPN1"

------------------------------------------------------------------------

# ifconfig -a ppp
ppp0      Link encap:Point-to-Point Protocol
          inet addr:188.201.124.57  P-t-P:62.12.4.28  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:614021 errors:0 dropped:0 overruns:0 frame:0
          TX packets:502294 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:691562515 (659.5 MiB)  TX bytes:67199257 (64.0 MiB)

------------------------------------------------------------------------

# cat /etc/network/interfaces
auto dsl-provider
  iface dsl-provider inet ppp
  pre-up /sbin/ifconfig eth5 up
  provider dsl-provider

------------------------------------------------------------------------


             reply	other threads:[~2009-12-21 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 13:15 Jelle de Jong [this message]
2009-12-21 13:49 ` pppoe uplink goes down several times a day, what is wrong James Carlson
2009-12-21 14:25 ` Jelle de Jong
2009-12-21 14:51 ` James Carlson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B2F74DC.4040204@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox