Jason and I (James M.) were able to identify the connection issues we observed with ascli when running multi-session transfers to the cloud. UDP port numbers are being incremented from port '33001' for participating multi-session ascp transfers. This is normally desirable - Though for transfers into our cloud nodes, we restrict FASP UDP traffic to port 33001, rather than exposing a range.
Another feature request/proposal: Could we consider making the port-incrementing behavior for multi-session transfers optional by default? Or perhaps disabled by default when transferring to cloud nodes?
Jason and I (James M.) were able to identify the connection issues we observed with ascli when running multi-session transfers to the cloud. UDP port numbers are being incremented from port '33001' for participating multi-session ascp transfers. This is normally desirable - Though for transfers into our cloud nodes, we restrict FASP UDP traffic to port 33001, rather than exposing a range. Another feature request/proposal: Could we consider making the port-incrementing behavior for multi-session transfers optional by default? Or perhaps disabled by default when transferring to cloud nodes?