Ben, The Comm Effect Model only uses Comm Effect events. When 'defaultconnectivity' mode is enabled - which by your xml it is not, it is disabled upon reception of the first Comm Effect event.
You cannot use the matrix based commeffectgenerator in this case. This legacy event generator requires sequential NEM ids starting a 1. You have flow control enabled in your virtual transport configuration. The Comm Effect Shim does not support flow control. In transvirtual.xml change: <param name="flowcontrolenable" value="on" /> to <param name="flowcontrolenable" value="off" /> -- Steven Galgano Adjacent Link LLC www.adjacentlink.com On 06/10/2013 07:18 AM, Ben Stern wrote: > Steve, > > Thank you for the information. In response to the below, I am now using > only one EMANE Event daemon. tcpdump confirms that event packets are being > sent and received on eth1. > > I have examined the Comm Effect Model chapters, and have a scenario with the > attached configurations. I have tried both the textual and the EEL pathloss > scripts, as attached, and I consistently get messages that since the default > connectivity mode is off, no packets will be sent until a pathloss or > location event is generated. > > I have intentionally configured that behavior, but I also have included > pathloss, commeffect, and location events in my scripts/EEL. > > Can anyone explain why my comm effects are not being interpreted? I am > clearly overlooking something. > > Thanks, > Ben > _______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
