OK, now that I've got a working EMANE installation, I'm trying to bring up three linux containers in a centralized deployment and the comm effect shim, with full connectivity as the default. Taking cues from the demos, I add a bridge, start emane, and bring up the linux containers, which run a startup script that loads emanetransportd and sshd.
I can access them via the bridged interface fine, but no communication seems to occur over EMANE's transport. The emane0 interface is instantiated fine, and I can ping it locally -- from within its container -- but no joy with any traffic over the transport. The logs don't yield any clear failure info, so I wanted to know how I could start troubleshooting this, or if there are any specific sections in the manual I've overlooked… Thanks, James ___________________________________________ James B. Morris Dept. of Electrical, Computer, and Systems Engineering [email protected] JEC 6212 Rensselaer Polytechnic Institute 110 8th St. Troy, NY 12180-3590
_______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
