search

adjacentlink / emane

Distributed wireless network emulation framework
Other
129 stars 37 forks source link

EMANE Shell Localhost Scope #127

Closed hideogump closed 5 years ago

hideogump commented 5 years ago

While I have the EMANE shell (emanesh) command working when connecting to a specific Linux container running emane proper, I am looking as well for support at the host system level via "emanesh localhost" to allow me to get content across the simulation rather than through individual container levels. When I attempt this connection via "emanesh localhost", this connection fails, as there is no listener.

To get EMANE shell to operate at the localhost level, does emane proper need to be run at the host level? There is this suggestion in the sample configuration files, but is there a particular platform.xml file needed to simply have EMANE shell support at emulation scope?

sgalgano commented 5 years ago

emanesh connects to a running emulator instance's control port service which listens for incoming connections at controlportendpoint.

We use OpenTestPoint for the functionality you seek. Demonstrations contained in the emane-tutorial, python-etce-tutorial, and letce2-tutorial all use otestpoint to provide tiered access to statistics and tables from one or more emulation nodes (based on how you configure brokers).

You can also reference the emane-control-port-tutorial to create your own tools for accessing control port information.

hideogump commented 5 years ago

Thanks, I understand. It would seem the use of emanesh with total emulation scope would require all NEMS to exist within a single platform.xml as in one of the examples.

sgalgano commented 5 years ago

Keep in mind that is a highly contrived example for illustrative purposes only. We do not advocate running more than one NEM in an emulator instance.