From owner-freebsd-questions@FreeBSD.ORG Thu Aug 21 14:50:06 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E29A16A4BF for ; Thu, 21 Aug 2003 14:50:06 -0700 (PDT) Received: from lakemtao04.cox.net (lakemtao04.cox.net [68.1.17.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD0BA43F85 for ; Thu, 21 Aug 2003 14:50:05 -0700 (PDT) (envelope-from rjhjr@cox.net) Received: from kongemord.krig.net ([68.100.111.121]) by lakemtao04.cox.net (InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with SMTP id <20030821215006.DIFB419.lakemtao04.cox.net@kongemord.krig.net> for ; Thu, 21 Aug 2003 17:50:06 -0400 Received: by kongemord.krig.net (sSMTP sendmail emulation); Thu, 21 Aug 2003 17:50:04 -0400 From: "Bob Hall" Date: Thu, 21 Aug 2003 17:50:04 -0400 To: FreeBSD Questions List Message-ID: <20030821215003.GA1524@kongemord.krig.net> Mail-Followup-To: FreeBSD Questions List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-IMAPbase: 1061250701 6 X-UID: 6 Subject: dhclient denied X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2003 21:50:07 -0000 I posted about this a while ago, but I haven't been able to find the cause. I'm getting the following message: Aug 21 13:00:03 kongemord dhclient: send_packet: Permission denied DHCP seems to work fine; I'm getting and maintaining DHCP leases properly. But these messages are filling up my messages file and causing my curiosity to drive me crazy. I initially thought that my firewall was blocking DHCP packets, but I've tried various ipfw rule changes, including some suggested here, with no effect. My current DHCP rules are: ${fwcmd} add allow udp from any bootps to any bootps keep-state out via ${oif} ${fwcmd} add allow udp from any 68 to 255.255.255.255 67 keep-state out via ${oif} I know the second line is redundent. I was grasping at straws when I put it in. Generally, a failed connection attempt generates a message with the IP address and port at each end. This message doesn't have that, so that and the failure of firewall changes to end the message make me think that the blocked packets aren't getting as far as the firewall. Does anybody have any idea what is causing this? Bob Hall