From owner-freebsd-questions@FreeBSD.ORG Fri Aug 22 11:11:16 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 5480716A4BF for ; Fri, 22 Aug 2003 11:11:16 -0700 (PDT) Received: from lakemtao04.cox.net (lakemtao04.cox.net [68.1.17.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8D0143FBD for ; Fri, 22 Aug 2003 11:11:14 -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 <20030822181115.OSQQ419.lakemtao04.cox.net@kongemord.krig.net> for ; Fri, 22 Aug 2003 14:11:15 -0400 Received: by kongemord.krig.net (sSMTP sendmail emulation); Fri, 22 Aug 2003 14:11:14 -0400 From: "Bob Hall" Date: Fri, 22 Aug 2003 14:11:14 -0400 To: FreeBSD Questions List Message-ID: <20030822181113.GA8719@kongemord.krig.net> Mail-Followup-To: FreeBSD Questions List References: <20030821215003.GA1524@kongemord.krig.net> <44lltlya5g.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44lltlya5g.fsf@be-well.ilk.org> User-Agent: Mutt/1.4.1i Subject: Re: 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: Fri, 22 Aug 2003 18:11:16 -0000 On Fri, Aug 22, 2003 at 11:39:07AM -0400, Lowell Gilbert wrote: > "Bob Hall" writes: > > > 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. > > They're not redundant. 67 is bootps and 68 is bootpc. My error. > Furthermore, > not all DHCP messages go out to the IP broadcast address. > > > 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? > > You don't get IP addresses listed when you don't have one yet. I have an IP address. I have never received the message at a time when I didn't have an IP address. > I'd recommend trying something like this for your DHCP support: > $fwcmd add pass udp from any to any bootps keep-state out xmit ${oif} I tried it and it had no effect. The only difference between "out via" and "out xmit" is that "out via" checks both incoming and outgoing packets, while "out xmit" checks only outgoing. In theory, there may be a difference between "from any bootps" and "from any", but in practice it has made no difference in behaviour. I got the same message either way. Bob Hall