Hello
Sorry for the late reply, but work took over.
Taking your concerns into consideration, I changed the setup a little
bit. With Bugs #5751 and Bugs #5752 I added two patches, which add
heuristic sub-dissectors to both EPL and SercosIII dissectors. As a
side-effect, I cleaned the EPL dissector
On Mar 9, 2011, at 10:34 AM, Roland Knall wrote:
> I agree, but the current situation, where the selection seems to
> happen purely by chance is also not ideal.
The *ideal* situation would be one wherein registering more than one dissector
for a given type value would be an error, and other, be
On Wed, Mar 9, 2011 at 7:04 PM, Guy Harris wrote:
>
> On Mar 9, 2011, at 7:39 AM, Roland Knall wrote:
>
>> It would definitly not solve the underlying problem. but at least it
>> would make the whole process predictable, which is definitly not the
>> case now.
>
> That might or might not constitut
On Mar 9, 2011, at 7:39 AM, Roland Knall wrote:
> It would definitly not solve the underlying problem. but at least it
> would make the whole process predictable, which is definitly not the
> case now.
That might or might not constitute an improvement; the file name given to a
plugin, or whethe
On Wed, Mar 9, 2011 at 4:14 PM, Chris Maynard wrote:
> Roland Knall writes:
>
>> On Linux, when the gtk-based filehandler loads the list of plugins, it
>> does so alphabetically. This does not seem to be the case on Windows.
>> So here, someone might argue, that this indeed is plattform-specific,
Roland Knall writes:
> On Linux, when the gtk-based filehandler loads the list of plugins, it
> does so alphabetically. This does not seem to be the case on Windows.
> So here, someone might argue, that this indeed is plattform-specific,
> and not exactly a bug. You would have to sort the plugin
On Tue, Mar 8, 2011 at 4:41 AM, Chris Maynard wrote:
> Roland Knall writes:
>
>> Ok, now I have a question.
>>
>> Both dissectors register on a certain Ethernet Frame Type (0x88CD). If
>> I disable the SercosIII dissector, in theory, my dissector should get
>> called, right?
> That would be my ex
Roland Knall writes:
> Ok, now I have a question.
>
> Both dissectors register on a certain Ethernet Frame Type (0x88CD). If
> I disable the SercosIII dissector, in theory, my dissector should get
> called, right?
That would be my expectation as well.
> But no, even if I specifically disable th
Hi
On Mon, Feb 28, 2011 at 9:55 AM, Roland Knall wrote:
> On Mon, Feb 28, 2011 at 9:51 AM, Guy Harris wrote:
>> So my question is, can I influence the decision made by wireshark in
>> any way, which plugin get's called?
>
> Try disabling the dissector for the protocol whose dissector you don't
On Mon, Feb 28, 2011 at 9:51 AM, Guy Harris wrote:
>
> On Feb 28, 2011, at 12:32 AM, Roland Knall wrote:
>> On Windows, the SercosIII plugin takes precedence over my plugin. Both
>> register the same Ethertypes, therefore this should not be unusual,
>
> If you mean "it's not unusual that random st
On Feb 28, 2011, at 12:32 AM, Roland Knall wrote:
> My main development plattform is Linux. On it, my plugin get's loaded,
> everything get's dissected correctly, and works as intended. My plugin
> is called openSAFETY.
>
> On Windows, the SercosIII plugin takes precedence over my plugin. Both
>
Hello
I am developing a plugin, which will dissect protocols, where other
dissectors are already registered.
Two instances are the Ethernet Powerlink dissector as well as the
Sercos III dissector.
My protocol is part of their communication messages, but can not be
identified as easily, as e.g. a
12 matches
Mail list logo
