From owner-freebsd-net@FreeBSD.ORG Tue Aug 22 19:33:29 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 3C80F16A4DE for ; Tue, 22 Aug 2006 19:33:29 +0000 (UTC) (envelope-from fbsd@synoptic.org) Received: from gort.synoptic.org (gort.synoptic.org [216.254.17.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 234A743D73 for ; Tue, 22 Aug 2006 19:33:19 +0000 (GMT) (envelope-from fbsd@synoptic.org) Received: by gort.synoptic.org (Postfix, from userid 1000) id 7D4686352EBE; Tue, 22 Aug 2006 12:33:19 -0700 (PDT) Date: Tue, 22 Aug 2006 12:33:19 -0700 From: Xander To: freebsd-net@freebsd.org Message-ID: <20060822193319.GB27130@gort.synoptic.org> References: <021a01c6c322$d52bf510$4345a8c0@phobos> <20060819025613.GB11181@lor.one-eyed-alien.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060819025613.GB11181@lor.one-eyed-alien.net> User-Agent: Mutt/1.4.2.1i Subject: Re: dhclient and multiple addresses on single interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Aug 2006 19:33:29 -0000 On Fri, Aug 18, 2006 at 09:56:13PM -0500, Brooks Davis wrote: > > Not easily. If you could create some virtual ethernet interfaces, > bridge them to the real one and run dhclient on them I think that would > work, but I can't think of a suitable virtual interface at the moment. > I've actually played with this a little and got some enouraging results by using netgraph to create a number of virtual ethernet interfaces all linked to a netgraph bridge node linked to a physical interface. However, I ultimately ran into an issue where the global ARP table was making it difficult to actually *use* any of the other virtual interfaces. (when you resolve an ARP address on the local subnet, you remember what interface you resolved in on and tend to prefer that interface for all communications whether you want to or not). I didn't rule out the possibility that some serious firewall hackery/NATing could get around this problem. YMMV but netgraph is probably a good avenue to explore next if you haven't done so already. Oh, also I seem to remember thinking that a recent commit to the 6.1-STABLE codebase might have helped the arp difficulty I was experiencing, so it may all work better now than I did when I was playing with it. -x