From owner-freebsd-questions Tue Nov 6 10:20:22 2001 Delivered-To: freebsd-questions@freebsd.org Received: from kludgebox.com (kludgebox.com [208.44.74.30]) by hub.freebsd.org (Postfix) with ESMTP id 2819237B419; Tue, 6 Nov 2001 10:20:16 -0800 (PST) Received: by kludgebox.com (Postfix, from userid 1000) id 7D59727601; Tue, 6 Nov 2001 10:20:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by kludgebox.com (Postfix) with ESMTP id 6EC7226701; Tue, 6 Nov 2001 10:20:10 -0800 (PST) Date: Tue, 6 Nov 2001 10:20:10 -0800 (PST) From: Bob Zoller To: freebsd-questions@freebsd.org, Subject: rc.network diff Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG When my computer boots, it tries to use DHCP to assign xl0 (built in ethernet) an IP. Often times I am not using a physical cable, but rather using my wireless pcmcia card. The problem is while dhclient is sitting there waiting to timeout (I ususally hit Ctrl-C), the wireless card gets attached and fails to get an IP address (because.. I assume.. dhclient is already running for xl0). I wrote a patch to rc.network that fixes this. Quite simply, it doesn't bother running dhclient on an interface that is listed with a status of "no carrier" (ie no network plugged in). Now when I boot (no hardwire, wireless inserted), rc.network sees that xl0 isn't plugged in, skips trying to run dhclient, and proceeds to boot. When pccardd attaches my wireless card, it starts right up and grabs an IP address sucessfully. http://www.kludgebox.com/rc.network.diff Not sure if this will help anyone else.. but it works for me! Also handy for speeding up the boot of machines that use DHCP but aren't always plugged in. --Bob PS.. I'm not subscribed to either list, so please reply to my email directly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message