[ronnie sahlberg <ronniesahlberg@xxxxxxxxx>]

Hm,  as the guilty party here (thats my code)

This sounds like ethereal has forgotten to set the timestamp properly
for one of the structures it uses to keep track of the timestamps
and thinks the time for the previous packet is 0  (january 1 1970).

Do you have a small example capture you can send to me so i can track
down this bug and fix it?




On Sat, 9 Oct 2004 18:16:04 +1000, Ciaran Finnegan  wrote:
> 
> 
> 
> Hi,
> 
>  
> 
> I've got three traces of a telnet session (either side of a wireless bridge
> link and on the other side of a NAT router). 
> 
>  
> 
> When I run a filter tcp.analysis.ack_rtt>1 on each of the traces I see
> telnet data packets in both directions (some marked as [TCP out-of-order])
> where the SEQ/ACK Analysis reports the RTT to ACK the segment was a number
> that is consistently 10971xxxxx.xx seconds. The traces were run over a
> period of four hours.
> 
>  
> 
> If I were more knowledgeable would this be making me emit satisfied little
> 'ahaa' noises?
> 
>  
> 
> Ta,
> 
>  
> 
> Ciaran. 
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users
> 
> 
>