On Sun, 20 Jan 2008, s3raphi wrote:
I am running web polygraph against a FreeBSD7.0-RC1 squid server and
experiencing problems. I have run the same test against the same hardware on
FreeBSD 6.1 without issue. This seems to be specific to FreeBSD 7.
The problem is related to the number of client
*Originally posted to [EMAIL PROTECTED] mailing list but moved
here. Original may be found at
http://www.nabble.com/FreeBSD-7.0-RC1-syncache-problems-under-high-load-to14977783.html#a14981104
I am running web polygraph against a FreeBSD7.0-RC1 squid server and
experiencing problems. I have run th
Robert Watson wrote:
On Wed, 25 Jul 2007, Mike Silbersack wrote:
On Fri, 20 Jul 2007, Peter Wemm wrote:
TCP: [127.0.0.1]:52446 to [127.0.0.1]:1128 tcpflags 0x10;
syncache_expand: Segment failed SYNCOOKIE authentication, segment
rejected (probably spoofed)
[...]
How on earth can localhost be
On Wed, 25 Jul 2007, Mike Silbersack wrote:
On Fri, 20 Jul 2007, Peter Wemm wrote:
TCP: [127.0.0.1]:52446 to [127.0.0.1]:1128 tcpflags 0x10;
syncache_expand: Segment failed SYNCOOKIE authentication, segment
rejected (probably spoofed)
[...]
How on earth can localhost be spoofing itself? This
On Fri, 20 Jul 2007, Peter Wemm wrote:
TCP: [127.0.0.1]:52446 to [127.0.0.1]:1128 tcpflags 0x10;
syncache_expand: Segment failed SYNCOOKIE authentication, segment
rejected (probably spoofed)
[...]
How on earth can localhost be spoofing itself? This is getting quite
absurd. :-(
Any extra ACK
I was unable to apply Mike's patch so I have manually applied it. Here
is a new one that should apply against today's -CURRENT.
Cheers,
Index: tcp_syncache.c
===
RCS file: /home/ncvs/src/sys/netinet/tcp_syncache.c,v
retrieving revi
On Tuesday 10 July 2007, Mike Silbersack wrote:
> On Tue, 10 Jul 2007, Eygene Ryabinkin wrote:
> > Can't say that I am pushing much traffic through my box, but after
> > applying your patch and rebuilding the kernel I am still seeing the
> > messages like
> > -
> > TCP: [209.132.176.NNN]:NNN to
Good day.
Wed, Jul 11, 2007 at 10:04:23AM +0400, Eygene Ryabinkin wrote:
> OK, maybe I have something that can be related to this bug. It
> provokes another message, 'Spurious RST', but can be correlated
> with your guess. What is happening is that when one side closes
> the connection and relea
Robert Watson wrote:
On Tue, 10 Jul 2007, Mike Silbersack wrote:
On Tue, 10 Jul 2007, Eygene Ryabinkin wrote:
Can't say that I am pushing much traffic through my box, but after
applying your patch and rebuilding the kernel I am still seeing the
messages like - TCP: [209.132.176.NNN]:NNN
On Tue, 10 Jul 2007, Mike Silbersack wrote:
On Tue, 10 Jul 2007, Eygene Ryabinkin wrote:
Can't say that I am pushing much traffic through my box, but after applying
your patch and rebuilding the kernel I am still seeing the messages like
- TCP: [209.132.176.NNN]:NNN to [144.206.NNN.NNN]:N
Mike, good day.
Tue, Jul 10, 2007 at 08:29:14PM -0500, Mike Silbersack wrote:
> The fact that you're still getting the syncache_expand message tells me that
> there's another bug which I have not yet fixed still present.
>
> My suspicion is that the "Segment failed SYNCOOKIE authentication" mess
On Tue, 10 Jul 2007, Eygene Ryabinkin wrote:
Can't say that I am pushing much traffic through my box, but after
applying your patch and rebuilding the kernel I am still seeing the
messages like
-
TCP: [209.132.176.NNN]:NNN to [144.206.NNN.NNN]:NNN tcpflags
0x19; syncache_expand: Segment fa
Mike, good day.
Tue, Jul 10, 2007 at 12:20:49AM -0500, Mike Silbersack wrote:
> Anyway, the attached patch simplifies the syncache structure a bit and
> makes it retransmit properly. I'd appreciate testing from anyone who
> has experienced TCP problems with FreeBSD 7, as well as anyone who is
> p
On Tue, Jul 10, 2007 at 12:20:49AM -0500, Mike Silbersack wrote:
>
> I've found one of the causes of the network instability of FreeBSD 7; the
> tcp syncache fails to retransmit SYN-ACK packets. This causes interesting
> problems when packet loss is experienced during connection setup. The
>
14 matches
Mail list logo
