Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Jan 2003 10:34:35 +1030
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        Bill Moran <wmoran@potentialtech.com>
Cc:        bsdaemon@mail.com, ukla@attbi.com, freebsd-questions@FreeBSD.ORG
Subject:   Re: Bazillion kernel messages?
Message-ID:  <20030111000435.GA87427@wantadilla.lemis.com>
In-Reply-To: <3E1EDA8E.4010403@potentialtech.com>
References:  <20030110010009.88318.qmail@mail.com> <3E1EDA8E.4010403@potentialtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
[Format recovered--see http://www.lemis.com/email/email-format.html]

On Friday, 10 January 2003 at  9:37:02 -0500, Bill Moran wrote:
> bsdaemon@mail.com wrote:
>> From: Steve Warwick <ukla@attbi.com>
>>
>>> I have a bazillion of these kernel messages showing up in my logs...
>>>
>>> Jan  9 13:53:30 la last message repeated 7 times
>>> Jan  9 13:59:21 la /kernel: arp: 00:05:32:0e:64:12 attempts to modify
>>> permanententry for 12.158.234.65 on rl0
>>>
>>> I know rl0 is my ethernet but I don't host the .65 address. I have
>>> not seen these before - does anyone know what these messages mean?
>>
>> No help here, but I get this (alot) and I've seen it discussed, but no
>> resolution (if one is needed):
>> ...../kernel: arp: [address] has moved to [different] address on [cable
>> modem mac address]
>>
>> I'd be interested in any suggestions, as well.
>
> These are two different issues.  The "[address] has moved to
> [different] ..." message is simply caused by DHCP giving different
> addys to different computer as they turn on and off on the cable
> network.  It's not really anything to be concerned with.

That's not the only possibility.  It could be two machines both
insisting that the address is theirs.  That *is* an issue to be
concerned with.

> I'm not sure what Steve's problem is, but it sounds like a
> something's wrong.  If I were you, I'd do a little research to find
> out what computer has 00:05:32:0e:64:12 and see what software is
> running on it.  That may get you pointed toward the cause/solution
> of the problem.

You could also try connecting to it with ssh or rlogin or some such.
That should help you identify which machine it is more easily.

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030111000435.GA87427>