https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4607
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jeff.morriss.ws@xxxxxxxxx
Resolution| |WORKSFORME
--- Comment #2 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2010-03-22 10:55:53 PDT ---
The 2 directions are using different IP addresses--so it's the IP address
portion of that filter which is causing it to not work as you expect. For
example:
Frame 4060 has a CR from 10.44.222.1 (PC: 8954) -> 10.200.114.129 (PC: 10072)
Frame 4062 has the response from 10.200.114.193 (PC: 10072) -> 10.44.222.17
(PC: 8954)
Note how the outbound source IP address is NOT the same as the inbound
destination IP address.
In other words, your filter needs to contain 4 IP addresses instead of 2. This
isn't Wireshark's doing; if this filter used to work at this site then I'm
guessing something in the network changed.
Closing since this doesn't appear to be a Wireshark problem.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
