Hi Guy, > I don't know what it means to "dissect" an inter-packet gap, > however....
How long it is for example and what kind of idle were sent. > Or you could have a "PHY-level Ethernet" dissector that > dissects *only* > the preamble, SOP, and EOP, and hands the packet data to the existing > Ethernet dissector; that wouldn't put them in the *same* part of the > protocol tree, but some would argue that's not a bug but a feature. That what I need I think. > > Background: I�m working on a traffic recorder/replayer on > the PHY level > > (hw driven) and it would be nice if I could use the > ethereal software to > > analyze my recorded traffic. > > How "PHY-level" are you doing? line coding level, so its like you see it on the line. > For example, are you recording the octets of the packet data, > or the raw > 8B6T symbols for 100Mb Ethernet or the raw 8B/10B symbols for 1000Mb > Ethernet? We are talking about 10GE. 64b/66b block codes, 8b/10b XAUI side and something like that. > If you're recording the raw symbols, it'd be a *lot* more work for > Ethereal to dissect the packets. That�s what I�ve already done :-) . Please give me some hints on howto implement such kind of dissector mentioned above. Best regards, thomas
