Release Notes: IBM Aspera FASP Proxy 1.3.0
Product Release: Mar 4, 2016
Release Notes Updated: March 4, 2016
This release of IBM Aspera FASP Proxy provides the new features, fixes, and other changes listed below.
- A new configuration option, udp_port_reuse, has been
added to aspera.conf. This option defaults to true. When it
is set to false, the UDP port returned to the client is based on an index of
concurrent transfers running through the proxy server.
This option allows concurrent transfers to Windows nodes to work through the reverse proxy both with and without load balancing enabled.
- Reverse proxy (ascp_rproxy and ascmd_rproxy) can no longer be started except by aspshell. If not started by aspshell, reverse proxy now fails with an error message.
- The status of asperaproxy can now be checked with the following
# service asperaproxy status
- Setting <proxy_port> to zero in the proxy server's aspera.conf no longer enables the routing of concurrent transfers to successive ports; instead, it now generates an error and results in a failure to make the transfer. This feature is now enabled by setting <udp_port_reuse> to "false". For further information, see the topic "UDP Port Reuse" in the Aspera FASP Proxy 1.3.0 Admin Guide.
- Note: Proxy 1.3.0 now requires exclusive control of the following
ISSUES FIXED IN THIS RELEASE
#34694 - asuserdata -s does not display the <balancing> tag.
#34476 - The Proxy log ERR failed to touch the rule group entry invalid seq 1.
#34294 - For security reasons, Aspera is removing the default masquerade rule and disabling the default forwarding policy used on both the forward and reverse proxy products.
#34288 - aspera-proxy fails to start, and dpkg -r aspera-proxy fails to uninstall.
#34141 - Reverse proxy does not always return the FASP port to the source client; it only does this when the udp_port is set to 0. Workaround: use <src_port_filtering>true</src_port_filtering>.
#33601 - ascp_rproxy is not allowed to connect to another ascp_rproxy.
Linux 64-bit: RedHat 6, CentOS 6, Fedora 15-20, Ubuntu 12-14, Debian 6 & 7, SLES 11, Kernel 2.6 or higher, and libc version GLIB 2.3.4+.
PREVIOUS RELEASE NOTES
Aspera Proxy 1.2.2 Release Notes
Aspera Proxy 1.2.1 Release Notes
Aspera Proxy 1.1.1 Release Notes
Aspera Proxy 1.1.0 Release Notes
Aspera Proxy 1.0.3 Release Notes
Aspera Proxy 1.0,2 Release Notes
Aspera Proxy 1.0.1 Release Notes
Aspera Proxy 1.0.0 Release Notes
Aspera Proxy 0.9.1 Release Notes
md5: 8e478bcd824694aa67fa6cef619278eb sha1: 3222a5212b5aeb7f5290bb6897e8df97d4bda8cd
md5: 68e8fb6a54a8911e95683f346cd815fe sha1: 9b1eac7891406b1cb19b053a7dd0a1a47271e805
#19185 - A log file is created with proxy user permission, preventing a subsequent user from writing in it.
#34615 - Forward proxy is creating rules for UDP from SCP GUI connection, which it is not supposed to do.
#24270 - Transfers cannot be made to a server with a docroot on Azure if routed through an Aspera Proxy server.
#24012 - Rules created in reverse proxy for host_domain are not respected.
#21288 - On some Linux platforms (for example, SUSE) the iptables-restore command is not located in /sbin but /usr/sbin. Workaround: Create a symlink in /sbin for /usr/sbin/iptables-restore.
#19205 - Proxy does not support HTTP fallback.
#19202 - Proxy does not currently support reverse proxy for web applications.
#19185 - If you specify a directory for <log_dir>, the log file is created with 0640 permissions. As a result, not all transfers will be logged. Workaround: Once the log file has been created, change its permissions to 0660.
For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.