Re: FTP environment variable -- MIDRANGE-L

Subject: Re: FTP environment variable
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Thu, 12 Feb 2026 18:05:24 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hello Steve,

Am 12.02.2026 um 17:58 schrieb Steve McKay <samckay1@xxxxxxxxx>:

In this example, only 5 ports are available for FTP which means you are limited to 5 concurrent FTP sessions.

This is wrong. It means that you are limited to 5 concurrent *transfers*. Remember, FTP opens a separate TCP connection for each data transfer. Put/get as well as ls!

Is anyone using this environment variable? Is there any impact to your operation? Any specific issues that you saw? Any tips or caveats?

Can't answer your precise questions. I assume this is to counter some "special" cases of firewall-foobar which don't/can't inspect the initial port 21 connection of FTP for the dynamically derived data port. FTP/S (TLS encrypted FTP) comes to mind.

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: FTP environment variable , Steve McKay

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.