Let me rephrase what Gabriel said.
- ns-3.26 is 10-years old, and we can't offer reliable support (or even fully meaningful suggestions) on it.
- aomdv was (is) an external contributed model, so the maintainers never had the chance to fully comb though it.
Said so, I can give you a hint, but not a solution.
Packet Tags and Byte Tags are nifty solutions to add metadata to a packet - something that inside an OS is usually very common. Of course they're lost when you actually transmit a packet, so using a tag that the sender did add to the packet on reception is definitely a bad idea. You can use them in a simulation to simplify some operations, but they're not something that a real protocol could use.
What is (probably) happening here is that AOMDV is adding a tag when you transmit a packet and that tag is not removed before sending the data on the wire. Perhaps it's even used by intermediate nodes or on reception. Something that I would definitely classify as a no-no.
Ping takes the packet it receives and turns it to a reply, so if the tag has not been removed, you'll end up with a trying to transmit a packet whose data has been already tagged, and a crash.
The solution might range from a dirty fix (remove the tags before passing the packet to the upper layers) to a more serious question: is the AOMDV model using tricks that makes it so unrealistic that its results are unreliable?
SO, the question leads back to what Gabriel asked (a little bit expanded): are you sure you want to use a 10-years old ns-3 and a model that has some red flags waving around?
In both cases, we're sorry but we can't help you more than this.