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

2004-06-02 Thread Dmitry Pryanishnikov
Hello! > Date: Tue, 1 Jun 2004 19:07:35 -0500 (CDT) > From: Mike Silbersack <[EMAIL PROTECTED]> > > On Tue, 1 Jun 2004, Andre Oppermann wrote: > >> A port should not be reused this fast. Maybe the randomness isn't >> so random after all and choses the same port over again and again? >

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

2004-06-02 Thread Andre Oppermann
Dmitry Pryanishnikov wrote: > > Hello! > > > Date: Tue, 1 Jun 2004 19:07:35 -0500 (CDT) > > From: Mike Silbersack <[EMAIL PROTECTED]> > > > > On Tue, 1 Jun 2004, Andre Oppermann wrote: > > > >> A port should not be reused this fast. Maybe the randomness isn't > >> so random after all a

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

2004-06-02 Thread Barney Wolff
On Wed, Jun 02, 2004 at 12:41:51PM +0200, Andre Oppermann wrote: > > have 16383 non-repeated port numbers before the first repeat). > > The random generator indeed works badly. If it was truely random it > should generate a collision only every (1/range) on average. Maybe > the arc4random functi

5.2.1-R Support for 802.11b USB stick? usbd sees it as ugen0

2004-06-02 Thread Chris Shenton
I've got an olde thinkpad and picked up a "Syntax USB-400" 802.11b interface on a USB stick (heck, it's free after rebate): http://www.freeafterrebate.info/article.php?story=20040301213230483 When I plug it in, usbd sees it as a generic device: ugen0: vendor 0x0967 product 0x0204, rev 1.10/1

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

2004-06-02 Thread Dmitry Pryanishnikov
Hello! On Wed, 2 Jun 2004, Barney Wolff wrote: > Is the problem that the two systems have different ideas of MSL? I haven't changed default net.inet.tcp.msl: 3 on server. Note that on client side, connection never goes to TIME WAIT, because during active FTP server side closes data connec

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

2004-06-02 Thread Don Lewis
On 2 Jun, Dmitry Pryanishnikov wrote: > > Hello! > >> Date: Tue, 1 Jun 2004 19:07:35 -0500 (CDT) >> From: Mike Silbersack <[EMAIL PROTECTED]> >> >> On Tue, 1 Jun 2004, Andre Oppermann wrote: >> >>> A port should not be reused this fast. Maybe the randomness isn't >>> so random after a

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

2004-06-02 Thread Mike Silbersack
On Wed, 2 Jun 2004, Andre Oppermann wrote: > The random generator indeed works badly. If it was truely random it > should generate a collision only every (1/range) on average. Maybe > the arc4random function reuses the same or small number of initial vectors > all over again leading to the same