From owner-freebsd-hackers Mon Dec 28 21:54:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21542 for freebsd-hackers-outgoing; Mon, 28 Dec 1998 21:54:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21535 for ; Mon, 28 Dec 1998 21:54:17 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id NAA70876; Tue, 29 Dec 1998 13:53:29 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812290553.NAA70876@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: hackers@FreeBSD.ORG Subject: Re: How do I ... In-reply-to: Your message of "Mon, 28 Dec 1998 18:40:34 MST." <199812290140.SAA17444@harmony.village.org> Date: Tue, 29 Dec 1998 13:53:28 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > ... write a kld that I can unload when I'm doing a network interface? > Or at the very lead the ability to reload the driver... The catch is that the driver in question has to support unloading. All the existing network interfaces are pseudo-modules and only have a load routine. Obviously this requires a fair amount of work to detach a network interface from the stack (including cleaning up routing tables, pcbs, queued data, etc) - nobody has done this yet as far as I'm aware. I suspect there is a fair amount of infrastructure required to implement this. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message