From owner-freebsd-questions Wed Sep 5 16:57:12 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id 32D1737B406 for ; Wed, 5 Sep 2001 16:57:09 -0700 (PDT) Received: (qmail 41371 invoked from network); 6 Sep 2001 00:06:17 -0000 Received: from unknown (HELO proxy.the-i-pa.com) (151.201.71.210) by mail.the-i-pa.com with SMTP; 6 Sep 2001 00:06:17 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Bill Moran Organization: Potential Technology To: Cary , freebsd-questions Subject: Re: dhclient problems Date: Wed, 5 Sep 2001 19:59:56 -0400 X-Mailer: KMail [version 1.2] References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01090519595600.00871@proxy.the-i-pa.com> Content-Transfer-Encoding: 8bit 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 On Wednesday 05 September 2001 16:22, Cary wrote: > I've had my box up and running for about 2 weeks, no problems. About > 5 days ago, I suddenly started getting the following message in my > system logs: > Sep 4 20:39:54 fledermaus dhclient: send_packet: Permission denied > > I have the kernel firewall (ipfw) installed and have used the rc.d > script to start it up on bootup, as a client computer. But the > dhcp.lease is recieved > without any problem when I bootup, so I don't think ipfw is the source > of the problem. If I turn my computer reboot my computer, it may or > may not get the lease at first, but then it will. Afterwards, I can > access the network and all, but then these messages start showing up > again. My ability to get work done is not affected (that I've noticed) > but it is very annoying to have to scroll through the syslogs and > seeing this repeated ad infinitum. I hit this one a little while back with firewalls. If I'm remembering incorrectly, someone else feel free to correct me. When the machine first boots up, and it doesn't know who the DHCP server will be, it does ethernet broadcasts to find a DHCP server and config its networking. However, once it's been running for a while and it's time to renew the DHCP lease, it connects to the server in a different manner - which can be adversely affected by firewall rules. I don't remember the details (i.e. ports and firewall rules to allow DHCP) but the way I figured it out was to run a sniffer (ethereal or tcpdump) and see what was actually happening. You can do the same. -Bill -- Bill Moran Potential Technology technical services (412) 793-4257 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message