<p>Just to give a feedback,
It seems that directly it cannot be done, not the full INET as it is can be parallelized in short because it uses global variables in some places.
in this particular case, mac addresses assignment are one of the issues (uses a global variable), hence eth interface cannot be parallelized.</p>

<p>for more details refer to this paper explaining why this is not possible:</p>

<ul>
<li><a href="http://arxiv.org/abs/1409.0994" rel="nofollow">Enabling Distributed Simulation of OMNeT++ INET Models:</a></li>
</ul>

<p>For reference/possible solution refer to authors webpage from aachen university, where you can download a complete copy of omnet++ and INET that can be parallelized: </p>

<ul>
<li><a href="https://code.comsys.rwth-aachen.de/redmine/projects/parallel-inet" rel="nofollow">project overview and code</a></li>
</ul>
Omnet++: Parallelize Single Run Simulation
<p>I'm trying to parallelize my model  (I want to parallelize a single config run, not run multiple configs in parallel). 
I'm using Omnet++ 4.2.2, but probably the version doesn't matter.</p>

<p>I've read the Parallel Distributed Simulation chapter of the Omnet++ manual
and the principle seems very straightforward: 
simply assign different modules/submodules to different partitions. 
Following the provided cqn example</p>

<pre><code>*.tandemQueue[0]**.partition-id = 0
*.tandemQueue[1]**.partition-id = 1
*.tandemQueue[2]**.partition-id = 2
</code></pre>

<p>If I try to simulate relatively simple models everything works fine I can partition the model at wish.
However, when I start to run simulation that use Standardhost module, or modules that are interconnected using ethernet links that doesn't work anymore. </p>

<p>If i take for example the Inet provided example WiredNetWithDHCP (inet/examples/dhcp/eth), as experiment, lets say I want to run hosts in a different partition than the switch
I therefore assign the switch to a partition and everything else to another:</p>

<pre><code>**.switch**.partition-id = 1
**.partition-id = 0
</code></pre>

<p>The different partitions are separated by links, there is delay, and therefore it should be possible to partition this way.
When I run the model, using the graphic interface, I can see that the model is correctly partitioned however the connections are somehow wrong and i get the following error message:</p>

<pre><code>during network initialization: the input/output datarates differ
</code></pre>

<p>clearly datarates don't differ (and running the model sequentially works perfectly), by checking the error message this exception is triggered also by link not connected. This is indeed what happen. It seems that the gates are not correctly linked. </p>

<p>Clearly I'm missing something in the Link connection mechanism, should I partition somewhere else?</p>

<p>Due to the simplicity of the paradigm I feel like being an idiot but I'm not able to solve this issue by myself</p>