Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update

From: Colin Percival <cperciva_at_freebsd.org>
Date: Sat, 09 Dec 2006 18:27:16 -0800
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
Received on Sun Dec 10 2006 - 01:28:52 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:03 UTC