I don't think I'd want SCTP guessing the frame number Wireshark is going to assign.
Anyway the TSN analysis stuff all works out with this change, but it does mean that the TSN analysis fields can't be used in read filters. Hmmm, maybe guessing the frame number could allow that to work, but I'm not sure if it's worth it. Luis EG Ontanon wrote: > Does it work if you do > > guint last_frame = 0; > ... > if (framenum == 0) > framenum = ++last_frame; > > > On Wed, Sep 17, 2008 at 11:59 PM, <[EMAIL PROTECTED]> wrote: >> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=26226 >> >> User: morriss >> Date: 2008/09/17 02:59 PM >> >> Log: >> If we're dissecting for a read filter in the GUI [tshark assigns >> frame numbers before running the read filter], don't do the TSN >> analysis. (We can't anyway because we don't have a valid frame >> number...) >> >> Without this change if you load a capture file in the >> GUI while using a read filter, every SCTP TSN is marked as a >> retransmission of that in frame 0. >> >> Directory: /trunk/epan/dissectors/ >> Changes Path Action >> +20 -8 packet-sctp.c Modified >> >> _______________________________________________ >> Wireshark-commits mailing list >> [EMAIL PROTECTED] >> https://wireshark.org/mailman/listinfo/wireshark-commits >> > > > _______________________________________________ Wireshark-dev mailing list [email protected] https://wireshark.org/mailman/listinfo/wireshark-dev
