From owner-freebsd-questions@FreeBSD.ORG Thu Jul 14 04:49:27 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54E7216A41C for ; Thu, 14 Jul 2005 04:49:27 +0000 (GMT) (envelope-from rjhjr@cox.net) Received: from lakermmtao10.cox.net (eastrmmtai01.cox.net [68.230.240.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id C088B43D45 for ; Thu, 14 Jul 2005 04:49:26 +0000 (GMT) (envelope-from rjhjr@cox.net) Received: from localhost ([68.230.186.138]) by lakermmtao10.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050714044922.MMYR7476.lakermmtao10.cox.net@localhost> for ; Thu, 14 Jul 2005 00:49:22 -0400 Date: Thu, 14 Jul 2005 00:49:25 -0400 From: Bob Hall To: freebsd-questions@freebsd.org Message-ID: <20050714044924.GA2716@kongemord.krig.net> Mail-Followup-To: Bob Hall , freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: DHCP assigned unregistered IP address X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 04:49:27 -0000 Tonight, during a thunderstorm, I shutdown the household FBSD internet gateway. After the storm passed, I booted it up again, only to discover that during the bootup, my ISP's DHCP server had assigned me a new IP address. That wasn't a problem in itself, but the new address was 192.168.100.11, an unregistered address. The result was that I could ping my ISP's DHCP server, but I couldn't do anything that required a URL. When I talked to a tech at my ISP, she couldn't see my modem. She insisted that the IP address wasn't a problem because I had a router. (Huh?) After she scheduled a visit from a tech for tomorrow and I hung up, I released the lease on the unregistered address a few times until the DHCP server gave me a new, registered address. Magically, everthing worked again. When I cancel the tech visit tomorrow, I'll have them check to see if they can see my modem again. Obviously, the unregistered IP address screwed up my system and theirs. My understanding, after extensive reading, is that the unregistered address could only have come from my ISP's DHCP server. However, I don't know why they would have assigned an IP address that screwed up their systems and mine. I'm wondering if dhclient could have assigned this address to itself if it encountered a problem during bootup. I don't believe this could happen, but I don't understand why my ISP would shoot itself (and me) in the foot. Does anyone know enough about dhclient to say definitely whether it could have been the culprit? Anybody with enough experience with ISPs to say why they would have assigned an unregistered IP address that broke both systems?