From owner-freebsd-arch Tue Dec 14 18:17:17 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 6738115370 for ; Tue, 14 Dec 1999 18:17:14 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id DAA15228 for ; Wed, 15 Dec 1999 03:17:13 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA67644 for freebsd-arch@freebsd.org; Wed, 15 Dec 1999 03:17:12 +0100 (MET) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id B5FAF15282 for ; Tue, 14 Dec 1999 18:16:48 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id TAA08379; Tue, 14 Dec 1999 19:16:27 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpdAAA5laWuq; Tue Dec 14 19:16:20 1999 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA17370; Tue, 14 Dec 1999 19:16:31 -0700 (MST) From: Terry Lambert Message-Id: <199912150216.TAA17370@usr08.primenet.com> Subject: Re: The if_detach problem To: brian@Awfulhak.org (Brian Somers) Date: Wed, 15 Dec 1999 02:16:31 +0000 (GMT) Cc: jlemon@americantv.com, brian@Awfulhak.org, imp@village.org, freebsd-arch@freebsd.org, brian@hak.lan.Awfulhak.org In-Reply-To: <199912142322.XAA36949@hak.lan.Awfulhak.org> from "Brian Somers" at Dec 14, 99 11:22:15 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Right, but how about a ``notthere'' flag instead ? A "virtual interface"? This plays havoc with default routes. > My concern is that there are some APIs that use interface ids > (sysctl(PF_ROUTE) springs to mind) and some APIs that use > interface names (the struct ifaliasreq ioctls etc) and reassigning > the association between the two on the fly seems a tad dangerous - > lots of races. I think the answer is as obvious as "ps" and "libkvm": data interfaces suck, and procedureal interfaces don't. > Another (more real?) argument for keeping the interface but making it > unusable 'till the driver wants it again is that there may be > security concerns.... at the moment, ``netstat -i'' reports what's > been going on very nicely. Removing the interface entirely will > allow people to hide what should not be hidden.... ??? Doug Ambrisko is running wireless in the office right now with a PCMCIA card. It's unreasonable to not allow him to switch between a wireless adapter and a docking bay or other PCMCIA card as his default route as it becomes available. I think that the routing table and other information needs to be correct, more than it needs to be historically accurate. For netstat -i, if you destroy the object on which you are keeping statistics, it's right to destroy the statistics information as well. Consider that packets sent, collisions, and similar counts are not presistant across a reboot (in which interfaces are "deinstanced" and subsequently "reinstanced"). I know there's a lot of cached state issues, but like "ps", this isn't a very good reason to _not_ fix them. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message