IBM Power Ideas Portal
This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Power Systems Development
IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it. IBM will use votes and comments from others in the community to help prioritize this request.
The CAAC has reviewed this requirement and recommends that IBM view this as a “nice to have” low priority feature. The world is moving away from FTP because of security concerns. Though this would be nice to have, there is a limited number of members of the community that would use it. Folks use products like "Go Anywhere", or use Drop box, or other file sharing options.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CAAC, see www.common.org/caac
For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/
Nancy Uthke-Schmucki - CAAC Program Manager
What's the problem you saw on win7/8/10 ftp client to IBM i ftp server?
Could you open a PMR for this issue? You'll get full support from our level 2 team to figure out what's wrong and if it is a bug in IBM i ftp server, we will fix it.
QIBM_QTMF_SERVER_REQ is designed to restrict the ftp operation. So, it is not desired to extend this exit point to add an IP address.
As for adding an ip address to QIBM_QTMF_SVR_LOGON and returns this IP to client in PASV, this does add some flexibility to ftp: it is possible to select different interface, maybe interfaces on other machines, for different user or client IP address.
It works only for IPv4, not for IPv6. IPv6 EPSV does not return IP address to ftp client and by default the ftp client should use the same IP address of the ftp server control channel.
As for this specific problem, I prefer adding retry logic in the ftp client.
When switching to PASV mode, FTP server uses the IP address where it receives the FTP client request.
Looks like this requirement requests to specify an IP address and pass this IP address to ftp client.
Perhaps, it is more easier to define a dataarea to specify which IP address is preferred for PSAV.
This is doable. But the problem is for IPv6 EPSV, the IP address field is removed and only the listen port is kept in the EPSV reply packet. The ftp client should connect to the port returned from EPSV reply packet on the ftp server IP address to establish ftp data connection.
Maybe, the more simple way is to ask ftp client not using the IP address returned by the PASV packet. Ftp client can connect to the data port on the same ftp server IP address.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Networking
Operating system - IBM i
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Core OS
Operating system - IBM i
Source - None
When I created this request, I was thinking the QIBM_QTMF_SVR_LOGON exit program could return the IP address to be used on every PASV reply to the FTP client, and would be set as a global value for the FTP session being initiated.
Another option would be to modify the QIBM_QTMF_SERVER_REQ exit point to allow the exit program to return the desired IP address for the PASV reply on each FTP client request.