Date: Sat, 9 Jun 2001 19:02:14 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Brian Somers <brian@Awfulhak.org> Cc: Brooks Davis <brooks@one-eyed-alien.net>, Poul-Henning Kamp <phk@critter.freebsd.dk>, hackers@FreeBSD.ORG Subject: Re: cloning network interfaces Message-ID: <20010609190214.A6854@Odin.AC.HMC.Edu> In-Reply-To: <200106092024.f59KOMA07577@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sat, Jun 09, 2001 at 09:24:22PM %2B0100 References: <brooks@one-eyed-alien.net> <200106092024.f59KOMA07577@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 09, 2001 at 09:24:22PM +0100, Brian Somers wrote: > I think it'd be better to use the solaris ``plumb'' keyword. I can't=20 > recall how it works (something like ``ifconfig gif0 plumb'' - I=20 > haven't got a Solaris machine handy here), but it seemed cleaner,=20 > making it more obvious what's being done. An ``unplumb'' keyword may=20 > be appropriate for doing the removal. That's how it works. I've though about adding (un)plumb functions, but that gets a bit weird. With the current way ifconfig parses options would require that you peak at the argument list early because you need to create the device before arguments are processed. Also, given the way the FreeBSD rc system works you have to support commands like: ifconfig gif0 plumb inet 10.0.0.1 10.0.0.2 tsrc 192.168.1.6 tdst 192.168.1.7 because you only get one shot at each device[0]. In -stable I think I'd like to leave the current create behavior where devices are created if you try to use them and perhaps emit a warning suggesting using plumb to avoid breaking configs. In 5.0 I'd be reasionably happy to force plumbing of interfaces if there's come concensus that it's the right way to go. Alternativly, we could hack the rc system to try plumbing all interfaces before they are used. Any opinions on this? -- Brooks [0] This is actually a serious problem with wireless interfaces today because you can't write: ifconfig wi0 ssid XXX wepmode on wepkey 1:12345 DHCP which is exactly what you want to do on most home networks. IMO following the Solaris example of teaching ifconfig about dhcp is the right way to go here. Perhaps by allowing plugable external parameters to keep it general. --=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 --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7ItUlXY6L6fI4GtQRAgoxAKCURYzCIfMXEo5wuLpK7tCTht5AUACfXa9o h/v0w/StECrMyVS4RT1/NQc= =Doz6 -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010609190214.A6854>