Wireshark-bugs: [Wireshark-bugs] [Bug 8975] Exported filtered packet cannot be isolated, you can
Jeff Morriss
changed
bug 8975
| What |
Removed |
Added |
| Status |
CONFIRMED
|
INCOMPLETE
|
Comment # 4
on bug 8975
from Jeff Morriss
(In reply to comment #3)
> The packets I was trying to filter out are seperate connections to the same
> client as the ones I was trying to save. So if this is a feature I do not
> like it. There should of been no reason for keeping the other packets for
> reassumbly. This is a 1.4 Gig file, I think it is just too large for
> Wireshark to handle.
If they are truly separate (TCP) connections then either:
1) your filter isn't working quite the way you're expecting (and you are
displaying some packets from those connections)
2) (or) there's a bug in the code which is picking up dependencies between
connections
If you can provide a smaller capture which proves it's the latter then we could
fix it.
The intent of the feature is quite simple: without it when you open the newly
saved capture file you won't be able to actually see the (reassembled) PDUs
you're currently displaying. You will, instead, see just the last
segment/frame of those PDUs (if you use Wireshark version 1.6.x this is what
will happen).
You are receiving this mail because:
- You are watching all bug changes.
