-BEGIN PGP SIGNED MESSAGE-
> "Guy" == Guy Harris <[EMAIL PROTECTED]> writes:
Guy> On Mar 24, 2004, at 7:08 AM, Michael Richardson wrote:
>> okay, but there is more than just in/out.
>>
>> enum pcap1_probe {
>> INBOUND =1,
>> OUTBOUND =2,
>> FORWARD =3,
-BEGIN PGP SIGNED MESSAGE-
> "Hannes" == Hannes Gredler <[EMAIL PROTECTED]> writes:
Hannes> | okay, but there is more than just in/out.
Hannes> |
Hannes> | enum pcap1_probe {
Hannes> | INBOUND =1,
Hannes> | OUTBOUND =2,
Hannes> | FORWARD =3,
Hanne
-BEGIN PGP SIGNED MESSAGE-
> "Darren" == Darren Reed <[EMAIL PROTECTED]> writes:
Darren> I suppose I'm not so much concerned about it being "private"
Darren> as it being unique.
Darren> Maybe a vendor field and vendor sub-type field would be
Darren> useful ? That'd gi
-BEGIN PGP SIGNED MESSAGE-
> "Richard" == Richard Sharpe <[EMAIL PROTECTED]> writes:
Richard> That is, the ability to add textual comments to
Richard> frames. These comments would be ignored by tools that do
Richard> not understand them, but they would be displayed by tool
