Question about enabling security and changing the AnalogModel about artery HOT 7 CLOSED

For Nakagami we use the following entry in our omnetpp.ini:

*.radioMedium.pathLossType = "NakagamiFading"

from artery.

Security is disabled by default for performance reasons. You can enable it by setting the typename of Vanetza.ned's security submodule to "artery.networking.SecurityEntity". SecurityEntity has further parameters to customise its behaviour, see SecurityEntity.ned.

m-wegner's approach works when you are using INET as foundation. For Veins, you need to edit the config.xml and set the AnalogueModel's type to "NakagamiFading" (not tested).

from artery.

So, if I understand correctly, I just have to add a line in Vanetza.ned that would be.
*.securityModule.typename = "artery.networking.SecurityEntity"

I am familiar with the configuration for the security parameters, in the last version of Artery that I had those parameters were set in Middleware.ned. In fact, what I am intending to do is to see the same behavior, where all messages were around 370 bytes in lenght when the security parameters were in null and dummy values, and also fluctuating packet sizes with Naive and Straight values. What I need is to have that behavior in the new version of artery.

from artery.

Sorry @oscarmex1986, it turns out that I have made another mistake when refactoring the integration of Vanetza in Artery. I have added a simple example to scenarios/artery/omnetpp.ini, the inet_security configuration, at 699a9a5.

from artery.

I cloned the new commit, and when trying to build the run_example, this appeared:
Error: NED type 'artery.networking.SecurityEntity' could not be fully resolved due to a missing base type or interface, at /home/oscar/artery/src/artery/networking/SecurityEntity.ned:3

from artery.

Oops, that's embarrassing: I missed to add the ISecurityEntity module interface to the previous commit.

from artery.

Great. Security is enabled now. Thanks.

from artery.