From owner-freebsd-questions Mon Sep 20 15: 4:39 1999 Delivered-To: freebsd-questions@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id DACB815409 for ; Mon, 20 Sep 1999 15:04:35 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id IAA26158 for ; Tue, 21 Sep 1999 08:04:34 +1000 (EST) X-BPC-Relay-Envelope-From: areilly@nsw.bigpond.net.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id IAA29024 for ; Tue, 21 Sep 1999 08:04:33 +1000 (EST) Received: (qmail 1649 invoked by uid 1000); 20 Sep 1999 22:04:35 -0000 From: "Andrew Reilly" Date: Tue, 21 Sep 1999 08:04:35 +1000 To: freebsd-questions@freebsd.org Cc: bugs@bugs.au.freebsd.org Subject: dhclient, kernel (STABLE) glitch this morning Message-ID: <19990921080435.A857@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I use the local cable company's internet service. Early this morning, they reconfigured my area's router, so that it looked like a single /22 network. Previously it had appeared to be four separate class-C networks. This caused a few glitches with dhclient, (and the kernel?) which have otherwise performed flawlessly. Actually, dhclient seems to have continued to work OK, but I've uncovered an edge case for /sbin/dhclient-script. The gist of the problem is that when dhclient was given the new netmask, the gateway router address changed from 24.192.49.1 to 24.192.49.1. However, since my IP address did _not_ change, dhclient-script didn't change the routing table accordingly. OK, that wasn't to hard to figure out, and I fixed it by hand. Things still didn't work for a while, and /var/messages started to fill with: Sep 21 07:37:46 gurney /kernel: arplookup 24.192.48.1 failed: host is not on local network Sep 21 07:37:46 gurney /kernel: arpresolve: can't allocate llinfo for 24.192.48.1rt These messages seem to have stopped after about 226 seconds, without any obvious correlation to what I was doing at the time (shutting X applications down in preparation for rebooting). I doubt that the situation will occur again, so I can't really "test" things much further. I suppose I should send-pr something about dhclient-script? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message