Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Guillaume Nault <gnault@redhat.com>
To: Martin Zaharinov <micron10@gmail.com>
Cc: "Pali Rohár" <pali@kernel.org>,
"Greg KH" <gregkh@linuxfoundation.org>,
netdev <netdev@vger.kernel.org>,
"Eric Dumazet" <eric.dumazet@gmail.com>
Subject: Re: Urgent Bug report: PPPoE ioctl(PPPIOCCONNECT): Transport endpoint is not connected
Date: Wed, 11 Aug 2021 18:40:01 +0200 [thread overview]
Message-ID: <20210811164001.GA15488@pc-32.home> (raw)
In-Reply-To: <2B54E919-1263-4AD2-B37C-6B1F24211D77@gmail.com>
On Tue, Aug 10, 2021 at 09:27:14PM +0300, Martin Zaharinov wrote:
> Add Guillaume Nault
>
> > On 9 Aug 2021, at 18:15, Pali Rohár <pali@kernel.org> wrote:
> >
> > On Sunday 08 August 2021 18:29:30 Martin Zaharinov wrote:
> >>>>>> [2021-08-05 13:52:05.294] vlan912: 24b205903d09718e: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:05.298] vlan912: 24b205903d097162: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:05.626] vlan641: 24b205903d09711b: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:11.000] vlan912: 24b205903d097105: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:17.852] vlan912: 24b205903d0971ae: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:21.113] vlan641: 24b205903d09715b: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:27.963] vlan912: 24b205903d09718d: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:30.249] vlan496: 24b205903d097184: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:30.992] vlan420: 24b205903d09718a: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:33.937] vlan640: 24b205903d0971cd: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:40.032] vlan912: 24b205903d097182: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:40.420] vlan912: 24b205903d0971d5: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:42.799] vlan912: 24b205903d09713a: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:42.799] vlan614: 24b205903d0971e5: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:43.102] vlan912: 24b205903d097190: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:43.850] vlan479: 24b205903d097153: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:43.850] vlan479: 24b205903d097141: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:43.852] vlan912: 24b205903d097198: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:43.977] vlan637: 24b205903d097148: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
> >>>>>> [2021-08-05 13:52:44.528] vlan637: 24b205903d0971c3: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
The PPPIOCCONNECT ioctl returns -ENOTCONN if the ppp channel has been
unregistered.
From a user space point of view, this means that accel-ppp establishes
PPPoE sessions, starts negociating PPP connection parameters on top of
them (LCP and authentication) and finally the PPPoE sessions get
disconnected before accel-ppp connects them to ppp units (units are
roughly the "pppX" network devices).
Unregistration of PPPoE channels can happen for the following reasons:
* Changing some parameters of the network interface used by the
PPPoE connection: MAC address, MTU, bringing the device down.
* Reception of a PADT (PPPoE disconnection message sent from the peer).
* Closing the PPPoE socket.
* Re-connecting a PPPoE socket with a different session ID (this
unregisters the previous channel and creates a new one, so that
shouldn't be the problem you're facing here).
Given that this seems to affect all PPPoE connections, I guess
something happened to the underlying network interface (1st bullet
point).
next prev parent reply other threads:[~2021-08-11 16:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 20:53 Martin Zaharinov
2021-08-06 4:40 ` Greg KH
2021-08-06 5:40 ` Martin Zaharinov
2021-08-08 15:14 ` Martin Zaharinov
2021-08-08 15:23 ` Pali Rohár
2021-08-08 15:29 ` Martin Zaharinov
2021-08-09 15:15 ` Pali Rohár
2021-08-10 18:27 ` Martin Zaharinov
2021-08-11 16:40 ` Guillaume Nault [this message]
2021-08-11 11:10 ` Martin Zaharinov
2021-08-11 16:48 ` Guillaume Nault
2021-09-07 6:16 ` Martin Zaharinov
2021-09-07 6:42 ` Martin Zaharinov
2021-09-11 6:26 ` Martin Zaharinov
2021-09-14 6:16 ` Martin Zaharinov
2021-09-14 8:02 ` Guillaume Nault
2021-09-14 9:50 ` Florian Westphal
2021-09-14 10:01 ` Martin Zaharinov
2021-09-14 11:00 ` Florian Westphal
2021-09-15 14:25 ` Martin Zaharinov
2021-09-15 14:37 ` Martin Zaharinov
2021-09-16 20:00 ` Martin Zaharinov
2021-09-14 10:53 ` Martin Zaharinov
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=20210811164001.GA15488@pc-32.home \
--to=gnault@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=micron10@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pali@kernel.org \
--subject='Re: Urgent Bug report: PPPoE ioctl(PPPIOCCONNECT): Transport endpoint is not connected' \
/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
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).