Why Your Wireshark Filter May Not Mean What You Think It Means
Views: 405Wireshark display filters can look deceptively simple. For example: tcp.port > 1024 seems obvious. But a TCP packet normally has two port values: a source port and a destination port. That means Wireshark may be evaluating more than one value when you write a filter. Consider: This packet satisfies: tcp.port > 1024 because 53000
Why Your Wireshark Filter May Not Mean What You Think It Means Read More »
