Hello, I currently am using CORE to run tests with EMANE. In the current setup, EMANE is run centralized on the host system while CORE spawns off containers. I would like to expose EMANE position events into each container and process the messages. Here's how I'm thinking of doing this: 1. Inside CORE, create a controlnet 2. On the host system, have a multicast repeater script that listens for EMANE events and redirects it to the bridged interface created by CORE for the control net 3. Inside the container, subscribe to the emaneevents and do my parsing there. I have #1 and #2 working. For #3, I'd like to use the EMANE user demo #19 (eventsubscriber.py) to subscribe to EMANE events and print them. Running this script on the host system works perfectly.. However, when I try to run the script inside the container, I get an error:
root@n1:~/Documents/demonstration/19# ./eventsubscriber.py
Traceback (most recent call last):
File "./eventsubscriber.py", line 15, in <module>
service = emaneeventservice.EventService()
emaneeventservice.error: Transport option add membership
I'm suspecting it cannot find a library that it needs. I'm wondering if
there's anything special I need to enable inside the container to be able to
use the emaneeventservice python bindings inside a container?
Also, if there's an easier way to do this (getting emane events inside
containers with EMANE running in centralized), please share. Thanks!
-Bow-Nan
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
