Problems with protocol/service registration

[GiovanniTortia]

I have defined a new protocol in Protocol.cc to represent raw data being generated by an application being sent directly to a layer 2 CAN, the idea is that there is an EthernetBurstApplication, which i defined, which sends out frames with the raw ehtertype in the mac header, which are "caught" by an EthernetSinkApp. The CAN i want to simulate uses TsnDevice modules, however when the frames are received they get stuck right after the EthernetLayer module, because the bl message dispatcher doesn't see a module registered to receive frames tagged with the raw protocol tag. I have added the following line to EthernetSocketIo.cc, in its initialize function during the INITSTAGE_NETWORK_INTERFACE_CONFIGURATION + 1 stage:
registerProtocol(Protocol::raw, gate("trafficIn"), SP_INDICATION);
but this doesn't seem to have any effect, since i still get the error:
handlePacket(): Unknown protocol: protocolId = 74, protocolName = raw, servicePrimitive = INDICATION, pathStartGate = demo.t2.ethernet.macHeaderChecker.out, pathEndGate = demo.t2.bl.in[2] -- in module (inet::MessageDispatcher) demo.t2.bl (id=12), at t=0.000425717252s, event #14
What bothers me is that from qtenv i can clearly see that, in its serviceToGateIndex table, at has an entry for service 74 (but there's no entry in the protocol table), and that the parameters forwardProtocolRegistration and forwardServiceRegistration are set to true.
I have also tried to register the protocol with registerService(...), changing the gate to socketIn and changing the initialization stage at which the registration happens, to no avail, and the knowledge base chatbot doesn't seem to offer any better solution

[aarizaq]

It is a bit more complex.
First, you need to include your protocol in the files, Protocol.cc and Protocol.h.
Also, if it is an Ethernet type, you need to assign a number to identify the protocol in the file EtherType.msg, and finally, in the file ProtocolGroup.cc in ethertypeProtocols, you need to include the link between the protocol definition and the protocol number.

[GiovanniTortia]

I have already done that, as a matter of fact the frames go through a TsnSwitch just fine, the problem appears once the frame exits the ethernetLayer module of the recipient and the message dispatcher doesn't know where to send it

[aarizaq]

The next layer has not been registered in the dispatcher, and the dispatcher doesn't know where to send the frames.

[levy]

You can check the mapping tables of all message dispatchers along the path. Probably the registration is not forwarded by some module between the EthernetMacHeaderChecker and the modified EthernetSocketIo. BTW, you don't need to create a new protocol just to send raw Ethernet frames from one node to another. It's perfectly fine to use applications for that.

If you think there's a bug somewhere then please send a minimal example that demonstrates the problem.

[GiovanniTortia]

I probably didn't need to but i wanted to make a single application which could both send single frames as well as bursts, and most importantly which would operate in a way i fully understand. In the end the problem was the initialization stage i called registerProtocol in, but the EthernetSocketIO module after receiving the message sent it back out so i made another app called EtherBurstSink which only registers itself to the raw protocol without doing anything else, where i will implement other functionalities at need. Thanks for the reply