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 (wmeier@xxxxxxxxxxx) and Joerg
(jmayer@xxxxxxxxx) 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 <jmayer@xxxxxxxxx>
Reply-To: Developer support list for Wireshark
<wireshark-dev@xxxxxxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
References: <20081202230235.9226223069@xxxxxxxxxxxxxxxxxx>
<4936FBB9.7050801@xxxxxxxxxxx>
<FD9222E5-19DE-48A0-9DE3-51E423AD2A37@xxxxxxxxx>
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 <jmayer@xxxxxxxxx>
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
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev
