On 2/28/07, Michael Tuexen <Michael.Tuexen@xxxxxxxxxxxxxxxxx> wrote:
On Feb 28, 2007, at 2:09 PM, lego@xxxxxxxxxxxxx wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=20947
>
> User: lego
> Date: 2007/02/28 02:09 PM
>
> Log:
> SCTP TSN analysis part 1.
>
> Up and running.
> As it is analysis will stop at TSN rollover (0xffffffff->0x00000000).
Is it possible to get rid of that limitation?
Yes, I'm still evaluating the best way to do it.
BTW. I discovered I have to fix Gap Blocks before that.
>
> And It will start to misbehave when a TSN is seen again in the
> same half association (that's a case where an out-of-memory error
> will probably had happened before).
That seems to be acceptable.
>
> It still needs testing.
>
> Directory: /trunk/epan/dissectors/
> Changes Path Action
> +238 -325 packet-sctp.c Modified
>
> _______________________________________________
> Wireshark-commits mailing list
> Wireshark-commits@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-commits
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
