> I suppose at this point nobody is using BXXP any more, so I guess it
> could be a replacement, yes.
Well, given that the BXXP dissector registers on TCP port 10288, and the
BEEP dissector registers on TCP port 10288, if both were included in
Ethereal, TCP port 10288 traffic would probably be dissected, by
default, by the BXXP dissector, given that dissectors' registration
routines currently happen to be called in alphabetical order by
dissector file name (this is *NOT* a guarantee, though; it's subject to
change, so nothing should *rely* on dissectors' registration routines
being called in a particular order).
If support for both protocols is to be included in Ethereal, there
should probably be a configuration flag in the dissector to control
whether BEEP or BXXP is being dissected, or something such as that.
Note also that the BEEP dissector appears to be based on an older BXXP -
a number of changes made to the BXXP dissector since the version with
which you probably started are missing, e.g. the changes in revisions
1.19 and 1.20 of "packet-bxxp.c".
