Update on the situation: FreeBSD 5.1's version of the ISC dhclient, which is 
something like the same major number but r30, works flawlessly (even with 
the packet error). Just like with the NetBSD box, I did not at first use the 
dhclient.conf... and did not need to.

Also, I had been using the default 1.6.1 kernel/userland... should I have 
recompiled anything with any other options to use dhclient properly? It does 
the same thing as NetBSD 1.6.1's version output-wise, but it just doesn't 
connect...


>From: "Thomas Miller" <tom@insolvencyhelp.org>
>Reply-To: "Thomas Miller" <tom@insolvencyhelp.org>
>To: onlyihavehandle@hotmail.com
>Subject: Re: 1.6.1 cannot get dhclient to work
>Date: Wed, 14 Jan 2004 17:21:15 -0500
>
>"Allen Thomas" <onlyihavehandle@hotmail.com> wrote:
>
> > I have the basic "request"s configured in /etc/dhclient.conf; starting
> > dhclient yields the standard stuff, then:
> >
> > ip length 576 disagrees with bytes received 582
> > accepting packet with data after udp payload
> >
> > Then it seems to work, but it doesn't. No /etc/resolv.conf updating, I 
>can't
> > even ping my router. (Which runs a DHCP server)
> >
> > Oddly enough, if I run dhclient without specifying the interface, it 
>starts
> > sending DHCPDISCOVER to strip1... but then gets some of the following 
>stuff
> > from sip0.
> >
> > Apologies if this is the wrong list, and especially about the lack of
> > information, but I'm having to type by hand and by memory (boxes aren't
> > close).. oh yeah, and about the hotmail too, but it's the only thing I 
>can
> > get on at the moment
> >
> > If anyone has the slightest clue what the hell I'm talking about, please 
>CC
> > me (I'll be happy to hand-type as much information as is necessary)
> >
> > _________________________________________________________________
> > Get a FREE online virus check for your PC here, from McAfee.
> > http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>I'm far from an expert, but, if you have only one network card in
>the NetBSD machine, you could try moving the dhclient.conf aside,
>rebooting the NetBSD machine and also the router, and then running
>dhclient without the benefit of the dhclient.conf.
>
>Here, dhclient works this way on hpcmips, macppc, and also i386.
>
>Fwiw, I also get the length error message on all three platforms,
>but I haven't bothered to run it down because everything seems to
>be working okay despite the error message.
>
>Here, dhclient finds the network card in each machine all by itself
>without any configuration.
>
>If you don't want to reboot the NetBSD machine, try issuing the
>command `dhclient -r' followed by dhclient.
>
>Hope this helps you at least a little!
>
>Best wishes and kindest regards,
>
>Tom

_________________________________________________________________
Rethink your business approach for the new year with the helpful tips here. 
http://special.msn.com/bcentral/prep04.armx