> On Sun, 2005-09-25 at 17:27, Pimin wrote:
> > My DHCP connection with Comcast started behaving strangely
> > when they changed their DHCP server to address 10.145.0.1.
> > My NetBSd (1.5A) firewall started running out of buffers
> > NMBCLUSTERS exhausted (or some such message).  Now when
> > I run "dhclient tlp1" (which used to work just fine) I
> > get:
> > 
> 
> It's hard to imagine that no one replied to this.

I did get several off-list replies.

> This error "address already in use" means dhclient(8) is trying to bind
> to the "bootpc" UDP port on ...whatever interface and that there's
> already an instance running.

No, no other dhclient is running.  Power cycling the modem (with more than
an hours off time) didn't help.  If I hook it to another machine it works
fine.  I'm thinking (very dangerous) that the NIC may be bad.

> Just "pkill -9 dhclient" and try again.  Fix up dhclient_intefaces in
> rc.conf and "/etc/rc.d/dhclient restart"

This had been working then Comcast changed their DHCP server to address
10.145.0.1.  Now that one machine can't get dhclient to work.  The address
is routed over that interface just like the old address was.

Paul


> ~BAS
> 
> >   Can't bind to dhcp address:
> >   Address already in use.
> > 
> > I run tcpdump on that interface.  I see lots of arp requests
> > for/from other machines on the network but, I never see any
> > activity generated by the firewall.  It's not going ot the
> > network to determine the "already in use" address.   I've
> > move the lease file aside,  Removed it completely. Put it
> > back.  Tried this witht he interface up and down, as the 
> > default route and not as the default.  
> > 
> > I'm hoping somebody will be able to point me at what information
> > I should be looking at to help me figure out what address is
> > "already in use"??
> > 
> > TIA,
> > Paul
> 
>