From owner-freebsd-current@FreeBSD.ORG Tue Jul 29 01:20:55 2003 Return-Path: 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 2C5B437B401 for ; Tue, 29 Jul 2003 01:20:55 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96C3D43F85 for ; Tue, 29 Jul 2003 01:20:54 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0dr.dialup.mindspring.com ([209.86.1.187] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19hPiz-0000XJ-00; Tue, 29 Jul 2003 01:20:50 -0700 Message-ID: <3F262E1E.9936E5D7@mindspring.com> Date: Tue, 29 Jul 2003 01:19:42 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Martin Blapp References: <20030729094308.L41136@cvs.imp.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4395a218928a880ea75ba67d37cac0923350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: current@freebsd.org Subject: Re: STEP 2, fixing dhclient behaviour with multiple interfaces X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 29 Jul 2003 08:20:55 -0000 Martin Blapp wrote: > I't is my goal to make dhclient really functional, so it can not only > be used with one interface, but several. > > On a well known OS this works just fine. A first interface gets > initialized and the GW gets set as usual. But if a second interface > gets added, and the first one is still active and has a working lease, > the GW will not be overwriten. If you remove now the first interface, > the default GW changes to the one of the second interface. [ ... ] > If there are other ideas, I'm open to them. You could add kevents for interface arrival and departure, and add a kqueue to the dhcpd to catch the arrival/departure events, and then just act on them. -- Terry