From owner-freebsd-net@FreeBSD.ORG Thu Jul 15 19:28:44 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C69316A4CE for ; Thu, 15 Jul 2004 19:28:44 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1E3E43D1D for ; Thu, 15 Jul 2004 19:28:43 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id i6FJScnJ021381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Jul 2004 23:28:39 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i6FJSc2g021380; Thu, 15 Jul 2004 23:28:38 +0400 (MSD) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 15 Jul 2004 23:28:37 +0400 From: Gleb Smirnoff To: Gary Corcoran Message-ID: <20040715192837.GB21326@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Gary Corcoran , freebsd-net@freebsd.org References: <40F5C880.3090206@comcast.net> <20040715085219.GA17358@cell.sick.ru> <40F6A878.9090407@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <40F6A878.9090407@comcast.net> User-Agent: Mutt/1.5.6i cc: freebsd-net@freebsd.org Subject: Re: DHCP server over PPPoE server X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2004 19:28:44 -0000 On Thu, Jul 15, 2004 at 11:53:28AM -0400, Gary Corcoran wrote: G> My research indicates that rather than doing the usual DHCP DISCOVER to G> start things off, I should be able to send a DHCP INFORM message, G> which includes my already-assigned IP address. The DHCP server should G> see this, it then MUST NOT (according to the RFC) lookup the address G> in its lease database, but it then should respond, sending the all the G> configuration parameters *except* an IP address, back to the IP address G> that was included in the message. G> G> Thus my desire to get dhcpd running with mpd pppoe... G> Any suggestions? Well if you even make your DHCP server send packets to already configured IP address, I'm afraid the client side will just ignore them. What operating system is on client side? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE