From owner-freebsd-questions Fri Apr 26 6:44:15 2002 Delivered-To: freebsd-questions@freebsd.org Received: from gamma.root-servers.ch (gamma.root-servers.ch [195.49.62.126]) by hub.freebsd.org (Postfix) with SMTP id 733E737B416 for ; Fri, 26 Apr 2002 06:44:08 -0700 (PDT) Received: (qmail 16266 invoked from network); 26 Apr 2002 13:44:05 -0000 Received: from dclient217-162-131-134.hispeed.ch (HELO athlon550) (217.162.131.134) by 0 with SMTP; 26 Apr 2002 13:44:05 -0000 Date: Fri, 26 Apr 2002 15:46:45 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.60c) Educational Reply-To: gabriel_ambuehl@buz.ch Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <172180938515.20020426154645@buz.ch> To: Bill Moran Cc: questions@freebsd.org Subject: Re[2]: dhclient going crazy... In-Reply-To: <3CC95A01.5000908@potentialtech.com> References: <1965488492.20020424150235@buz.ch> <3CC86D86.7060100@potentialtech.com> <158162746907.20020426104334@buz.ch> <3CC95A01.5000908@potentialtech.com> 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 -----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. Best regards, Gabriel -----BEGIN PGP SIGNATURE----- Version: PGP 6.5i iQEVAwUBPMlMOcZa2WpymlDxAQGUIQgApFhbKy5h7FMldNSPqxeJfSc1S6GT6rI4 xcextJL6Pz2x3nX6Yo84HpegRSZ02mcX0P9HXvjtqOskF9i1rVAdpLYBerwkSG3e u6djnBSaJuihGxCSjfiU4ZPlGHlqrZTqeiT2leFm9IX4pDH8ghytPgqDm+6uM6XP WRS7dbpMsJT7wtU5yhlFIQ/SUA9k29AN4ABYE2rjnr+xzwa972lmtRH2gEu80+kv O+tvLacoSLJ6jpD1G8JDMi/YElyXEtIcb7mtvLqpVrIgtOjKPW51o3rk87whxHrH V9vg6//b7CeyQFHA+sDGQ1mvIpAfK7akTiKKo2tuj4wAKByKK3sgZQ== =SaSC -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message