On Sun, 9 Mar 2008, Jake Rizzo wrote:
The patch didn't work, but doing this:
sysctl net.inet.tcp.tso=0
sysctl net.inet.tcp.sack.enable=0
Allows the client to connect again. Since my ifconfig doesn't show that my
nic supports TSO then I presume it's the sack sysctl that's making it work.
The
The patch didn't work, but doing this:
sysctl net.inet.tcp.tso=0
sysctl net.inet.tcp.sack.enable=0
Allows the client to connect again. Since my ifconfig doesn't show that my
nic supports TSO then I presume it's the sack sysctl that's making it work.
The machine's a webserver serving almost exclu
On Fri, Mar 07, 2008 at 05:53:37PM -0600, David DeSimone wrote:
> Jake Rizzo <[EMAIL PROTECTED]> wrote:
> >
> > 16:04:31.445390 IP (tos 0x20, ttl 109, id 41184, offset 0, flags [DF], proto
> > TCP (6), length 48) x.comcastbusiness.net.22625 > 192.168.1.104.http: S,
> > cksum 0x81e2 (correct), 3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jake Rizzo <[EMAIL PROTECTED]> wrote:
>
> 16:04:31.445390 IP (tos 0x20, ttl 109, id 41184, offset 0, flags [DF], proto
> TCP (6), length 48) x.comcastbusiness.net.22625 > 192.168.1.104.http: S,
> cksum 0x81e2 (correct), 3539746141:3539746141(0) win
On Fri, 7 Mar 2008, Jake Rizzo wrote:
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.
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
