There is a serius bug in the strongswan patch for dmvpn.
The fault happens when opennhrp tries to tear down a connection (swanctl -t).
While opennhrp specifies both source -S and destination -R options swanctl actually deletes all the peers
to recreate a setup:
set up 3 nodes and configure dmvpn between them.
Then on one of the nodes stop opennhrp. then run:
swanctl -i -c dmvpn -S 10.0.0.1 -R 10.0.0.2
swanctl -i -c dmvpn -S 10.0.0.1 -R 10.0.0.3
This will show as two created session in swanctl
swanctl -t -S 10.0.0.1 -R 10.0.0.2
Running this should delete the session between 10.0.0.1 and 10.0.0.2, but actually deletes both sessions to 10.0.0.2 and 10.0.0.3