Replies: 1 comment 1 reply
-
|
Take a look at the babeld emulation showcase It does exactly this, except it does not use docker but rather handles and creates network namespaces internally. It means that it runs the application in a less isolated environment (i.e. you have to install the necessary files and application on the HOST system, but the network namespace is separate) You can launch multiple application, each with a different IP address. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I'm new to INET and would be interest what the community would recommend.
I would like to have docker application in a separate Docker environment alongside an INET-based simulation. Target architecture places the application and the INET simulation in distinct layers.
Approaches what I thought about is using socket-based link between the application containers and a proxy implemented as a custom INET StandardHost.
I would also be interest, whether I can use the stuff from the emulation showcase.
Exists there already comparable experiments or demonstrations already?
Beta Was this translation helpful? Give feedback.
All reactions