Re: Bad TCP - Why ?

[Guy Harris <guy () alum mit edu>]

On Feb 18, 2010, at 5:28 AM, Forthofer Russ wrote:

> I don't believe it is necessarily indicating a problem

Then the rule name should probably be changed, as not all tcp.analysis.flags bits indicate that there's something "bad" 
about the packet.  Perhaps there was a time when all the flags did indicate a problem, and the rule was created and 
named then.

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe