Steve, Thanks for your detailed response! > are using internal transports. This is a new feature in 0.9.2 that > improves performance and simplifies configuration for the > preferred emane configuration: running 1 NEM per emulator > instance except when configuring multi-channel gateways.
Thanks for clarifying. I wasn't sure if the new internal transport feature was going to work with the way CORE was doing business. CORE was installing TAP devices into the containers after the TAPs were created, using a single emanetransportd running on the host. One emane process is also running on the host. I was planning to update CORE to run one emanetransportd/emane process per container -- looks like that is needed for 0.9.2 support. Nice that we no longer need the emanetransportd. -Jeff _______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
