A nullspace bundle is a bundle for the Network Coding router, that lets other nodes know what data they have. Usually they're one-hop bundles, but they are addressed as stated above. All nodes in the NC router should be receiving them intermittently so they know when they can stop passing data back and forth. When I say they are bouncing back essentially want is happening is that Node A wants to update Node B with a nullspace bundle. Node B receives it, and for some reason it then gets queued up to get sent back to Node A. The real problem then is that Node A receives the bundle again and thinks that it's from Node B and thinks that Node B is equivalent to itself.
From what I've seen in the NeighborRoutingExtension, in the ShouldAdd function, the line:
if (_entry.eid.getNode() != meta.destination.getNode())
in the older version was not part of a if (meta.get(dtn::data::PrimaryBlock::DESTINATION_IS_SINGLETON)) block. If none of the destinations are marked as singletons, won't this change the router's behavior significantly?
Thanks,
Carson