From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 18:48:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37F6E1065672 for ; Mon, 9 Jun 2008 18:48:59 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) Received: from mx1-a.inoc.net (mx1-a.inoc.net [64.246.131.30]) by mx1.freebsd.org (Postfix) with ESMTP id D9A8C8FC15 for ; Mon, 9 Jun 2008 18:48:58 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=inoc.net; h=Received:From:To:Subject:Date; b=lHJmHVms8M82LfG0Nxk51mIMP2kt1F4JjGseOI7LNcqGJzGJyFHoV1pJE0HrzeD8o4OzvYx5i/aa3QuCMYdhlhO8QtmDdryA2k+y7qocNa6Lrr61hflMxxD82sB8pwf337BFfD85onne/Ncrzv36Ck3xYyKLPbqWPaan2wibJgI=; Received: from void.ops.inoc.net (vanguard.noc.albyny.inoc.net [64.246.135.8]) by mx1-a.inoc.net (build v8.3.29) with ESMTP id 150419829-1941382 for ; Mon, 09 Jun 2008 18:48:58 +0000 (UTC) Message-Id: <0D67AF88-6593-47F3-9774-BE1875795B80@inoc.net> From: Robert Blayzor To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 9 Jun 2008 14:48:57 -0400 X-Mailer: Apple Mail (2.924) Subject: BOOTP and no default route X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 18:48:59 -0000 Is there any way to prevent the BOOTP client from injecting a default route? When I originally set things up our DHCP server would not send a default route because there was no gateway, local only. If you leave out the default route, the server will try proxy-arp when ends up putting a default route to itself in the routing table. The problem is that on startup the servers actually setup static networks with default routes out another interface. The problem is, if the BOOTP client puts in a default route, we cannot easily add another default because one already exists. The only way I've found around this behavior was to error the BOOTP client out and send it a default gateway that does not exist on the local net the DHCP server provides. This causes the BOOTP client not to set a default route and all works fine. Obviously this seems like a cobb/hack and was wondering if there was a BOOTP option or kernel tweak that can be done to tell the BOOTP client not to use proxy-arp. -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net http://www.inoc.net/~rblayzor/