osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

Add in a comment about the "fs" and "flags" fields in the "frame2" 

record.

svn path=/trunk/; revision=1130
This commit is contained in:
Guy Harris 1999-11-28 02:08:48 +00:00
parent d6c3d1b5bf
commit 9f084a7ebc
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
wiretap/ngsniffer.c
View File

@ -1,6 +1,6 @@
/* ngsniffer.c
*
* $Id: ngsniffer.c,v 1.26 1999/11/27 20:46:46 guy Exp $
* $Id: ngsniffer.c,v 1.27 1999/11/28 02:08:48 guy Exp $
*
* Wiretap Library
* Copyright (c) 1998 by Gilbert Ramirez <gram@verdict.uthscsa.edu>
@ -475,6 +475,21 @@ static int ngsniffer_read(wtap *wth, int *err)
t = (double)time_low+(double)(time_med)*65536.0 +
(double)time_high*4294967296.0;
/*
* In one PPP "Internetwork analyzer" capture,
* the only bit seen in "fs" is the 0x80 bit,
* which probably indicates the packet's
* direction; all other bits were zero.
* All bits in "frame2.flags" were zero.
*
* In one Ethernet capture, "fs" was always 0,
* and "flags" was either 0 or 0x18, with no
* obvious correlation with anything.
*
* In one Token Ring capture, "fs" was either 0
* or 0xcc, and "flags" was either 0 or 0x18,
* with no obvious correlation with anything.
*/
wth->phdr.pseudo_header.x25.flags = frame2.fs & 0x80;
goto found;