Date: Sun, 12 Nov 2006 01:15:42 +0100 From: Daniel Hartmeier <daniel@benzedrine.cx> To: Kimi Ostro <kimimeister@gmail.com> Cc: freebsd-pf@freebsd.org Subject: Re: Having a couple of issues Message-ID: <20061112001542.GQ6819@insomnia.benzedrine.cx> In-Reply-To: <42b497160611111538g6e07d972r5d0d6a577e43efc4@mail.gmail.com> References: <42b497160611111207t2e168afdnba91607fd66371d2@mail.gmail.com> <200611112329.43326.max@love2party.net> <42b497160611111504q3a287bf9qa439e62deac62c36@mail.gmail.com> <20061111232425.GO6819@insomnia.benzedrine.cx> <42b497160611111538g6e07d972r5d0d6a577e43efc4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 11, 2006 at 11:38:53PM +0000, Kimi Ostro wrote: > The clients are users of FreeBSD, KDE and Mozilla Firefox. > > So I guess it is harmless? am I the only one to have this issue?? I > did not find much about it. I'd say it's harmless. It could be interesting to find out why this just popped up now, after having been undetected for years before. I'm just curious about why a client would do that. Maybe it is somehow related to how client stacks react to running out of source ports under high connection establishment rates. Something like dropping one tcpcb that is not yet fully established to free up a port for another new connection? And generating a RST to the peer of the dropped tcpcb? Has something like that been added or enabled by default recently in FreeBSD? Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061112001542.GQ6819>