From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alan Ott <alan@signal11.us>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: IP over 802.2 with LLC/SNAP
Date: Wed, 27 Jul 2011 13:32:09 +0100 [thread overview]
Message-ID: <20110727133209.0d9dd6c4@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <4E2F8B7B.80906@signal11.us>
> 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.
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.
You are about the first person in the known universe to care 8). Now
there isn't any reason for not supporting it. The receive side is a case
of using register_snap_client() and piping the frames into the IP stack.
The send side could be tackled two ways I can see, one would be to allow
for snap protocols to be set somehow on devices and routes, the other
that might be simply would be to create a 'snapifier' device that added
snap headers then routed the frame via the bound physical device as
802.2 LLC. That way you'd be able to do
route add gould-relic dev snap0
In both cases you'd need to tackle ARP but that seems to need no
configuration as SNAP requests get SNAP replies, and so on.
It should be a 'simple matter of hacking' and there are example devices
that fiddle with packets and add headers etc you can nick a lot of code
from. I figure if you can write an IP stack for an ancient Gould system
you can probably do that.
The other way is to use the Linux raw packet interfaces, open a raw
socket, push a BPF filter onto it to just get the frames for IP/SNAP and
ARP/SNAP then modify them and feed them to the kernel tun/tap interface.
Alan
next prev parent reply other threads:[~2011-07-27 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 3:52 Alan Ott
2011-07-27 5:13 ` Ben Pfaff
2011-07-27 12:32 ` Alan Cox [this message]
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=20110727133209.0d9dd6c4@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@signal11.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.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
all inboxes | Powered by JetHome®