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

Kris Kennaway kris at obsecurity.org
Tue Jun 1 16:12:22 PDT 2004


On Tue, Jun 01, 2004 at 12:05:35PM -0500, Mike Silbersack wrote:
> 
> 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.

Is this also the cause of the mysql server connection failures
reported on freebsd-stable@?

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20040601/fcb431ee/attachment.bin


More information about the freebsd-net mailing list