'Local port range' bug

Perplexer · 05-10-2006, 05:34 PM

* FlashFXP v[3].[2], build [1080 ], [ ]registered, [X]unregistered, [ ]pirated
* OS [X ] WinXP, [ ] Win2K, [ ] Win98, [ ] WinME, [ ] Other
* Running behind NAT/router [X, ICS] Yes & Model [ ], [ ] No, [ ] Not sure
* Running firewall [X, ICF] Yes, Name [ ], Ver. [ ], or [ ] No
* Running Antivirus [ ] Yes, Name [ ] or [X] No
* Network [X] xDSL, [ ] CABLE, [ ] Dail-Up, [ ] Other

Installed FlashFXP 3.2.0 (build 1080) STABLE and I am experiencing difficulties with the "Limit local port range to" setting for active (PORT) connections. FlashFXP often sends the wrong port (PORT) to the server. I have the range set to 49873-49873 (1 port). Most PORTs are OK (PORT 132,275,258,36,194,209) but it often goes out of the specified range (for example PORT 132,275,258,36,8,149) when CWD-ing on both sides at the same time, which causes connection to fail (firewall). (note: IP mangled for this post).

The bug can be replicated by connecting to two sites (in active mode) and doing (near) simultaneous dir changes (CWD) on both sites.

The newest beta has the same bug.

Any ideas ?

UPDATE: I opened another port on the firewall and extended the port range to include 2 ports. That seems to work and doesn't make FlashFXP request connections on random out-of-range ports anymore. Admins can therefore remove this post if so desired.

bigstar · 05-10-2006, 10:56 PM

Just for reference, we recommend at least 10 ports per instance of FlashFXP.

If none of the ports are available within the port range than a random port is used.