Den 17. aug. 2007 kl. 22.11 skrev Guy Harris:
> I checked in a change to make the code that handles LAPB packets do
> the
> same check for two bytes in the record header to decide whether
> there's
> 4 bytes of junk at the end of the packet that we do for other types.
> That seems to fix the c
Stig Bjørlykke wrote:
> They are at the end of each frame.
Looks like the same sort of stuff we've seen in other captures.
I checked in a change to make the code that handles LAPB packets do the
same check for two bytes in the record header to decide whether there's
4 bytes of junk at the end
Den 17. aug. 2007 kl. 18.43 skrev Guy Harris:
Do those 4 bytes show up at the beginning, or the end, of the frame?
For some frame types, we find either 4 bytes of FCS or 4 bytes of junk
at the end of the frame.
They are at the end of each frame. Sometimes they have data and
sometimes they a
Stig Bjørlykke wrote:
> I have a NetXRay 2.2 capture with some LAPB/X.25 traffic. The data is
> shown correct, but all frames have 4 bytes extra which wireshark tries
> to dissect without any luck. Can this 4 bytes belong to the capture
> format?
Do those 4 bytes show up at the beginning, or th
Hi.
I have a NetXRay 2.2 capture with some LAPB/X.25 traffic. The data is
shown correct, but all frames have 4 bytes extra which wireshark tries
to dissect without any luck. Can this 4 bytes belong to the capture
format?
--
Stig Bjørlykke
___
Wiresh
