Evan Huus
changed
bug 8606
| What |
Removed |
Added |
| Status |
INCOMPLETE
|
RESOLVED
|
| Resolution |
---
|
NOTABUG
|
Comment # 16
on bug 8606
from Evan Huus
Oh, I see. Yes, I can reproduce your problem if I actually look at the frame
numbers you mention. There were enough 'good' reassemblies that the errors were
getting lost as noise. My mistake.
It's not a reassembly error though: you're missing packets. See, for example,
frame 650 which indicates that a segment is missing mid-stream (this is why the
response to frame 168 is never reassembled, it doesn't have all the data). Did
tshark indicate any dropped packets during capture?
Other frames noting errors:
- 641 (thus no response to 167)
- 1142, 1149, 1153 (thus no response to 1057)
etc.
You are receiving this mail because:
- You are watching all bug changes.