Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2019-11-07,master

commit 1f450faf8b1d5f9e97ec3f42d954ae9914646159 Author: Sven Eckelmann sven@narfation.org Date: Sun Oct 27 17:55:13 2019 +0000

doc: open-mesh/Emulation_Environment

1f450faf8b1d5f9e97ec3f42d954ae9914646159 open-mesh/Emulation_Environment.textile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/open-mesh/Emulation_Environment.textile b/open-mesh/Emulation_Environment.textile index c4accda..b5a7cf5 100644 --- a/open-mesh/Emulation_Environment.textile +++ b/open-mesh/Emulation_Environment.textile @@ -4,14 +4,13 @@ To give an answer to the often asked question "How to test/evaluate/debug mesh n

A simple setup is shown first and various extension and debugging helpers are explained later.

- h2. Architecture

The test stack consists of the following components:

* Host running the virtual instances * virtual instances (cloned) from a single image -* interconnect to connect the virtual instances +* interconnect to allow commmunication between the virtual instances * various debugging tools * optional external devices and services