From owner-freebsd-questions Tue Apr 30 2:58:42 2002 Delivered-To: freebsd-questions@freebsd.org Received: from sub21-156.member.dsl-only.net (sub21-156.member.dsl-only.net [63.105.21.156]) by hub.freebsd.org (Postfix) with ESMTP id D55A537B425 for ; Tue, 30 Apr 2002 02:58:14 -0700 (PDT) Received: from freebsd.localhost.local (localhost.localdomain [127.0.0.1]) by freebsd.localhost.local (8.11.6/8.11.6) with SMTP id g3QGQ9P01769; Fri, 26 Apr 2002 09:26:14 -0700 (PDT) (envelope-from nkinkade@dsl-only.com) Date: Fri, 26 Apr 2002 09:26:09 -0700 From: Nathan To: gabriel_ambuehl@buz.ch Cc: questions@freebsd.org Subject: Re: Re[2]: dhclient going crazy... Message-Id: <20020426092609.2ce17e4c.nkinkade@dsl-only.com> In-Reply-To: <172180938515.20020426154645@buz.ch> References: <1965488492.20020424150235@buz.ch> <3CC86D86.7060100@potentialtech.com> <158162746907.20020426104334@buz.ch> <3CC95A01.5000908@potentialtech.com> <172180938515.20020426154645@buz.ch> X-Mailer: Sylpheed version 0.7.4 (GTK+ 1.2.10; i386-portbld-freebsd4.5) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 26 Apr 2002 15:46:45 +0200 Gabriel Ambuehl wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Hello Bill, > > Friday, April 26, 2002, 3:45:37 PM, you wrote: > >> DoS but thought that there might be a bug in the dhclient. > > Did you reboot the box? FreeBSD isn't very prone to binary > > corruption, but (theoretically) it's still possible. I wouldn't > > blame dhclient itself, though, as I've run it for years with no > > problems. If your dhclient is acting up you probably need to do > > buildworld again. > > That I had already scheduled but postponed it until I could > run cvsup again. We'll see how it's going once I'm finished with it. > > >> Actually, there's a whole lot of those ARP changes for the GW, > >> could it be that dhclient went crazy about it? > > dhclient shouldn't have any reason to change MAC addresses. > > Yeah sure but the DHCP *server* changed its... > > >> That's originally what I expected to be the reason too but the NOC > >> guy > >> told me that they're running with 60min leases. > > Yeah, but remember that you're running things in a sane manner, and > > if they (for some unknown reason) went wacko, you'd think that it > > must be the other guy as well. > > Oh we all are familiar with the fact that this industry does even > more > fingerpointing than most others... > > > my first reaction is "what did you break" (because usually that's > > true) Then later I find that my systems are wacked out. Only > > Yeah I know. But as I'm admin myself, I wanted to speak with the NOC > guys which the helpdesk wouldn't let me do, stating they haven't got > the number of the NOC anyway... > > > difference is that I'll admit my mistake to the customer. > > ACK (maybe not if the mistake really was too stupid ;-) > > >> Neither did I. The box in question has a somewhat doubtful > >> internal (dc0) interface that would generate watchdog alerts from > >> time to time since a few week but despite it was running for more > >> than a year without a single problem. I sure did upgrade it from > >> time to time but as STABLE really is stable for the very most > >> part, I never ever > >> encountered any trouble while on it... > > Well, definately take a minute to email me if you ever figure > > it out. I'd be curious to know what's up. > > Will sure post it to the list as others seem to be interested also. Do you have a protocol analyzer, like ethereal, that you could run when this happens - or possibly you could setup rules and run it all the time for a while? I'm wondering if there is any other strange activity that's just not getting logged by dhclient. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message