From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Starting dhcpcd terminates the established PPPoE connection
Date: Sat, 31 Dec 2016 19:24:13 +0000 [thread overview]
Message-ID: <e6a858bd-b6a4-0630-f8b1-0257f51092ff@workingcode.com> (raw)
In-Reply-To: <CAMBnWDj4zppEWV4i0ekcNmgbEDP_eVENBkKDEjFHUP8ZJYZi=w@mail.gmail.com>
On 12/31/2016 8:45 AM, Sven Kirmess wrote:
> On Thu, Dec 29, 2016 at 9:37 PM, James Carlson <carlsonj@workingcode.com> wrote:
>
>> I don't see much that's special going on there. I still think the
>> problem is on the peer's side, not yours.
>
> That's going to be much more difficult to get fixed.
>
>> Does /libexec/dhcpcd-run-hooks do anything crazy, such as pkill?
>
> I can't find anything.
>
> Besides that, I've restarted dhcpcd and for now know it's working
> again. Without a change on my side.
>
> Thanks for your confirmation that it's probably not on my side.
>
One possibly interesting note is that I see LCP being renegotiated after
starting authentication. That's a dead give-away that the other side
has a front-end device that tunnels the PPP traffic back to back-end
servers.
The reason it works sometimes and not at other times could be that you
sometimes hit a broken (or misconfigured) back-end server, and other
times you hit one that's ok.
It could also be that someone on their side noticed the errors and fixed
something. You could be just that lucky. :-/
--
James Carlson 42.703N 71.076W <carlsonj@workingcode.com>
prev parent reply other threads:[~2016-12-31 19:24 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
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 [this message]
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=e6a858bd-b6a4-0630-f8b1-0257f51092ff@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).