At multiple levels on OSI, there are too many protocols on Ethernet. If you need to make my xray (a) Net support so much agreement, it is not a better way, so I have thought of one for the time being. By XML configuration plug-in, the following is the description of Ethernet Frame under my XRAY @ Net, XRAY @ Net extension class parsed similar to these XMLs and cache to memory, when unpacking, The PORT NUT NUMBER of the current Packet is determined in the Ethernet frame unpacking thread, then determines the protocol type, and then confirms the next layer of protocol type.
Write so much first, I am learning Etherpeek, etherpeek is relatively smart, its display may use XSLT. Interested in discussing.
// etNumber.xml -> Ethernet frame type definition.
"ECMA Internet" = "Xerox" /> Number decimal = "2991" hex = "0baf" description = "vines echo" References = "RFC1701" /> "Cronus Direct" References = "131, DT15" /> Description = "AEONIC Systems" References = "Xerox" /> References = "xerox" /> /> Number Decimal = "32964" HEX = "80c4" description = "banyan systems" References = "xerox" /> Number Decimal = "3299" HEX = "80E4-80f0" description = "datability" references = "Xerox" /> HEX = "814c" Description = "SNMP" References = "jkr1" />
