Comment # 11
on bug 11525
from Pascal Quantin
(In reply to Dragan from comment #10)
> (In reply to Pascal Quantin from comment #9)
> > (In reply to Dragan from comment #8)
> > > (In reply to Pascal Quantin from comment #7)
> > > > (In reply to Dragan from comment #6)
> > > > > (In reply to Dragan from comment #5)
> > > > > > Created attachment 13871 [details]
> > > > > > false positive for acked unseen
> > > > >
> > > > > ples see this case, packets 62 and 61. It is analysed with latest nightlly
> > > > > build
> > > >
> > > > If I"m not mistaken, there is a TCP segment missing between packets 59 and
> > > > 61, thus the detection: SN=23652 to 28031 were not received.
> > > > That's why you get a warning in packet 61 and 62.
> > >
> > > mybe, but thenj this message in packet 62 is misleading. it is strange. If I
> > > open packet 62 in detail (SEQ/ACK analysys section), there is stated that
> > > this is ack to packet 61
> >
> > Yes this is true, and it's telling you that it's acking an unseen segment,
> > which is true also.
>
> you mean that server ACK the whole stream of data by ACKing segment in
> packet 61 ... but wireshark does not see whole stream?
looks like at first glance.
You are receiving this mail because:
- You are watching all bug changes.