Dan, Your XML indicates you are using 2ray which requires location events:
<param name="propagationmodel" value="2ray"/> It is easier to debug emane using the control port. Connect to each emulator instance and verify you are receiving location events using the emulator physical layer statistic tables. See the emane tutorial for more information on using the control port to debug an emulation: https://github.com/adjacentlink/emane-tutorial/wiki -- Steven Galgano Adjacent Link LLC www.adjacentlink.com On 02/01/2016 02:29 PM, Dan O'Keeffe wrote: > Hi, > I'm having trouble getting a distributed CORE/EMANE emulation working > because of what I think is an EMANE problem. In particular, OLSR > broadcast packets received from remote containers are dropped by emane > with something like the following log message: > > DEBUG PHYI 001 FrameworkPHY::processUpstreamPacket_i transmitter 4, src > 4, dst 65535, drop propagation model missing info > > I have 2 emulation servers in total, with 2 nodes running OLSR inside a > container on each (started using the CORE GUI). > > Nodes on the same machine can communicate fine, but not nodes on > different machines. > > Using tcpdump I can see that OLSR broadcast packets are reaching the > emane daemon running in the node containers on different machines. > > Does anyone know what my problem might be or how to debug it further? > > I'm running emane 0.9.2 and core 4.8. I've attached the emane configs > generated by core for one of the nodes in case that helps. The configs > are identical on the other machine except for nem and tap ids. > > Thanks, > Dan > > > _______________________________________________ > emane-users mailing list > [email protected] > http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users > _______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
