archive mirror
 help / color / mirror / Atom feed
From: James Carlson <>
Subject: Re: Starting dhcpcd terminates the established PPPoE connection
Date: Wed, 28 Dec 2016 17:20:01 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12/27/2016 6:26 PM, Sven Kirmess wrote:
>>From /var/log/ppp.log:
> Dec 25 02:26:56 kaldra pppd[8185]: rcvd [LCP TermReq id=0x2]
> Dec 25 02:26:56 kaldra pppd[8185]: LCP terminated by peer
> Dec 25 02:26:56 kaldra pppd[8185]: Connect time 1.0 minutes.

It wouldn't be a bad thing to see what led up to this point, but I
suspect there isn't much more information available on this side.  A
good implementation of PPP uses the optional disconnection message in
LCP Terminate-Request to report the reason why the connection is being
dropped.  Unfortunately, the PPP implementation used by your peer isn't
good, and it doesn't do that.

It's remotely possible that the disconnection is unrelated to DHCP and
that it's just coincidence.  That's why I suggested posting more of the
logs.  But I think it's just a very remote possibility.

I'm afraid that most likely means that you need to talk with your ISP
and find out if they have logs or error messages to share with you.  My
experience with most of these ISPs, though, is that there's nobody home
at the other end, and the only thing you can really do is quit and find
a better one.

Your mileage may vary.

> Dec 25 02:26:57 kaldra pppd[8185]: Failed to disconnect PPPoE socket:
> 114 Operation already in progress

Besides this apparently spurious error message, did the PPPoE client log
any sort of message about the disconnection?

James Carlson         42.703N 71.076W         <>

  reply	other threads:[~2016-12-28 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27 23:26 Starting dhcpcd terminates the established PPPoE connection Sven Kirmess
2016-12-28 17:20 ` James Carlson [this message]
2016-12-29 11:35 ` Sven Kirmess
2016-12-29 20:37 ` James Carlson
2016-12-31 13:45 ` Sven Kirmess
2016-12-31 19:24 ` 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:

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

  git send-email \ \ \ \

* 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).