[Alan Burlison <Alan.Burlison@xxxxxxx>]

Guy Harris wrote:

> There was a bug when a zero-length string appeared in some packets; I've
> checked in a fix.

Thanks :-)

> However, it appears that the capture you sent has the middle of an RSYNC
> sequence, but not the beginning of the connection, and, unfortunately, I
> don't think Ethereal's RSYNC dissector can handle that, so, if you have
> started the capture in the middle of an RSYNC sequence, you will
> probably only be able to make sense out of that capture by manually
> decoding the raw hex data in the TCP segments - Ethereal's dissection
> will probably not be correct, even with the bug fix, so don't infer from
> it that the RSYNC session is necessarily invalid.
>
> I don't know when that'll be fixed, if it's even fixable; I'm not an
> RSYNC expert, and won't be working on that.  (The bug I referred to in
> the first paragraph was a generic bug, not a bug in the RSYNC
> dissector.)

The full trace was pretty huge, so I just chopped out a few offending 
packets - it does work OK if I start the capture before the start of the rsync.

Thanks again for the prompt fix,

--
Alan Burlison
--