net.inet.ip.portrange.randomized=1 hurts

[Mike Silbersack]

On Tue, 1 Jun 2004, Dmitry Pryanishnikov wrote:

>  The main question is: how to prevent this situation? Of course, as a
> workaround I can set net.inet.ip.portrange.randomized to zero, but what's
> the real solution? Is it FTP-client or FTP-server that should take care of
> the previous DATA port usage? Or even network stack behaviour should be
> further modified to avoid this collision?
>
> Sincerely, Dmitry
> --
> Atlantis ISP, System Administrator
> e-mail:  dmitry at atlantis.dp.ua
> nic-hdl: LYNX-RIPE

Sounds like something that should be dealt with on the server's end.  Some
of the changes we've made in 5.x might fix the problem, but I don't think
anyone has looked into that specific case.

A simpler solution might be to use passive mode.  I think that you can set
that somewhere in the install options.

Mike "Silby" Silbersack