linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPP cycling between UP and DOWN
Date: Mon, 08 Jun 2020 17:15:48 +0000	[thread overview]
Message-ID: <c3e9fab3-116c-ee26-cfa7-7fb7c76c7c4c@workingcode.com> (raw)
In-Reply-To: <f44e7e14-1621-7141-66a3-3a2218e8db86@mahan.org>

On 2020-06-08 13:04, Patrick Mahan wrote:
> On 5/28/20 6:59 AM, James Carlson wrote:
>> That's the most likely case.  It would help to have _complete_ debug
>> logs showing what's happening.
[...]
>> It sounds like a stretch to me.  A debug log would show for sure, though.
[...]
>> This doesn't sound likely to me.  But, again, debug logs are your friend
>> here.
>>
>> Use the pppd 'debug' option.  By itself, that'll write the log
>> information to syslog daemon.debug (be sure to redirect that to a file).
>>   Or use the "logfile /path/to/file" option to write the messages to a
>> file.  Then post those logs.
[...]
> I finally obtained the PPPoE logs from my customer.  I have redacted the
> IP addresses.  This is where I think we get the UP-->DOWN-->UP that is
> causing my issue.  Oddly, the customer has not experienced another event
> of this nature since then.
> 
> Here is the log with my annotations:
> 
> Executing pppd w/plugin(/etc/ppp/plugins/rp-pppoe.so): '/usr/sbin/pppd
> plugin /etc/ppp/plugins/rp-pppoe.so nic-wan0  unit 0 noipdefault noauth
> default-asyncmap defaultroute hide-password nodetach  mtu 1492 mru 1492
> noaccomp nodeflate nopcomp novj novjccomp user w29ddnjt@bizf.ocn.ne.jp
> lcp-echo-interval 20 lcp-echo-failure 3 '

The one option that's not included in the list above is "debug".

> local  IP address XX.XX.XX.XX
> remote IP address YY.YY.YY.YY
> 
> NOTE: This is where the first ip-up callout was triggered.

This looks like normal start-up.

> Connect time 0.1 minutes.
> Sent 0 bytes, received 10 bytes.
> 
> NOTE: This is where I think the ip-down callout was triggered.

This looks like it could be a normal tear-down of some sort.  Without
debug information, we're not going to be able to say a whole lot more
about this.  (Crucially, a debug log would likely show which side
initiated the tear-down.)

> sifdefaultroute(unit=0, ouraddr=XX.XX.XX.XX, gateway=YY.YY.YY.YY)
> local  IP address XX.XX.XX.XX
> remote IP address YY.YY.YY.YY
> 
> NOTE: This is where I think the second ip-up callout was triggered.
> 
> Modem hangup
> Connect time 1629.1 minutes.
> Sent 572 bytes, received 452067 bytes.
> Connection terminated.
> PPPoE shutdown on interface 'ppp0', exit status is '16'

"Modem hangup" means that PPPoE, not PPP, shut down this link.  It would
be a completely wild guess -- I know the pppd code fairly well, but I
don't know the separate rp-pppoe code too well at all -- but it's
possible that this user was bit by the same stray PADT problem that
someone reported earlier on this list.  Or maybe not.

Assuming that "Modem hangup" is the problem we're worried about here
(I'm not 100% sure at this point), the next thing to do would be to
debug the PPPoE stuff.  The Roaring Penguin guys would probably know
more about that, but, personally, my first action would be to use
something like wireshark to capture the traffic on the Ethernet itself,
and use that to find out what happens to shut down the link.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

  parent reply	other threads:[~2020-06-08 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 19:16 PPP cycling between UP and DOWN Patrick Mahan
2020-05-28 13:59 ` James Carlson
2020-05-28 17:54 ` Patrick Mahan
2020-06-08 17:04 ` Patrick Mahan
2020-06-08 17:15 ` James Carlson [this message]
2020-06-08 21:32 ` David Balažic
2020-06-08 22:51 ` Patrick Mahan
2020-06-08 22:52 ` Patrick Mahan
2020-06-09 18:03 ` 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=c3e9fab3-116c-ee26-cfa7-7fb7c76c7c4c@workingcode.com \
    --to=carlsonj@workingcode.com \
    --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;
as well as URLs for NNTP newsgroup(s).