This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Hello, I would like to suggest a feature to allow configure external address of active FTP. I have issues receiving errors like: 500 I won't open a connection to 192.168.1.xxx (only to 78.56.xx.xxx) It is because I am behin a router and Netbeans passes wrong IP (my local one instead of external), so I really cannot use Active FTP. Other software (like Filezilla for example) has a great configuration over this including limiting port ranges, entering external IP over active ftp and etc., so I think introducing it into Netbeans would allow to use Active ftp in all cases with external IP input there. Thanks!
For FTP, NetBeans uses Apache Commons Net [1] - feel free to have a look whether such configuration option is available. If yes, it could be done quite easily. Thanks. [1] https://commons.apache.org/proper/commons-net/
Thank you for reply, as documentation states (https://commons.apache.org/proper/commons-net/apidocs/org/apache/commons/net/ftp/FTPClient.html) it do have such feature: void setActiveExternalIPAddress(String ipAddress) Set the external IP address in active mode. So just a simple textbox field for entering IP address there would be just fine, and during active connection check for if(active_mode_external_ip != NULL){ setActiveExternalIPAddress(configuration.external_ip_addr); }
Also there is function: void setActivePortRange(int minPort, int maxPort) Set the client side port range in active mode. So setting of port ranges are also available, which would be just great!
In such a case, it could be done. Thanks for investigating it!
Any news when this may become available? Thanks.
No idea now, busy working on other areas, sorry. Will try to look at it soon. Thanks.
Hopefully there will be a place for these new fields...
Should be done now, please verify. Thanks. http://hg.netbeans.org/web-main/rev/cd87a1216d89
I have downloaded Build 201601120002 (nightly), but I see it is not there yet, so cannot test.
Please, wait for a message that will appear here automatically. It will tell you in which daily build this change will be available. Thanks.
Integrated into 'main-silver', will be available in build *201601130002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/cd87a1216d89 User: Tomas Mysik <tmysik@netbeans.org> Log: #255982 - Active FTP external ip assign
Hey, Just tested - now that's we are talking!!! Using active ftp project syncs, downloads and upload from ftp are hundreds of times faster than in passive mode. However didn't checked the fields validations, but they should be fine, they are just an integer and IP fields. It also can be updated that if no ports are defined, they are automatically selected (not executing ports command, only IP assing), but that's fine. What is great, that I can enter different ports for different projects - that's actually a feature over other software, which use same ports for all connections, quite a novel! Thanks a lot, waiting this to be in live version!
Thanks for your feedback, marking as verified.
Hello. I found an issue with active FTP (ports section). In project I define active ports range 49500 - 65400. Same goes on my NAT forward on router (49500 - 65400). I do occasionally see an errors like "425 Unable to build data connection: Connection refused". After I started to analyze what's wrong I found an issue - FTP client on netbeans tries to execute this command: PORT 192,168,1,xxx,192,206 <- My internal IP, and last two comma imploded values are port, which is described as (192 DEC -> C0 HEX and 206 DEC -> CE, combining them as C0CE HEX -> 49358 DEC). So it tries to connect to port 49358 where I have ranges 49500..65400. I am not sure if it's an apache ftp client bug, or command called in wrong time (before connection established) or with empty/wrong parameters. From source code it looks like everything is fine, but I think it should be good thing to debug "ftpClient.setActivePortRange(activePortMin, activePortMax);" section to check what values are applied and if it even being executed at all. After a lot of tries in eventually fits into 49500..65400 range (because port count increased every connection) and works fine. After increase overcomes 65400 range it goes to 65535 port causing issues again.
Please, do not reopen verified issues. Report a new one. Thanks.