11-09-2010 12:39 PM
-)))(((- ----- -----
SERVER IP: 10.1.50.21
The user role that the laptop is using will allow any on the network. So it has full access to the network when it’s connected to the correct SSID.
We are testing a DST-NAT rule. When we use the DST-NAT rule everything works fine except for FTP. In other words, the rule is set so that the LAPTOP can communicate with the FTP SERVER on IP 22.214.171.124.
Here is the dst-nat rule:
Source : Destination : Service : Action
Any : host 126.96.36.199 : any : dst-nat ip 10.1.50.21
I am using FileZilla as the FTP Client and FileZilla as the FTP Server. As soon as the client sends a PASV command, the communication between the server and client stops. If I try to do this from the laptop to the server on the regular IP’s everything works fine. Also if I try some other protocols like SSH, SFTP, RDP over the dst-nat 188.8.131.52 IP etc.. it works fine.
Any ideas if there is a bug that needs to get resolved? This is on ArubaOS 184.108.40.206. If anyone would like to test this they should be able to add the same dst-nat rule like I have and nothing on the SSID will be affected. The only difference is that now you will be able to talk to the device pointing to a different IP.
11-10-2010 03:27 AM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
Validated Reference Design Guides : http://community.arubanetworks.com/t5/Validated-Reference-Design/tkb-p/Aruba-VRDs
11-18-2010 08:03 AM
I am afraid currently Aruba does not support Passive FTP if the inside traffic is natted under the VLAN interface. However RFE (Request for enhancement) has already been filed in regard to this issue ani believe we will get the fix soon.