Exact same problem that i'm having. I confirmed it exists in 7.0 only since
downgrading one of our servers back to 6.3 stable allowed the same clients
to connect again. This seems to work for us as a workaround:
sysctl net.inet.tcp.sack.enable=0
On 3/12/08, d.s. al coda <[EMAIL PROTECTED]>
webserver serving almost exclusively dynamic content - with
sack disabled is it likely to affect performance much?
Thanks,
Jake
On Fri, Mar 7, 2008 at 11:52 PM, Mike Silbersack <[EMAIL PROTECTED]> wrote:
>
> On Fri, 7 Mar 2008, Jake Rizzo wrote:
>
> > Hi,
> >
> > I had
Hi,
I had two 6.3-STABLE boxen which have been happily running away for months
on end now without any problems. Last week I upgraded (via buildworld) both
boxes to 7.0-STABLE. Since then I've had reports of some clients being
unable to connect via tcp. I've seen this happen first hand on an aff
