Package: wireshark
Version: 1.0.2-3
Severity: normal
TCP Port numbers reused happens every now and then, especially if
the capture is run over a longer time and the client OS does not use a
wide range of local ports.
Now I noticed that at least for HTTP the extremely useful Follow TCP
stream
forwarded 496768 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1447
thanks
Christoph Biedl wrote...
Package: wireshark
Version: 1.0.2-3
Severity: normal
I've learned this problem is already described in the upstream bugzilla.
Therefore this tagging to avoid duplicate work.
On Wednesday 27 August 2008 11:52:18 Christoph Biedl wrote:
Package: wireshark
Version: 1.0.2-3
Severity: normal
TCP Port numbers reused happens every now and then, especially if
the capture is run over a longer time and the client OS does not use a
wide range of local ports.
Now I
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
On Wednesday 27 August 2008 19:24:53 Christoph Biedl wrote:
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
5 matches
Mail list logo