From: Alan Ott <alan@signal11.us>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: IP over 802.2 with LLC/SNAP
Date: Tue, 26 Jul 2011 23:52:27 -0400 [thread overview]
Message-ID: <4E2F8B7B.80906@signal11.us> (raw)
Hi,
What I have is a fairly straight-forward question, but takes a little
background to get there.
I have an ancient computer (Gould 3267) that I'm trying to interface
with both a Windows computer and an embedded Linux computer over
UDP/Ethernet. Since the Gould doesn't have any IP support, I have to
make the IP packet myself. Also, because of the way the Gould's Ethernet
driver works, sent packets all use the type/length field in the Ethernet
header to represent the length and therefore are unable to specify that
the packet contains IP data in the Ethernet header. To get around this,
I added an 802.2 LLC/SNAP header to my packet[1]. My packet looks good
in Wireshark, and I have it working well communicating with the Windows
PC. However, I can't seem to get Linux to recognize the packet as IP,
and thus I am unable to receive it using the normal socket interface on
the Linux system.
So the question is, does Linux support IP over 802.2 with LLC/SNAP? Is
there a sysfs/proc entry that I have to turn on to make this work (I
didn't find one)? I have the LLC2 module loaded, and I believe my packet
to be correct, since Windows recognizes it and since Wireshark doesn't
give any red flags on it. I've been unable to find anything about this
kind of thing in my searching.
I put a sample capture file of the packets I'm sending at [2] for those
interested.
Alan.
[1] So the packet looks like this:
Ethernet Header
LLC/SNAP header
IP Header
UDP Header
data
[2] www.signal11.us/~alan/testraw.pcap
next reply other threads:[~2011-07-27 3:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 3:52 Alan Ott [this message]
2011-07-27 5:13 ` IP over 802.2 with LLC/SNAP Ben Pfaff
2011-07-27 12:32 ` Alan Cox
2011-07-27 16:26 ` Rick Jones
2011-07-29 18:42 ` Alan Ott
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=4E2F8B7B.80906@signal11.us \
--to=alan@signal11.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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