[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJht_ENiEi1u-fNuE+3NSBY=3BOWL4cC8ndJAH04f-jBR-CW1w@mail.gmail.com>
Date: Fri, 6 Nov 2020 03:25:02 -0800
From: Xie He <xie.he.0141@...il.com>
To: David Laight <David.Laight@...lab.com>
Cc: Arnd Bergmann <arnd@...nel.org>, Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>, Martin Schiller <ms@....tdt.de>,
Andrew Hendry <andrew.hendry@...il.com>,
Linux X25 <linux-x25@...r.kernel.org>
Subject: Re: [PATCH net-next] net: x25_asy: Delete the x25_asy driver
On Fri, Nov 6, 2020 at 1:03 AM David Laight <David.Laight@...lab.com> wrote:
>
> Hmmm.... LAPB would expect to have an X.25 level 3 and maybe ISO
> transport (class 0, 2 or 3) sat on top of it.
I actually used AF_PACKET sockets to transport data directly over LAPB
and it worked.
LAPB doesn't need anything from layer 3. It just sees the layer 3
packets as a sequence of packets, numbers them and reliably transports
them in order. It doesn't read the internal contents of the packets.
Powered by blists - more mailing lists