When you launch the CLI you can pass a --bind=xxx param which then controls the client side bind address used for connections. But you can't specify this with the connect command itself.

This is minor; I just noticed it while experimenting with the fix for WFCORE-2225 when I wanted to confirm the fix was working by using the CLI.

Also, I noticed that if I did a "connect --bind=192.168.1.10" the CLI accepted the invalide command.