From owner-freebsd-questions@FreeBSD.ORG Sun Aug 24 11:21:43 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 EDBC016A4C1 for ; Sun, 24 Aug 2003 11:21:42 -0700 (PDT) Received: from lakemtao04.cox.net (lakemtao04.cox.net [68.1.17.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id A287F43FCB for ; Sun, 24 Aug 2003 11:21:41 -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 <20030824182141.OEBN419.lakemtao04.cox.net@kongemord.krig.net> for ; Sun, 24 Aug 2003 14:21:41 -0400 Received: by kongemord.krig.net (sSMTP sendmail emulation); Sun, 24 Aug 2003 14:21:40 -0400 From: "Bob Hall" Date: Sun, 24 Aug 2003 14:21:40 -0400 To: FreeBSD Questions List Message-ID: <20030824182140.GA11060@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 8 X-UID: 8 Subject: dhclient denied repost 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: Sun, 24 Aug 2003 18:21:43 -0000 ----- Forwarded message from Bob Hall ----- Date: Thu, 21 Aug 2003 17:50:04 -0400 From: "Bob Hall" Subject: dhclient denied repost To: FreeBSD Questions List I'm posting this again in hopes that someone who has some insight into dhclient will notice it and respond. I'm getting the following message: Aug 21 13:00:03 kongemord dhclient: send_packet: Permission denied I don't believe the problem is the firewall for the following reasons: 1) DHCP works. I acquire and renew leases without any problems. 2) The IP address:port# pair for the failed connection is generally listed in messages when a connection attempt is blocked at the firewall. I've never received this message at a time when I didn't have an IP address, but the socket pair isn't listed. 3) Over the past couple of months, I've tried the following ipfw rules, without any change. ${fwcmd} add allow udp from any bootpc to any bootps keep-state out via ${oif} ${fwcmd} add allow udp from any bootps to any bootps keep-state out via ${oif} ${fwcmd} add allow udp from any to any bootps keep-state out via ${oif} Note that ipfw rewrites the last as $fwcmd add pass udp from any to any 67 keep-state out xmit ${oif} The two are equivalent. I'm not an expert on ipfw rules, and the problem could still be the firewall. I'd appreceate input from someone who knows more about it than I do. Bob Hall