Joost Yervante Damad wrote...
> On Wednesday 27 August 2008 11:52:18 Christoph Biedl wrote:
>
> > Now I noticed that at least for HTTP the extremely useful "Follow TCP
> > stream" function ignores all data in the second TCP stream. This
> > hides potentially interesting data.
>
> I'd expect this as behavior as this are indeed 2 unrelated TCP streams that
> just happen to use the same ports "by accident".
In that case selecting a packet of the seconds stream before "Follow TCP
stream" would display that one - not always the first. And the filter
expression automatically set would respect that in any way. Currently it
does not.
Christoph
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
