Wireshark · Ethereal-dev: Re: [Ethereal-dev] New Dissector: Dumb Question

[Alex Kirk <alex@xxxxxxxxxxxx>]

> > Judging by your prompts below, it seems you are building on a Unix
> > system, not a Windows system.  If that's the case, then you probably
> > also need to modify epan/dissectors/Makefile.in.  After that, you'll
> > likely need to re-run autogen.sh, then configure & make again.

Autogen.sh was the ticket here -- I first tried modifying
epan/dissectors/Makefile.in, configuring & making, and got the same result;
however, re-running autogen.sh (which added a lot more to
epan/dissectors/Makefile* than I would have known to add) got it to compile in.

Let me follow up, though, by asking what I've done wrong in terms of
registration to have my new protocol not appear in my new copy of Ethereal --
not automatically, not in "Decode As...", nowhere.

Frankly, I have a feeling that I'm conflicting with some already-registered
protocol: I'm doing a (very basic so far) WINS decoder, and I'm trying to set it
up on TCP port 42, which Ethereal already IDs as "nameserver". 

For convenience's sake, I'm going to attach my packet-wins.c, so if I have made
a mistake in the syntax there, it's very obvious (also, you can see that I'd
declared my registration functions right, they matched the regex, etc.).

Thank you all for your assistance. Hopefully I'll be able to make some solid
decoder contributions in return soon. :-)

Alex Kirk

Attachment: packet-wins.c
Description: Binary data