From owner-freebsd-net@FreeBSD.ORG Tue Jan 17 08:10:42 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 5657B16A41F; Tue, 17 Jan 2006 08:10:42 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD49A43D4C; Tue, 17 Jan 2006 08:10:41 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from [84.247.144.144] (helo=marcin) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1Eylus-0002rT-TG; Tue, 17 Jan 2006 09:10:11 +0100 Date: Tue, 17 Jan 2006 09:10:38 +0100 From: Marcin Jessa To: Brooks Davis Message-Id: <20060117091038.2a2027e0.lists@yazzy.org> In-Reply-To: <20060116180333.GA30608@odin.ac.hmc.edu> References: <20060116091605.GB18530@heff.fud.org.nz> <20060116112504.63ba886b.lists@yazzy.org> <20060116180333.GA30608@odin.ac.hmc.edu> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.9; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.1 (--) Cc: freebsd-net@freebsd.org, thompsa@freebsd.org Subject: Re: autobridge patch 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, 17 Jan 2006 08:10:42 -0000 On Mon, 16 Jan 2006 10:03:33 -0800 Brooks Davis wrote: > On Mon, Jan 16, 2006 at 11:25:04AM +0000, Marcin Jessa wrote: > > On Mon, 16 Jan 2006 22:16:05 +1300 > > Andrew Thompson wrote: > > > > > Hi, > > > > > > > > > I have a patch here that adds the ability to automatically add an > > > interface to a bridge when its attached. This is aimed towards > > > apps like qemu or vmware that open a tap interface and need it > > > bridged with the network adapter, the user can set up a glob for > > > interfaces to be automatically added (eg tap*). It may also be > > > useful for Xen dom0 support. > > > > > > This patch includes a big change to how interfaces are configured > > > in userland. Before only physical Ethernet cards were handled by > > > devd, now _ALL_ interfaces are (vlans, pflog, pfsync, tap, tun, > > > etc..). This has the added bonus that the pseudo interfaces can > > > be configured after boottime in rc.conf, ifconfig_xxx="". > > > > > > Please test this patch, even if you dont use a bridge. Im not in > > > a hurry to commit it. > > > > I just rebuild and installed my world and kernel to test the > > patches. Seems like things did not work as expected. > > The name part of ifconfig_vlan0 left me with renamed but not > > configured device. The IP etc of VLAN01 was not set at boot. Am I > > doning something wrong? > > > > cloned_interfaces="bridge0 vlan0" > > ifconfig_sk0="up" > > ifconfig_vlan0="name VLAN01 inet 10.137.99.4 vlan 1 vlandev sk0" > > If you want to rename the vlan interface use: > > ifconfig_vlan0_name="name VLAN01" > ifconfig_VLAN01="inet 10.137.99.4 vlan 1 vlandev sk0" > > not that this has anything to do with the Andrew's bridging script. Would be great if Andrew also wrote an example of how the patchset works. I read the patches now and it seems it works for bridge interfaces only adding ability to automatically add new interfaces to the bridge with the new "autobridge_*" options. The original post confused me making me think the patches made it possible to use a feature I was looking for and that I did know existed - operate on pseudo interfaces the same way one does with the normal ones. Your last comment in the "Automatic VLANS" thread on the same mailinglist made me assume I could not rename pseudo devices at boot with the rc.conf script, which I can see now was fully possible. Thanks, Marcin.