I imagine this may be intentional for some reason, but I've noticed that if the remote side is running bwctld, the -E option is ignored.This can cause problems if the remote side does not have the peer ports open to the host you are testing from, whereas if it would have honored -E, tests would run fine. Its a bit confusing in the current behavior but I suspect the original intent was -E meant "the remote end is not required to have an endpoint but if it does use it because yay coordination". I suspect given BWCTLs support lifecycle we will never fix this, so mostly putting it here for documentation purposes.
I imagine this may be intentional for some reason, but I've noticed that if the remote side is running bwctld, the -E option is ignored.This can cause problems if the remote side does not have the peer ports open to the host you are testing from, whereas if it would have honored -E, tests would run fine. Its a bit confusing in the current behavior but I suspect the original intent was -E meant "the remote end is not required to have an endpoint but if it does use it because yay coordination". I suspect given BWCTLs support lifecycle we will never fix this, so mostly putting it here for documentation purposes.