Re: IP over 802.2 with LLC/SNAP
Alan Cox <[email protected]> Wed, 27 Jul 2011 13:32:09 +0100
| Newsgroups | gmane.linux.network,gmane.linux.kernel,gmane.linux.network.general |
|---|---|
| Message-ID | <[email protected]> |
> 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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html