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
> recall how it works (something like ``ifconfig gif0 plumb'' - I
> haven't got a Solaris machine handy here), but it seemed cleaner,
> making it more obvious what's being done. An ``unplumb'' keyword may
> 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.
--
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
PGP signature
