Can you give us an example of a proper heuristic dissector or can you 
give me an example of a TAPA packet that got eaten by the heuristic 
patch Don provided?
Do we just need to do more checks to eliminate the possibility of 
non-unistim packets being detected as unistim?

Chad Singer
Software Developer
Cypress Communications
404-442-0216

Jaap Keuter wrote:
>
> Hello Don,
>
> Seems that your unistim patch didn't go down well, so has basically been
> reverted. Could you please work with Bill ([email protected]) and Joerg
> ([email protected]) to get this heuristics things out of the way?
>
> Thanx,
> Jaap
>
> -------- Original Message --------
> Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 26904:
> /trunk/plugins/unistim/ /trunk/plugins/unistim/: packet-unistim.c
> Date: Thu, 4 Dec 2008 10:31:57 +0100
> From: Joerg Mayer <[email protected]>
> Reply-To: Developer support list for Wireshark 
> <[email protected]>
> To: Developer support list for Wireshark <[email protected]>
> References: <[email protected]>
> <[email protected]>  
> <[email protected]>
>
> On Thu, Dec 04, 2008 at 12:20:25AM +0100, Jaap Keuter wrote:
> > Care to comment on this one?
> > Frankly I'm getting tired of going back and forth with this thing. 
> > Can't we sort it out once and for all?
>
> The only comment I can give is, that in current svn head using port 5000
> for Unistim still eats TAPA packets.
> I've changed it back to the old comment and port 0
>
>   ciao
>       Joerg
> --
> Joerg Mayer                                           <[email protected]>
> We are stuck with technology when what we really want is just stuff that
> works. Some say that should read Microsoft instead of technology.
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> https://wireshark.org/mailman/listinfo/wireshark-dev
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> https://wireshark.org/mailman/listinfo/wireshark-dev
>

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to