On 26 Nov 2005, at 3:53 AM, Gleb Smirnoff wrote:
the ARP problem in RELENG_6 is fixed in revision 1.137.2.6 of
if_ether.c.
The problem was introduced in revision 1.137.2.5. Make sure that
you have
revision 1.137.2.4 or revision 1.137.2.6.
It was kind of a sticky situation: I could not s
Colleagues,
the ARP problem in RELENG_6 is fixed in revision 1.137.2.6 of if_ether.c.
The problem was introduced in revision 1.137.2.5. Make sure that you have
revision 1.137.2.4 or revision 1.137.2.6.
I'm sorry for the problems that I've caused to you.
--
Totus tuus, Glebius.
GLEBIUS-R
On Sat, Nov 26, 2005 at 12:08:08PM +0700, Hendry Sarumpaet wrote:
H> >> The following change appears to have crashed my network today.
H>
H> > Ditto, this killed both my wireless and wired interfaces upon a cvsup to
H> > the latest RELENG_6. It just sent a continuous stream of ARP queries,
H> > m
Dan Allen wrote:
> The following change appears to have crashed my network today.
Ditto, this killed both my wireless and wired interfaces upon a cvsup to
the latest RELENG_6. It just sent a continuous stream of ARP queries,
many per second, despite getting replies and populating the routing
tabl
On Wed, Oct 27, 2004 at 11:12:33PM +0400, Gleb Smirnoff wrote:
> If we are interested in tracking this down, we should add a printf,
> so that people who hit this will notce it and report.
> Otherwise this problem will be left forever in a workaround state.
That's what revision 1.109 was for, but
Bruce,
On Mon, Oct 25, 2004 at 08:41:26PM -0700, Bruce M Simpson wrote:
B> On Tue, Oct 26, 2004 at 03:31:59AM +, Bruce M Simpson wrote:
B> > Log:
B> > Check that rt_mask(rt) is non-NULL before dereferencing it, in the
B> > RTM_ADD case, thus avoiding a panic.
B>
B> PR: kern/42030
B>
On Tue, Oct 26, 2004 at 03:31:59AM +, Bruce M Simpson wrote:
> Log:
> Check that rt_mask(rt) is non-NULL before dereferencing it, in the
> RTM_ADD case, thus avoiding a panic.
PR: kern/42030
It isn't immediately clear to me if this is a routing socket API issue
or a client issue.
T
