From: Sven Kirmess <sven.kirmess@kzone.ch>
To: linux-ppp@vger.kernel.org
Subject: Re: Starting dhcpcd terminates the established PPPoE connection
Date: Thu, 29 Dec 2016 11:35:22 +0000 [thread overview]
Message-ID: <CAMBnWDh0p60inpNyt2viaSCC5RahGxoTk05y2snzE0wg-LOjdw@mail.gmail.com> (raw)
In-Reply-To: <CAMBnWDj4zppEWV4i0ekcNmgbEDP_eVENBkKDEjFHUP8ZJYZi=w@mail.gmail.com>
Hi James,
Thanks for looking into this.
On Wed, Dec 28, 2016 at 6:20 PM, James Carlson <carlsonj@workingcode.com> wrote:
> 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've added the log files to dropbox. I've rebooted the system at 01:39
and at 01:59.
<https://www.dropbox.com/s/k6s70fzl7ee4o42/daemon.txt?dl=0>
<https://www.dropbox.com/s/1h6mqvcxvstvf4y/debug.txt?dl=0>
<https://www.dropbox.com/s/msg66lt19f95772/kern.txt?dl=0>
<https://www.dropbox.com/s/lnm6aw5fzskq0d4/ppp.txt?dl=0>
<https://www.dropbox.com/s/qxcx7wm4yj7qhr5/syslog.txt?dl=0>
I was able to bring the line back up after I've removed the ip-up
script that starts/stops dhcpcd.
> 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?
I can't see anything.
Sven
next prev parent reply other threads:[~2016-12-29 11:35 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 [this message]
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:
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=CAMBnWDh0p60inpNyt2viaSCC5RahGxoTk05y2snzE0wg-LOjdw@mail.gmail.com \
--to=sven.kirmess@kzone.ch \
--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).