Me again.
Tue, Jun 12, 2007 at 07:26:56AM +0400, Eygene Ryabinkin wrote:
> Mon, Jun 11, 2007 at 09:09:18PM +0200, Andre Oppermann wrote:
> > These messages are unrelated to your hardware. There you can relax.
> > We have a bug in the TCP FSM state transitions which I'm currently
> > tracking down
Andre, good day.
Mon, Jun 11, 2007 at 09:09:18PM +0200, Andre Oppermann wrote:
> These messages are unrelated to your hardware. There you can relax.
> We have a bug in the TCP FSM state transitions which I'm currently
> tracking down that indirectly causes the log messages. You don't
> have to w
At Tue, 22 May 2007 01:48:26 +0100,
"Bruce M. Simpson" <[EMAIL PROTECTED]> wrote:
> > Responsible-Changed-From-To: freebsd-net->bms
> > Responsible-Changed-By: andre
> > Responsible-Changed-When: Sun May 13 18:36:25 UTC 2007
> > Responsible-Changed-Why:
> > Send over to BMS. He's active in that
The following reply was made to PR kern/113548; it has been noted by GNATS.
From: Cristian KLEIN <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/113548: [dummynet] [patch] system hangs with dummynet queues
Date: Mon, 11 Jun 2007 23:35:21 +0300
I think the pr
Eygene Ryabinkin wrote:
Good day.
I had recently upgraded my amd64 box to the 7-CURRENT and started
using nfe(4) instead of nve(4), because the latter was almost
unusable on the moderate traffic flow from the amd64 box to some
other machine due to the watchdog timeouts.
But the stock nfe(4) wa
Good day.
I had recently upgraded my amd64 box to the 7-CURRENT and started
using nfe(4) instead of nve(4), because the latter was almost
unusable on the moderate traffic flow from the amd64 box to some
other machine due to the watchdog timeouts.
But the stock nfe(4) was not good too: it provoke
Current FreeBSD problem reports
Critical problems
Serious problems
S Tracker Resp. Description
a kern/38554 netchanging interface ipaddress doesn't seem to work
s kern/39937 netipstealth
