Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Jun 2004 12:05:35 -0500 (CDT)
From:      Mike Silbersack <silby@silby.com>
To:        Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>
Cc:        freebsd-net@freebsd.org
Subject:   Re: net.inet.ip.portrange.randomized=1 hurts
Message-ID:  <20040601120412.B63021@odysseus.silby.com>
In-Reply-To: <20040601120238.B44353@atlantis.atlantis.dp.ua>
References:  <20040601120238.B44353@atlantis.atlantis.dp.ua>

next in thread | previous in thread | raw e-mail | index | archive | help

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@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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040601120412.B63021>