From: David Laight <David.Laight@ACULAB.COM>
To: "'Dimitrios P. Bouras'" <dimitrios.bouras@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH 1/1] eth: Transparently receive IP over LLC/SNAP
Date: Sat, 5 Mar 2022 07:02:26 +0000 [thread overview]
Message-ID: <4baebbcb95d84823a7f4ecbe18cbbc3c@AcuMS.aculab.com> (raw)
In-Reply-To: <462fa134-bc85-a629-b9c5-8c6ea08b751d@gmail.com>
From: Dimitrios P. Bouras
> Sent: 05 March 2022 00:33
>
> Practical use cases exist where being able to receive Ethernet packets
> encapsulated in LLC SNAP is useful, while at the same time encapsulating
> replies (transmitting back) in LLC SNAP is not required.
I think you need to be more explicit.
If received frames have the SNAP header I'd expect transmitted ones
to need it as well.
> Accordingly, this
> is not an attempt to add full-blown support for IP over LLC SNAP, only a
> "hack" that "just works" -- see Alan's comment on the the Linux-kernel
> list on this subject ("Linux supports LLC/SNAP and various things over it
> (IPX/Appletalk DDP etc) but not IP over it, as it's one of those standards
> bodies driven bogosities which nobody ever actually deployed" --
> http://lkml.iu.edu/hypermail/linux/kernel/1107.3/01249.html).
IP over SNAP is needed for Token ring networks (esp. 16M ones) where the
mtu is much larger than 1500 bytes.
It is all too long ago though, I can't remember whether token ring
tends to bit-reverse the MAC address (like FDDI does) which means you
can't just bridge ARP packets.
So you need a better bridge - and that can add/remove some SNAP headers.
...
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-03-05 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 0:33 [PATCH 1/1] eth: Transparently receive IP over LLC/SNAP Dimitrios P. Bouras
2022-03-05 7:02 ` David Laight [this message]
2022-03-06 21:09 ` Dimitrios Bouras
2022-03-07 16:08 ` Stephen Hemminger
2022-03-07 17:45 ` Dimitrios Bouras
2022-03-07 18:10 ` Stephen Hemminger
2022-03-07 18:19 ` Dimitrios Bouras
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=4baebbcb95d84823a7f4ecbe18cbbc3c@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=davem@davemloft.net \
--cc=dimitrios.bouras@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@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).