From owner-freebsd-current@FreeBSD.ORG Thu Jul 14 21:21:47 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E15F16A41C for ; Thu, 14 Jul 2005 21:21:47 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B24F43D48 for ; Thu, 14 Jul 2005 21:21:47 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 4B48919F3B; Thu, 14 Jul 2005 14:24:03 -0700 (PDT) From: "Darren Pilgrim" To: "'Eric Anderson'" Date: Thu, 14 Jul 2005 14:21:46 -0700 Message-ID: <003c01c588ba$0ad14a70$642a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 In-Reply-To: <42D6C686.4070407@centtech.com> Importance: Normal Cc: freebsd-current@freebsd.org Subject: RE: Problems with OpenBSD dhclient X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 21:21:47 -0000 From: Eric Anderson >=20 > Here's what I think would work well in most situations: >=20 > If another interface (B) is currently down, that has=20 > dhclient running=20 > on it, then when interface (A) comes up with a valid ip, it should=20 > remove the ip info from interface (B). This is a very bad idea. Unless the interfaces have been bonded or configured as redundant for each other, they're independent by design. If I'm using the wired port to do any of the many useful things one can do with multiple interfaces (diagnostics, configuring new devices without loss of internet access, etc.), I don't want the unavoidable link-state changes on that interface to result in my wireless connection going down. > If an interface (A) changes from down->up has conflicting IP=20 > information=20 > with an interface (B) that is down, that dhclient manages, it should=20 > remove the IP setup from interface (B), and set routes=20 > according to the=20 > newly upped interface. > > If an interface (A) changes from down->up, and there is another=20 > interface (B) that is up that dhclient manages, then=20 > configure interface=20 > (A) only if it will not conflict with the other interface's=20 > (B) network.=20 > This could be an rc.conf option - to force newly brought up=20 > interfaces=20 > to override currently up interfaces. No. Multiple interfaces with addresses in the same subnet (or even the same address) is a routing issue. Dhclient is not the correct tool to solve routing issues. A dhclient program needs to do only one thing: negotiate a lease for the interface specified.