Help Needed: Compatible Versions of OMNeT++, INET, and Simu5G

[akiraaaaa226]

Hello,

I’ve been trying to find a combination of OMNeT++, INET, and Simu5G versions that work well together, but I keep running into compatibility issues. I've tested multiple version combinations, but none seem to fully work without errors or build problems.

Could you please let me know:

Which versions of OMNeT++, INET, and Simu5G are currently known to be compatible and stable together?

Are there any specific commits or branches I should be using for Simu5G or INET?

I’m working on Windows 10 and my goal is to implement a simulation involving 5G, 5G sidelink communication and D2D relay mechanisms, so I’d appreciate your advice to make sure I start with the right setup.

Thank you in advance!

[avarga]

opp_env has been designed expressly for this purpose: to facilitate installation of OMNeT++ models. After installing it, you can list the compatible version combinations with this command:

opp_env list simu5g --expand

And the following command will install Simu5G on your system without requiring any attention from you:

mkdir simu5g-workspace && cd simu5g-workspace && opp_env install --init simu5g-latest

Then you can use the opp_env shell command to open a shell where you can use it.

Hope you use Linux, macOS, or at least WSL on Windows. The native Windows distro of OMNeT++ is not recommended for any serious work (compilation is incredibly slow there).

[akiraaaaa226]

Dear András,

I hope you're doing well.
I successfully installed compatible versions of OMNeT++6.1.0, Simu5G1.3.0, and INET 4.5.4 using opp_env on WSL, and everything build fine so far.
I'm working on a small university project using OMNeT++, Simu5G, and INET, focused on 5G D2D communication with relay selection (based on RSSI, distance, and battery level).
However, I’m unsure about how to organize my implementation:

Should I create a new OMNeT++ project,

Or should I write C++ code for handling messages by Base station from UEs in the Simu5G folder, and implement D2D communication (e.g., via Wi-Fi) in the inet folder using INET modules ?

Thank you very much for your time and help!

[rhornig]

Either way is working. If you write something that is generic enough so other people might be interested to use it or it would make sense as part of simu5g in the future, then fork Simu5G and add your code somewhere under the src folder.

On the other hand, if your work is about some specific simulation/paper that is not generic enough, create a sperate project, make it dependent on both Simu5G and INET and use that project for your code. (on long term this is easier to maintain)

[akiraaaaa226]

I did the second option cause I need only simulation, the build process is going smoothly. However, when I try to run the simulation using Qtenv, I encounter this issue

…

On Wed, Apr 30, 2025, 13:07 Rudolf Hornig ***@***.***> wrote: Either way is working. If you write something that is generic enough so other people might be interested to use it or it would make sense as part of simu5g in the future, then fork Simu5G and add your code somewhere under the src folder. On the other hand, if your work is about some specific simulation/paper that is not generic enough, create a sperate project, make it dependent on both Simu5G and INET and use that project for your code. (on long term this is easier to maintain) — Reply to this email directly, view it on GitHub <#264 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2HHQEMWOTVG5ZXKTEMNJED24C4GJAVCNFSM6AAAAAB2UVFNLGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJZGI2TMNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>