Date: Tue, 17 Jan 2006 09:49:19 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Marcin Jessa <lists@yazzy.org> Cc: freebsd-net@freebsd.org, thompsa@freebsd.org Subject: Re: autobridge patch Message-ID: <20060117174919.GC21625@odin.ac.hmc.edu> In-Reply-To: <20060117093203.1fb41851.lists@yazzy.org> References: <20060116091605.GB18530@heff.fud.org.nz> <20060116112504.63ba886b.lists@yazzy.org> <20060116180333.GA30608@odin.ac.hmc.edu> <20060117093203.1fb41851.lists@yazzy.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--1ccMZA6j1vT5UqiK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 17, 2006 at 09:32:03AM +0100, Marcin Jessa wrote: > On Mon, 16 Jan 2006 10:03:33 -0800 > Brooks Davis <brooks@one-eyed-alien.net> wrote: >=20 > > On Mon, Jan 16, 2006 at 11:25:04AM +0000, Marcin Jessa wrote: > > > On Mon, 16 Jan 2006 22:16:05 +1300 > > > Andrew Thompson <thompsa@freebsd.org> wrote: > > >=20 > > > > Hi, > > > >=20 > > > >=20 > > > > 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. > > > >=20 > > > > 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=3D"". > > > >=20 > > > > Please test this patch, even if you dont use a bridge. Im not in > > > > a hurry to commit it. > > >=20 > > > 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? > > >=20 > > > cloned_interfaces=3D"bridge0 vlan0" > > > ifconfig_sk0=3D"up" > > > ifconfig_vlan0=3D"name VLAN01 inet 10.137.99.4 vlan 1 vlandev sk0" > >=20 > > If you want to rename the vlan interface use: > >=20 > > ifconfig_vlan0_name=3D"name VLAN01" > > ifconfig_VLAN01=3D"inet 10.137.99.4 vlan 1 vlandev sk0" >=20 > Actually only this will work: > ifconfig_vlan0_name=3D"VLAN01" > ifconfig_VLAN01=3D"inet 10.137.99.4 vlan 1 vlandev sk0" >=20 > One thing I noticed was VLAN01 could not be called something more > descriptive like VLAN-FOO since then the startup scripts went bananas > leaving my console in an ifconfig loop. I know about that problem and plan to fix it (by collapsing the namespace so that all unsupported characters are treated as though they are _'s in the rc.conf scripts). It's not super high on my current list though so if someone else wasn't to do it, that would be great. > There was a patch from bart <bart@convex.ru> that he posted to > net@ adding possibility to add an ASCII description to devices the same > way Cisco does.=20 > Was it ever conserned as a commit candidate? I plan to commit a revised version at some point, but first I want to commit the ioctl changes I proposed a few days ago so we don't end up with an implicit size encoded in the ioctl interface. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --1ccMZA6j1vT5UqiK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDzS4eXY6L6fI4GtQRAolrAJ9byR3kovyexG5+ODnnml1DspoQDQCfRpzJ FeoTlRqL7me2Ibbd7yQXKk8= =eQF+ -----END PGP SIGNATURE----- --1ccMZA6j1vT5UqiK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060117174919.GC21625>