From owner-freebsd-hackers Tue Apr 7 19:49:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28008 for freebsd-hackers-outgoing; Tue, 7 Apr 1998 19:49:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.numachi.com (numachi.numachi.com [198.175.254.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA27970 for ; Tue, 7 Apr 1998 19:48:48 -0700 (PDT) (envelope-from reichert@numachi.numachi.COM) Received: (qmail 23303 invoked by uid 1001); 8 Apr 1998 02:48:39 -0000 Message-ID: <19980407224839.64875@numachi.com> Date: Tue, 7 Apr 1998 22:48:39 -0400 From: Brian Reichert To: hackers@FreeBSD.ORG Subject: dhcpc and ed3 interface Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya- I'm having marginal luck getting the wide-dhcpc DHCP client working consistently. I've got the bpf interface built, etc, but occasionally, when I reboot, the dhcpc process bitches that my 'device isn't configured for dhcp'. Rebooting _eventually_ clues it in, but I feel it's silly to adopt such an M$-like solution. I admit I'm using the worlds cheapest PCI NE2000 clones. But these things have been behaving quite well. Does anyone have an opinion as to to why the dhcpc software occasionally thinks my card isn't configured? -- Brian Reichert reichert@numachi.com 37 Crystal Ave. #303 Current daytime number: (617)-873-4337 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message