Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 09 Dec 2006 18:27:16 -0800
From:      Colin Percival <cperciva@freebsd.org>
To:        Adam McDougall <mcdouga9@egr.msu.edu>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update
Message-ID:  <457B7084.9070409@freebsd.org>
In-Reply-To: <20061210014924.GU81923@egr.msu.edu>
References:  <20061210010823.GS81923@egr.msu.edu> <457B621E.3020100@freebsd.org> <20061210014924.GU81923@egr.msu.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Adam McDougall wrote:
> I just tested tcp.closed with 3 seconds, down from 15 earlier but both were 
> unsuccessful.  I will look at the other options as well, but do you have any explanation 
> for why portsnap would use wildly randomish local ports that overlap too quickly
> when fetch does not?  Is that a kernel controlled behavior that I can adjust?

Try setting net.inet.ip.portrange.randomized=0.  This shouldn't make any
difference, but it might.

Colin Percival



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