From owner-freebsd-net Fri May 29 14:20:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05020 for freebsd-net-outgoing; Fri, 29 May 1998 14:20:32 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from toccata.fugue.com (toccata.fugue.com [204.152.188.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04959 for ; Fri, 29 May 1998 14:20:13 -0700 (PDT) (envelope-from mellon@andare.fugue.com) Received: from andare.fugue.com (andare.fugue.com [204.152.188.69]) by toccata.fugue.com (8.8.8/8.6.11) with ESMTP id OAA14046; Fri, 29 May 1998 14:19:35 -0700 (PDT) Received: from localhost (localhost [[UNIX: localhost]]) by andare.fugue.com (8.8.8/8.6.11) with SMTP id OAA03408; Fri, 29 May 1998 14:19:34 -0700 (PDT) Message-Id: <199805292119.OAA03408@andare.fugue.com> To: "Pitcairn, Duncan" cc: "'dhcp-client@fugue.com'" , "'freebsd-net@freebsd.org'" Subject: Re: FreeBSD Dhclient-script errors In-Reply-To: Your message of "Fri, 29 May 1998 16:24:49 EDT." Date: Fri, 29 May 1998 14:19:25 -0700 From: Ted Lemon Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, if it doesn't install the default route, there's probably something wrong with that code. What you should do to debug this is to kill off your existing dhcp client, and then run it again with the -D flag, which leaves the script invocation scripts around. Run the client, and when it goes into daemon mode, kill it off again. Then look for the most recent client script initialization code in /tmp - there will be four or five initialization scripts there - and run it by typing ``sh -x script-name''. Send us the output. _MelloN_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message