Re: [Wireshark-dev] Spurious TCP SEQ/ACK analysis errors
On 02/11/2010 18:08, Christopher Maynard wrote: > Graham Bloice writes: > >> Are folks >> seeing a lot of these on trunk? Almost every capture I load >> seems to have some "TCP ACKed lost segment" and "TCP Previous >> segment lost" warnings, even though the sequence numbers are >> fine. >> Even more oddly, the displayed warnings toggle on and off with >> every click of the reload button, along with the Seq value in >> the first packet (a SYN) changing from absolute to relative (in >> both the Info column and the packet tree for TCP). >> I've also just noticed the stream index field for the first >> packet toggles between 0 and some other integer with each >> reload. > Graham, I meant to reply before, but got side-tracked I guess. I'm not really > seeing this with the capture files I have, but of course that doesn't mean > it's > not happening with other capture files or that I'm simply missing it in those > I > do have. > > Anyway, maybe you want to open up a bug report about this and post a sample > capture file that illustrates these potential bugs? > I'll make another build from trunk and see where things are. If they're still bad for me I'll create a bug. -- Regards, Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Spurious TCP SEQ/ACK analysis errors
On Tue, Oct 19, 2010 at 06:25:09PM +0100, Graham Bloice wrote: > Even more oddly, the displayed warnings toggle on and off with every > click of the reload button, along with the Seq value in the first > packet (a SYN) changing from absolute to relative (in both the Info > column and the packet tree for TCP). I believe I saw that recently too, but I was so focused on troubleshooting a problem, that I turned toggled the relative sequence number option and forgot about it. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Spurious TCP SEQ/ACK analysis errors
Graham Bloice writes: > Are folks > seeing a lot of these on trunk? Almost every capture I load > seems to have some "TCP ACKed lost segment" and "TCP Previous > segment lost" warnings, even though the sequence numbers are > fine. > Even more oddly, the displayed warnings toggle on and off with > every click of the reload button, along with the Seq value in > the first packet (a SYN) changing from absolute to relative (in > both the Info column and the packet tree for TCP). > I've also just noticed the stream index field for the first > packet toggles between 0 and some other integer with each > reload. Graham, I meant to reply before, but got side-tracked I guess. I'm not really seeing this with the capture files I have, but of course that doesn't mean it's not happening with other capture files or that I'm simply missing it in those I do have. Anyway, maybe you want to open up a bug report about this and post a sample capture file that illustrates these potential bugs? ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Spurious TCP SEQ/ACK analysis errors
Are folks seeing a lot of these on trunk? Almost every capture I load seems to have some "TCP ACKed lost segment" and "TCP Previous segment lost" warnings, even though the sequence numbers are fine. Even more oddly, the displayed warnings toggle on and off with every click of the reload button, along with the Seq value in the first packet (a SYN) changing from absolute to relative (in both the Info column and the packet tree for TCP). I've also just noticed the stream index field for the first packet toggles between 0 and some other integer with each reload. -- Regards, Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
