Brian J. Murrell

But it's using the `clush` to replace `pdsh` that is my use-case. :-( Can we make this an RFE then?

I wasn't saying it was possible with `pdsh`. I was looking to `clush` as a replacement, to be better than `pdsh` but unfortunately this is one area where it isn't.

No, not a blocker and agreed, that CS does already have lots of interesting features over pdsh.

I suppose a more useful example would be: ```bash $ cluset -e wolf-100vm3,wolf-[122-129] wolf-122 wolf-123 wolf-124 wolf-125 wolf-126 wolf-127 wolf-128 wolf-129 wolf-100vm3 ``` to demonstrate why I want to use...

The existing behaviour for that is fine: ``` wolf-122 wolf-123 wolf-124 wolf-125 wolf-126 wolf-127 wolf-128 wolf-129 ``` So generally speaking I would say expanding left to right, maintaining order, suppressing...

Any ideas on this ICE failure?

In any case, the above was a failed call. Best I can tell it failed to complete an ICE negotiation. For seconds into the call the call status in linphone-android...

It does seem like the openvpn addresses (IPv4 and IPv6) should be in the candidate list and are not. Correct?

Any thoughts here? I did reopen this after closing it (prematurely as it turns out), in case that wasn't clear in the ticket history.

Any ideas here? This failure seems to make linphone unusable when it's behind any IPv4 NAT. :frowning: