http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2345
--- Comment #2 from Martin Peylo <wireshark@xxxxxxx> 2008-03-13 14:22:09 GMT ---
(In reply to comment #1)
> How does that work when message 1 goes to <1.1.1> and message 2 going to
> <1.1.2>? The packet can't be assigned an applicable address.
While this wouldn't occure in my example - the reassembling takes place in the
package of the last fragment - you're generally right. There could be umpteen
logical packages encapsulated in a single TCP package. This problem does affect
every protocol conveyed by TCP which uses its own addressing scheme. I don't
know if there are any others, but in theory one could convey e.g. Ethernet over
TCP.
A possible proposal would be to somehow create logical packets for stream
reassembling. They could be attached to the physical one in the "Packet List"
pane, they are found in - without having a distinct (global) packet number.
This would not only solve this problem but also enhance the lucidity by
enabling the user to see all the individual packet entities of the highest
layer (assuming that they are usually the most interesting) at a glance.
I can not estimate how much effort implementing this would need, but maybe
someone familiar with the Packet List knows a shortcut how to achieve this?
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.