Wireshark · Wireshark-dev: [Wireshark-dev] 1.7.1 bug? tcp.flags == 0x8c2

Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: [Wireshark-dev] 1.7.1 bug? tcp.flags == 0x8c2

From: Lanell Allen <blanellallen@xxxxxxxxx>

Date: Thu, 9 Feb 2012 09:20:52 -0600

[SYN, ECN, CWR]

The "tcp.flags == 0x8c2" filter crashes on v. 1.7. Stays "pink" with the error message "invalid filter" / "too big", etc.
Works fine on 1.6.1 and 1.6.4

Lanell Allen, WCNA

Follow-Ups:
- Re: [Wireshark-dev] 1.7.1 bug? tcp.flags == 0x8c2
  - From: Christopher Maynard

Prev by Date: Re: [Wireshark-dev] Adding name resolution blocks in Wireshark
Next by Date: Re: [Wireshark-dev] [Wireshark-commits] rev 40877: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-dns.c
Previous by thread: Re: [Wireshark-dev] Adding name resolution blocks in Wireshark
Next by thread: Re: [Wireshark-dev] 1.7.1 bug? tcp.flags == 0x8c2
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube