Date: Wed, 5 Sep 2001 20:20:37 -0400 (EDT) From: Dru <genisis@istar.ca> To: Bill Moran <wmoran@iowna.com> Cc: Cary <scattered@babel.acu.edu>, freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: dhclient problems Message-ID: <20010905201754.D25332-100000@x1-6-00-50-ba-de-36-33.kico1.on.home.com> In-Reply-To: <01090519595600.00871@proxy.the-i-pa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Sep 2001, Bill Moran wrote: > 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. Hi Cary, I second what Bill says; though it's hard to see what's blocking what without a look at your firewall rules. The following article might shed some light on what DHCP is doing: http://www.onlamp.com/pub/a/bsd/2001/06/01/FreeBSD_Basics.html If that doesn't help, send the output of "ipfw show" to the list. Dru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010905201754.D25332-100000>