riebl / artery

OMNeT++ V2X simulation framework for ETSI ITS-G5
GNU General Public License v2.0
204 stars 132 forks source link

Question about enabling security and changing the AnalogModel #45

Closed oscarmex1986 closed 5 years ago

oscarmex1986 commented 5 years ago

Hello. I don't think this goes in the issues page, but I'll post it anyway. I was wondering if the Security Entity is enabled by default, since Line 26 in Vanetza.ned shows: security: <default("")> In the last version of Artery I was working with, this was dealt with in Middleware.ned, setting a value to true. Also, and this might be more of a Veins question, do you happen to know how to activate the Nakagami analog model in config.xml? I mean, which tags and values would be the ones to write in there.

Thanks!

m-wegner commented 5 years ago

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

*.radioMedium.pathLossType = "NakagamiFading"
riebl commented 5 years ago

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).

oscarmex1986 commented 5 years ago

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.

riebl commented 5 years ago

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 699a9a56c4d95e1eaf566ccd1c8d4a67b4379b9f.

oscarmex1986 commented 5 years ago

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

riebl commented 5 years ago

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

oscarmex1986 commented 5 years ago

Great. Security is enabled now. Thanks.