Thanks, David. I'm going to have to go through the whole troubleshooting
process. Both the server and the client, my laptop, are running current and
to make it worse I did a portupgrade -Rria on both since I used dhcp the
last time. At least I know that it should work:-)
Quoting David Wolfskill <[EMAIL PROTECTED]>:
> >Date: Thu, 13 Dec 2001 06:15:32 -0800
> >From: Edwin Culp <[EMAIL PROTECTED]>
> >Is anyone using dhclient successfully with Current of the last week or so?
> Sure; hadn't noticed any problems with it.
> >I don't use it all the time but I have been trying for the last couple of
> >days without success.
> >It accesses the server and changes the interface ip to 0.0.0.0 netmask
> Odd. Looks like symptom of a failure to get a lease (to me, though I'm
> not an expert in DHCP). Do you have available IP addresses to hand out?
> Are you sure the NIC is operating properly? (E.g., can you put it in
> promiscuous mode & see traffic on the net, via tcpdump or ethereal?)
> (I've been tracking both -STABLE & -CURRENT daily(*), both on my laptop
> (which is a DHCP client) and my build machine (which isn't) for several
> months now....)
> * OK; modulo the occasional breakage. But that's been pretty rare --
> even in -CURRENT, for me.
> David H. Wolfskill [EMAIL PROTECTED]
> I believe it would be irresponsible (and thus, unethical) for me to advise,
> recommend, or support the use of any product that is or depends on any
> Microsoft product for any purpose other than personal amusement.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message