Product Release: Jan 13, 2013
Release Notes Updated: Jan 13, 2014
Release 1.0.3 of Aspera Proxy provides a fix for the issue listed below.
ISSUES FIXED IN THIS RELEASE
When reverse proxy is configured with <source_port_filtering> turned off (set to false), a transfer's source address will consist only of an IP address (with no port) in the proxy rule.
In such cases, when the internal server is Windows, or when <udp_port_reuse> is set to false on the internal server, the first transfer uses UDP port 33001, the second uses 33002, and so on. However, the forwarding rules will not allow additional transfers to proceed, because the UDP packets of subsequent transfers will always be forwarded to port 33001 (via the first proxy rule), which can only be used by the first transfer.
This release of Proxy provides a means of addressing the above scenario. Now, if <proxy_port> is set to 0 (zero), the proxy server will use the same port as the internal server to receive UDP traffic from the client. Note that for this to work, those ports (33001, 33002, and so on) will also have to be open on the external firewall.
Known issues identified in Aspera Proxy 1.0.2 Release Notes are still current.
Do not install Aspera Proxy on a machine where Aspera Enterprise Server or Connect Server is installed. If these products are already installed, be sure to remove them before installing Aspera Proxy.
Linux (RedHat or Debian) with kernel 2.4 or higher and libc version GLIB 2.3.4 or higher.
PREVIOUS RELEASE NOTES
Aspera Proxy 1.0.3 Admin Guide (Linux) [PDF only]
For online support resources for Aspera products, including raising new support tickets, please visit our 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.